π€οΈ Part of Galhoom Path Β· Track 1 β Study (global blueprint)
This repository belongs to the Galhoom Path organization (Study Β· Foundations Β· Problem Solving Β· Interview Prep Β· Projects). It is the shared template for every Study-track repo.
β Organization home
This repository holds the shared blueprint used by every study repo in galhoom-path.
One file drives the method:
π template.md
It defines Lectures β Interview Questions β Visual Maps β Final Project, naming rules, tutor/student roles, living-repo updates, series-without-overlap, and the AI prompt to generate a new subject repo.
01-Lectures/ β learn
02-Interview-Questions/ β explain
03-Visual-Maps/ β see / map the system (Mermaid in map.md β must look clear on GitHub)
04-Final-Project/ β build
| Track | Job |
|---|---|
| Lectures | One concept per session Β· analogy first Β· learner writes every line |
| Interview Questions | Subject-mapped Q&A (β org Track 4 Interview Prep) |
| Visual Maps | Flows, sequences, layers Β· GitHub-clear Mermaid Β· last map = end-to-end system view |
| Final Project | Capstone milestones (β org Track 5 practice builds) |
Learn β Explain β Map β Build. A track starts only after the previous trackβs Review Checklist is complete.
| Without a global template | With this repo |
|---|---|
| Each study repo drifts into its own rules | One official method for PHP, OOP, OOD, Design Patterns, Laravel, β¦ |
| Hard to remember which copy is newest | This repo is the source of truth |
| New subjects start from memory | New subjects start by copying template.md |
Improve the method in any study repo
β
βΌ
1. Update template.md HERE first (study-template)
β
βΌ
2. Copy the same change into every active study repo's template.md
(and .cursor/rules/template-sync.mdc when Section 19 changes)
β
βΌ
3. Bump "Template last synced" date in this file to today
Never leave a study repoβs template.md newer than this one without pushing the change back here.
When you only change subject content (lectures, questions, maps, project) β do not touch this repo.
When you change structure, conventions, or method β update this repo in the same change.
- Create an empty public repo under
galhoom-path(for examplephp-ood). - Copy
template.mdinto the new repo root. - Copy
.cursor/rules/template-sync.mdcfrom Section 19 oftemplate.md(or from an existing study repo). - Fill the placeholders in Section 2 of
template.mdfor the new subject (including{{MAP_COUNT}}). - Paste the AI prompt from Section 18 into a new chat, attach
template.md, and generate the scaffold. - Add the new repo to the Learning Series table on the org homepage.
- Link Comes after / Leads to to the neighboring repos β no repeated lessons.
The scaffold creates four tracks: 01-Lectures/ β 02-Interview-Questions/ β 03-Visual-Maps/ β 04-Final-Project/.
| Repo | Role |
|---|---|
| php-fundamentals | Series 1 β core PHP Β· π’ Active |
| php-oop | Series 2 β OOP Β· π’ Active |
php-ood |
Series 3 β OOD (SOLID / GRASP) Β· β¬ Planned |
php-design-patterns |
Series 4 β Design Patterns Β· β¬ Planned |
| Laravel, Filament, β¦ | Series 5+ Β· β¬ Planned |
Each of those keeps its own copy of template.md so the repo stays self-contained for learners and AI tutors. This repo is where the shared method is maintained.
study-template/
βββ README.md β you are here
βββ template.md β the global Galhoom Study Method blueprint
No lecture folders. No student practice files. Method only.
@Galhoom22 Β· Organization: galhoom-path
π Read. βοΈ Write. π¬ Explain. πΊοΈ Map. ποΈ Build. π Master.