Skip to content

docs: add Git branching best practices and optimize Netlify deployment instructions#29

Open
Grajales-K wants to merge 6 commits into
CodeYourFuture:mainfrom
Grajales-K:patch-1
Open

docs: add Git branching best practices and optimize Netlify deployment instructions#29
Grajales-K wants to merge 6 commits into
CodeYourFuture:mainfrom
Grajales-K:patch-1

Conversation

@Grajales-K
Copy link
Copy Markdown

@Grajales-K Grajales-K commented Apr 26, 2026

Revised PR Description
Problem: Currently, the instructions do not introduce GitHub Pages for early deployment, leading to unnecessary consumption of Netlify build credits. Additionally, the Level 500 instructions lack explicit guidance on feature branches and final deployment setup.

Changes:

Level 0: Replaced Netlify with GitHub Pages for initial deployment to provide a free, unlimited hosting option during early development.

Level 500: * Moved Netlify deployment instructions here as the final "production" step.

Added a detailed Step-by-Step guide for Netlify setup (since it was removed from Level 0).

Added a "Technical Workflow" section to encourage the use of feature branches (feature/level-500) after merging Level 400.

Aligned instructions with dashboard submission requirements to reduce student confusion.

Updated the success criteria to clarify that students should only deploy to Netlify once they reach Level 500. This change helps students avoid exhausting their Netlify build credits during the earlier stages of the project
Added best practices for Git branching and deployment. Encouraging students to use feature branches for Level 500 and deploy only after final merge to optimize Netlify usage.
Copy link
Copy Markdown
Member

@illicitonion illicitonion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally LGTM - let's avoid repeating the contents of the deployment guides here, so that if the steps need to change (e.g. if Netlify change their screens) we only need to update one place not multiple.

Comment thread levels/level-0.md Outdated
Comment thread levels/level-500.md Outdated
Comment thread levels/level-500.md Outdated
Comment thread levels/level-500.md Outdated
@Grajales-K Grajales-K requested a review from illicitonion May 11, 2026 23:07
@Grajales-K
Copy link
Copy Markdown
Author

Hi @illicitonion, thank you so much for carefully checking my changes. I have updated the file and removed the repetitive information that is already covered in the official documentation. I hope this is clearer now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants