Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version of Development Strategy #32

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

GabriellaLohy
Copy link
Contributor

@GabriellaLohy GabriellaLohy commented Apr 8, 2023

This is the new development strategy that I made using Samir template.
Inside this PR you can see this changes:

  1. Whole brand new version of development strategy
  2. Added wireframe picture named wireframe.jpg
  3. Added User Story Dependency diagram
  4. Organized assets folder

General Checks

  • the branch is up to date with main/master
  • the code works when pulled and run locally
  • All CI checks pass
  • all conflicts are resolved (if any)
  • PR has a descriptive title
  • PR has appropriate labels and milestones for easy identification
  • PR it is assigned to the owner
  • reviewers are assigned
  • the PR contributes only one focused change
  • It is in the appropriate column in the project board (if necessary)
  • has short and clear description
  • is linked to an issue (if it is related)
  • feedback is addressed (if any and if it is appropriate feedback.)

Markdown

  • the markdown source is formatted
  • spelling and grammar is correct in all text
  • The markdown looks correct when you preview the file
  • all links and images work

HTML

  • pages besides /index.html are stored in /pages
  • the code is well-formatted
  • the HTML is valid
  • there are no inline styles (example: style='color: red;')
  • there are no <style> tags with CSS, all styles are hrefs
  • there is no inline JavaScript (example: onclick='doSomething()')
  • there are no <script> tags with JS, all JS is in an separate file
  • ids are used for JavaScript only, not for CSS
  • semantic tags are used
  • spelling and grammar is correct in all site content

CSS

  • the code is well-formatted
  • passes all the linting checks

…, adding story dependency diagram, use the development strategy template from samir
@GabriellaLohy GabriellaLohy added documentation Improvements or additions to documentation planning Organizing information or task labels Apr 8, 2023
@GabriellaLohy GabriellaLohy added this to the Agile Development milestone Apr 8, 2023
@GabriellaLohy GabriellaLohy self-assigned this Apr 8, 2023
@GabriellaLohy GabriellaLohy linked an issue Apr 8, 2023 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation planning Organizing information or task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to remake development strategy
1 participant