Code reference detail
decks
presentations/decks/
| Idea | Status | Tags | Summary |
|---|---|---|---|
| slide_pack_format | Each published episode that ships a deck declares an `@slides` list. Each slide item is an anonymous block with: - id — stable slide handle - transition — reveal transition name per [slide_transitions] - background — theme key per [slide_visual_system] - kicker / heading / body — on-screen copy ( minimal ) - code / code_lang — optional fenced snippet shown on the slide - asset — key into [presentation_assets] - fragments — optional comma-separated fragment labels ( fade-in ) - notes — speaker notes, usually the VO lines from `@script` Authored deck JSONC under ["../../presentations/decks/"] is the editable source of truth derived from `@slides`. Authored catalog JSONC: ["../../presentations/manifest.jsonc"]. Runtime deck JSON consumed by [site_reqs.presentation_player_route] is generated from those JSONC sources. Standalone Reveal shell ( optional local serve ): ["../../presentations/player/"] Site embed and lesson routing follow [site_reqs.tutorials_section] and [site_reqs.presentation_player_route]. | ||
| tutorial_format | Production bar — every episode idea below must carry all of: - Audience, Outcome, Runtime ( always present — including advanced packs ) - Demo — explicit pre-state of `reqlan-tutorials-demo` at cold open ( files present, caret, UI already open ) - Related — feature requirement links the episode proves; `@todo` if a demoed surface is not `@status done` - `@example` — full recreateable fixture ( multi-file when the beat needs it ), fenced as opaque snippets when the sample itself contains braces - `@script` — caption-ready spoken VO plus screen directions ( VO = voiceover; SCR = what to show ). Structure: cold open → teach beats → misconception or recovery beat → try-this → end card. Use exact Command Palette / chat paths. VS Code is primary; note Cursor skill / chat alternate when AI tools differ. Use SCR: / VO: labels, not bracket tags, so they are not parsed as [reference] links. Prefer denser beats over stretching runtime. - `@slides` — one slide per major SCR beat ( ~ 7 – 10 ). Title, teach, try-this / end. `notes` = VO lines from `@script`. Authored Reveal JSONC under ["../../presentations/decks/"] is derived from `@slides` and may add JSONC-only fields ( `code_label`, dual-pane `code` / `code_b` ) for contrast beats. Episodes are self-contained; series order is recommended: get-started → concepts → advanced. After get-started 01 – 02, later get-started episodes can be sampled; concepts packs assume the loop was felt at least once. Prefer 1080 p screen capture with a small inset face cam optional; logo end-card with site / marketplace links from [phonebook]. Stay inside stated runtimes where possible ( get-started ~ 4 – 7 min, concepts ~ 8 – 12 min, advanced ~ 8 – 12 min ). | ||
| tutorials | draft | marketing, media, tutorials | Tutorial media teaches reqlan through short, scripted videos plus copy-pasteable `.rq` examples. Content must reflect [mission_statement]: semantic requirements as code for people working with LLMs, with ergonomic definition and consumption. Three series — do, then name, then craft: - [get_started_series]: first-hour fluency ( write, link, create a [base], neighbourhood, AI slice, code ). - [concepts_series]: ontology vocabulary, an [extension] surface map, and the [cli_package] headless surface after the learner has felt the loop. - [advanced_series]: graph craft, AI workflows, distribution. Host on the marketing site per [site_reqs.tutorials_section] and link from extension onboarding per [installation_event] and [phonebook]. Visual language follows [brand]; on-screen chrome stays quiet per [show_dont_tell] — narration carries concepts, UI does not lecture. |
Reference labels
../../presentations/decks/