How turntabl/git-training works
Project type and purpose
• Project type: Open-source training/documentation repository.
• Purpose: Provide a set of discrete, hands-on Git exercises (each in its own folder) plus a central README and cheatsheet.
Top-level structure analysis
• Root directory: contains the master README.md (project overview & cheatsheet).
• Subdirectories: one per exercise (e.g., basic-commits, basic-staging, basic-branching, etc.), each with its own README.md.
• No code, no build scripts, no runtime components—pure content.
a. Repository container (“git-training” on GitHub)
b. Central README + Cheatsheet
d. External Actors / Services:
• Learner (clones the repo, works locally)
• Tutor/Reviewer (clones or browses remotely)
• Git CLI & Local Git Engine
• GitHub (remote host)
Relationships & data flows
• Tutor → GitHub (reviews pushed branches or PRs)
Design principles
• Modular content: each exercise is self-contained in its own directory.
• Single source of truth: all instructions and reference commands live in Markdown files under version control.
• Extensibility: new exercises can be added as new folders without altering existing structure.
Technologies & frameworks
• Markdown (documentation format)
• Git (version control)
• GitHub (hosting & collaboration)
• Local file system (as the “runtime environment” for exercises)
• Optional notes on the side: “Add more exercises by creating new folders under /basic-commits, etc.”
• The modular folder structure of git-training
• How users interact with it via Git and GitHub