Runi Workshop Program

Working Handbook — Clover Technology

Preface

This book is the working handbook for Runi, Clover Technology’s AI workshop and delivery programme. It is written while the programme is still being built, so treat it as a live planning document first and a reference second. Over time, as the plans firm up into a run curriculum, this same book will evolve into the participant textbook handed to workshop attendees, so write with that eventual audience in mind, not just the internal team.

Who authors this

Each department head owns the chapters closest to their function: IT (Ted) writes the delivery, technical, and infrastructure chapters; Marketing and PD write the funnel, curriculum, and go-to-market chapters. Ted is chief editor, responsible for structure, cross-references, and keeping the whole book internally consistent, but not for rewriting anyone’s domain content.

If you notice a chapter conflicts with another (a number, a date, a decision that was superseded), flag it in the chapter or raise it with Ted rather than silently editing around it.

How to contribute

There are two paths in, pick whichever matches how you already work.

Technical: edit the .qmd files directly

Every chapter is a .qmd file under chapters/. Quarto documents are Markdown plus a few extras: normal headings and paragraphs, tables, blockquotes, and callout boxes (::: {.callout-note} ... :::) all work as you’d expect. Cross-references use the @sec-id syntax (e.g. @sec-funnel links to the funnel chapter), so link between chapters instead of repeating content. Diagrams can be written as text and rendered automatically using fenced ```{mermaid} blocks, no separate diagramming tool needed. Edit the file, save, and (once Quarto is installed, see README.md) run quarto preview from the book/ folder for a live-reloading preview as you write.

Non-technical (Marketing / PD): edit in your browser, nothing to install

You do not need Quarto, Markdown, Word, or git. Open the chapter on GitHub, click Edit, type your changes (there’s a live Preview tab), and click Propose changes — that creates a branch and a pull request automatically for you and Ted to review before it merges. The full step-by-step is in CONTRIBUTING.md. If a draft already exists as a Word file, you can still drop it in the shared folder and an AI session converts it into a chapter branch for review — but for day-to-day writing the browser editor is the simpler path.

House style

• Bilingual by convention. Content is written in English for technical material, with Chinese business terms kept inline where they are the precise or original term (e.g. 落地方案, 闭环). Do not translate these away, they carry meaning the English gloss doesn’t fully catch.
• One H1 per chapter. Each .qmd file has exactly one top-level heading, the chapter title. Everything else inside the chapter is H2 or deeper.
• Every module chapter ends with a 落地方案 section. Mirroring the reference programme this handbook draws on (see 4  Reference: 品誉咨询 Workshop Model & Source Material), any chapter that teaches a module of the workshop curriculum must close with a concrete, actionable 落地方案 (landing plan), what the reader does with this at home or at work, not just what they learned.