Stricly Adhere to the order
HTML_implementation/
βββ index.html
βββ login.html
βββ register.html
βββ notes.html
βββ profile.html
βββ style/
β βββ main.css
β βββ login.css
β βββ register.css
β βββ dashboard.css
β βββ responsive.css
βββ assets/
βββ logo.png
βββ favicon.ico
βββ icons/
We use an issue-based development flow. Some issues are dependent on others and must be completed in sequence.
-
Only start working on an issue that is assigned to you.
-
Do not submit a PR without a corresponding GitHub issue.
-
In your PR description, mention the issue number it closes using:
Closes #issue_number -
Only one issue should be solved per pull request.
-
Your PR will only be accepted if:
- It is properly linked to the issue.
- The issue has a points label (e.g.,
10 points). - The code follows the structure and naming conventions.
-
Do not work on blocked issues. Wait for dependencies to be resolved.
-
Make sure your code is well formatted and clean before submitting.
- Only claim one issue at a time. This helps avoid conflicts and encourages quality over quantity.
- Check dependencies before working on an issue.
- Mention the issue youβre working on in your Pull Request title and description.
- If an issue is marked
blocked, wait for the dependent issue to be closed before starting work.
| Issue | Description | Depends On |
|---|---|---|
| #2 | Style the login form | #1 (Login HTML layout) |
| #4 | Add responsive CSS for register page | #3 (Register HTML structure) |
| #6 | Create task board columns (To Do, In Progress, Done) | #5 (Basic dashboard layout) |
| Label | Meaning |
|---|---|
good first issue |
Beginner-friendly task |
blocked |
Cannot be worked on until prerequisite is done |
in progress |
Someone is already working on it |
ready |
Open for contribution |
needs review |
Pull Request submitted |