How vishakhasadhwani/60daystocloud works
Project type and purpose (what you’re diagramming)
This repo is not an application/runtime system (no src/, services, or executables). It’s a curriculum/content repository for the “60DaysToCloud – Foundations track,” organized as weekly modules, each with its own README containing goals, learning resources, labs, templates, and mini projects.
File structure (what the system is made of)
Top-level structure indicates a modular, week-by-week layout:
• README.md (root): program overview, structure, how to use, contribution guidance, license.
• Prework_Foundations/README.md: prework module.
• Week1_Cloud_Foundations/README.md … Week8_Final_Projects/README.md: weekly modules.
• images/: shared visual assets used by READMEs (or intended to be).
This implies a simple but important architecture:
• Root README is the “entrypoint”
• Each week folder is a self-contained module
• Images are a shared dependency across modules
• Contribution flow is PR-based (not code build/deploy)
Pull key architectural hints from the README
From the root README:
• Each week “has its own set of steps,” “topics, free resources and notes,” and “mini projects.”
• Usage model: learner navigates week-by-week, consuming READMEs.
• Contribution model: contributors open PRs against chore/add-weekly-folders (or main).
These lines define the primary interactions worth diagramming:
• Learner ↔ GitHub repo content
• Contributor ↔ Branch/PR workflow ↔ Maintainer review ↔ Merge into main
What
Use clear conventions:
Labels
• Use the exact folder names as component names (this repo is strongly name-driven).
• Root README → each week (progression / index links)
• Each week → External Resources (links out)
• Each week → images (embedded assets)
To be “very detailed” without inventing systems that aren’t there:
• Break out each week folder as its own component (you have 9 modules including prework).
• two major user personas:
• Learner (consumer of content)
• Contributor/Maintainer (producer/curator of content)
• explicit external nodes:
• “Free resources”
• “Labs”
• “Templates”
• “Mini projects”