Appearance
ediky-website
The Ediky product: React SPA, Cloudflare Pages Functions, Workers and question-bank content.
ArchitectureHow the repository is structured and how its parts interact.ModulesModules and packages, one page each.ComponentsUI and service components, one page each.FunctionsImportant functions and helpers.APIsEndpoints, commands and service interfaces.ConfigurationEnvironment variables, config files and secrets.DependenciesOther repositories, services and packages it relies on.ContributingLocal setup, workflow, standards and release.
What this repository is
TODO: Two to four sentences: what this repository is responsible for, who or what depends on it, and where it sits in the Ediky ecosystem.
At a glance
| Field | Value |
|---|---|
| Repository | EdikyLab/ediky-website |
| Primary language | TODO |
| Runtime / hosting | TODO |
| Deploys to | TODO |
| Owners | TODO |
| Status | TODO: active / maintenance / experimental |
Tech stack
TODO: Languages, frameworks, key libraries, build tooling and hosting.
Repository layout
TODO: Top-level folders, one line each.
text
ediky-website/
├── TODO/ TODO: purpose
├── TODO/ TODO: purpose
└── TODO TODO: purposeGetting started
TODO: Prerequisites, then the commands to install, run and test locally. Details go in Contributing.
bash
# TODO: clone, install, runExisting guides
Long-form guides written before this section existed. They keep their original URLs and are listed in the sidebar under Guides. Start here:
- Website: Complete Workflow
- Core UI Features: Dashboard & Progress Tracking
- Code Execution & DSA: Judge0 & Code Execution
- OA Simulator & Integrity: OA Structure & Timer Logic
- Backend & Infrastructure: API Reference (Functions)
Related documentation
- Architecture
- Repository dependencies
- Cross-repository data flow
- TODO: Links to the repositories this one talks to.