Curricula catalog / Forking for your role
Forking for your role
A curriculum repository is shared; a fork is where your personal work lives. The mechanics differ slightly by role.
On GitHub, a fork of a public repository is always public too — see keeping your fork private if you'd rather it wasn't (GitLab lets you choose at fork time).
Apprentices
- Fork the curriculum repo to your own GitHub or GitLab account (or just download it as a local folder).
- Open your fork in apprenti.dev with Clone repository.
- Your profile, tasks, reflections, and submissions live in your own personal folder inside your fork — never in the upstream repo.
Mentors
- Fork the curriculum repo — your fork pairs with the apprentice(s) you mentor.
- Give your apprentice access to that fork, then each of you opens it with Clone repository.
- Your reviews live in your own personal folder — the app never overwrites either side's personal data on sync.
Content Creators
- Fork a curriculum repo as a structural reference, or start from an empty repository with a single curriculum manifest file.
- Author tasks and modules by hand (JSON + Markdown) or visually with apprenti creator.
- Push to your own repository — there's no publish button. Sharing a curriculum is just sharing a Git repository.