Home: уточнение про размер backend-команды при полном frontend
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KMBAcnFBAAPsyJpaUVjNpF
Home: выбор frontend/backend для ОИ32, ОИ33, ОИ21 и новые размеры команд
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KMBAcnFBAAPsyJpaUVjNpF
Home: роли групп (frontend/backend) и максимальный размер команды
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KMBAcnFBAAPsyJpaUVjNpF
Add API contract guide, split spec template, finalize grading system
- New API-Contract-Guide.md: explains HTTP/API basics from scratch,
why backend and frontend need a contract, what backend must document
and when, what frontend needs and when, a worked endpoint example
from docs/examples/example_module, and a reconciliation checklist.
- Getting-Started.md: specification.md replaced with separate
specification-backend.md / specification-frontend.md per module
(chosen so contract mismatches are a real, checkable thing), links
to the new guide.
- Home.md: add API contract guide to the navigation list.
- Grading-System.md: fill in the full 100-point breakdown (15+10+20+10+35+10),
with defense in Module 3 serving as the exam, backend/frontend graded
separately except for the joint integration score.
Rewrite Home as a real landing/navigation page
Home.md was a single welcome line. Rewrote it as the actual entry
point: what the project is (one app, Python/FastAPI backend + plain
HTML/CSS/JS frontend, one DB, 7 modules), how the 14 teams are split
(backend + frontend per module), a step-by-step "how to work with
this" pointing at Getting Started -> Installation Setup ->
Git-GitHub-Guide -> Grading System -> FAQ in the order you'd actually
need them, links to the real architecture doc and the working example
(docs/examples/example_module + frontend/_example) in the repo, and a
full table linking every module's Design and Backend Tech Spec pages.
Also renamed Tech-Spec-Design-Student‐portal.md (used a U+2010 hyphen)
to Tech-Spec-Design-Student-portal.md, matching the plain hyphen used
by all 13 other Tech Spec pages — needed a consistent, guessable name
to link to from the new table.
Fix broken links, module paths, and add missing referenced pages
- Home.md: fixed repo name (was "College_Management_System2131",
actual repo is "College_Management_System").
- Getting-Started.md: fixed Issues link (same repo name mismatch),
fixed self-referencing broken link (was pointing to a dead
"Начало-работы" slug instead of Installation-Setup), updated module
folder paths to match the renamed modules/admin_panel,
modules/student_portal, modules/teacher_portal (underscores instead
of hyphens, since hyphens aren't valid in a Python import path).
Documented the new docs/examples/example_module/ reference pattern.
- Installation-Setup.md: replaced the placeholder clone URL
(your-org/college-management-system) with the real repo URL and
correct folder name, removed the mention of PyJWT as an installed
dependency (dropped as unused/redundant, see the main repo's latest
commits).
- Added Git-GitHub-Guide.md, Grading-System.md, FAQ.md as minimal
placeholder pages — both Getting Started and Installation Setup
already linked to these three pages, but they didn't exist yet.
Left as short placeholders (not full guides) since grading policy
and git workflow specifics are the instructor's call, not something
to fabricate.
- Added Tech-Spec-Design-Curriculum.md, Tech-Spec-Design-Reports.md,
Tech-Spec-Design-Teacher-portal.md, Tech-Spec-Design-Admin-panel.md,
matching the existing minimal one-line style of
Tech-Spec-Design-Gradebook/Schedule/Student-portal, so all 7 modules
have a page (still just placeholders for teams to fill in via their
own ТЗ, not pre-written specs).