Skip to content

Repo Purpose

oves-decks is the content and content-generation pipeline repo. It owns the content intent, the company-standard styles, and the tooling that turns intent into publishable artifacts (decks, scrolls, memos, training).

The technical stack — COS data buckets, EdgeOne CDN serving, and other infrastructure — is owned by the tencent-cloud repo. Its ADRs record those decisions (ADR-0011 URL strategy, ADR-0015 COS SPOT pipeline). This repo consumes that stack; it does not define it.

Responsibilities

  1. Content intent source — docs/decks/*.md intent documents are the authoring surface (WorkBuddy-facing) for decks, scrolls, memos, and training. They are upstream of the COS SPOT, not a replacement for it.
  2. Content-generation pipeline — scaffolding and build scripts that turn intent into artifacts: React/Spectacle decks, standalone scroll HTML, and self-contained decks.
  3. Company standard styles — reusable design system, page templates, content blocks, and deck templates that enforce visual and structural consistency.
  4. Git-tracked persistence for long-duration content — company presentations and multi-creator, long-lived content are versioned here and pushed through GitHub → Actions → COS.

Single origin, two persistence paths

oves-decks is the initiation point for both 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 intent (WB) → oves-decks push → GitHub Action → COS
Ad-hoc Individual, short-lived publications intent (WB) → local artifact → COS directly → EdgeOne serve

This mirrors ADR-0011 lifecycle rules: docs / decks / training / media are permanent (git-tracked); memo is short-lived (ad-hoc, auto-expires).

Audiences

  • Content creators building internal and external presentations, memos, and training materials.
  • Platform maintainers managing design standards and reusable primitives.