Documentation structure
Repository layout
Section titled “Repository layout”| Path | Purpose |
|---|---|
src/content/docs/fa, src/content/docs/en |
Bilingual public content |
src/styles/custom.css |
Typography, RTL/LTR, and presentation rules |
docs/adr/ |
Architecture decisions |
docs/architecture/ |
Ownership model, source contract, localization, deployment design |
contracts/ |
Internal publishing/integration contract definitions (no sync implementation in this phase) |
scripts/validation/ |
Build, link, i18n, and search checks |
.gitlab-ci.yml |
CI validation |
Ownership boundary
Section titled “Ownership boundary”- Service repositories: authoritative contracts, Schema/CRD, internal architecture, and service-tested examples.
aidin-docs: public documentation experience, customer guides, cross-service tutorials, bilingual navigation, and public reference presentation.aidin-landing: marketing messaging, product discovery, and links to documentation.
Future contracts must be consumed from immutable, verified artifacts (pinned commit/release); arbitrary default-branch fetches during production builds are not allowed.