Repo Structure¶
Pipeline Position¶
oves-decks is the content and content-generation pipeline repo. The
technical stack (COS data buckets, EdgeOne serving) is owned by
tencent-cloud (ADR-0011, ADR-0015) and consumed here, not defined here.
oves-decks is the initiation point for both persistence paths. Intent is
authored here; the paths diverge only in how the artifact is persisted:
| Path | Content | Flow |
|---|---|---|
| Git-tracked | Company presentations, multi-creator long-duration content | push → GitHub Action → COS |
| Ad-hoc | Individual, short-lived publications | local artifact → COS → EdgeOne |
Authoring Map¶
docs/decks/: deck-intent documents (deck-design) that define each deck before code generation.docs/scroll/: scroll/memo-intent documents.src/shared/: centralized design core. Do not edit as a content creator.src/page-templates/: prop-driven reusable slide/page layouts.src/deck/: prop-driven content blocks and block registry (Spectacle/React).src/scroll/: HTML string block renderers (standalone scroll output).src/diagram/: shared SVG diagrams + chart pipeline (PlantUML, flow, venn, charts).src/deck-templates/: purpose-curated deck skeletons.src/deck-depot/: approved completed decks for team reuse.src/decks/: generated or maintained deck app implementations.
Docs Map¶
docs/: intent layer, library index, and authoring guidance.docs/decks/: one intent document per deck.docs/scroll/: one intent document per scroll/memo.docs/deck-intents.md: contract fordeck-designfiles.docs/page-templates.md: page style reference.docs/block-library.md: block style reference.docs/deck-templates.md: deck blueprint reference.docs/deck-depot.md: reader-facing deck index.