Updated Tech Spec Design Student portal (markdown)
Add ТЗ structure/template to all 14 Tech Spec pages (backend + design) Each page now has the section skeleton to fill in (purpose, functional requirements, API endpoints, DB structure or screens/wireframes, acceptance criteria) instead of just a title stub. Sections in brackets are prompts, not content - teams still write everything specific to their own module themselves. Backend and Design templates differ (DB/API focus vs screens/API-consumer focus) and both point to the API Contract Guide for the shared 4.1 section.
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.