We follow a common workflow. The first few times, it feels like a lot, but it gets better.
Follow ⭐ Workflow: Apply Example to complete:
- Phase 1. Start & Run - copy the project and confirm it runs
- Phase 2. Change Authorship - update the project to your name and GitHub account
- Phase 3. Read & Understand - review the project structure and code
Continue with the same guide to complete:
- Phase 4. Make a Technical Modification - make one small, observable, explainable change and keep the project running.
- Phase 5. Apply the Skills to a New Problem - implement a custom project based on the example; see your-files.md for naming.
src/- modules named with your aliasnotebooks/- notebooks named with your aliasdata/raw/- source inputsdata/processed/- processed exports, if anyartifacts/- database files, logs, reports, or other outputs
Update the project landing page to describe your work: badges, tagline, project description, run commands, links to key artifacts, any visuals.
Your analytics write-up - the introduction, data description, objective & process, results & insights, future work, and the techniques you applied (be explicit while in school; later your skills become more implicit).
Set the About section with a link to your GitHub Pages site. Check the box. The workflow includes how to set the repo Pages to GitHub Actions. Pushing to GitHub automagically triggers an action to deploy the docs.
- Working project
- Meaningful insights with logged results
- Understanding of your chosen domain
- Accessible narrative
- Images, tables, logs, or output conveying your work
- GitHub About section linking to your GitHub Pages site