This repository holds the slides and demos for Chris Ayers' talk Feature Flags: The Art of the IF and Deployment. The deck is published to https://chris-ayers.com/feature-flags/.
slides/: Marp deck using thecustom-gaiatheme, images inslides/img/, themes inslides/themes/.feature-flags.sln: demo solution withfeature-management/(Microsoft.FeatureManagement),appconfig-sample/(Azure App Configuration), andlaunch-darkly-sample/(LaunchDarkly).IaC/: Bicep for App Configuration and the demo web apps;Scripts/has helper scripts.docs/code-reference-validation.md: how the LaunchDarkly code-references workflow is validated.
-
Write the deck in Markdown with Marp.
slides/Slides.mdis the source;build/is generated output and is never edited or committed. -
Keep the frontmatter at the top of the deck:
--- marp: true theme: custom-gaia ---
-
Store themes in
slides/themes/and images and diagram sources inslides/img/. Prefer theme classes and CSS variables over inline styles. -
Write speaker notes as HTML comments (
<!-- -->). -
Render locally with the Marp CLI version the Pages workflow uses (latest):
npx @marp-team/marp-cli --theme-set slides/themes --html -o build/index.html -- slides/Slides.md npx @marp-team/marp-cli --theme-set slides/themes --html --pdf --allow-local-files -o build/Slides.pdf -- slides/Slides.md
-
.github/workflows/marp-pages.ymlbuilds the HTML deck andSlides.pdfand publishes both to GitHub Pages. If you add slide assets outsideslides/img/andslides/themes/, add them to the workflow's copy step.
Use the shared skills from codebytes/skills (for Copilot CLI: copilot plugin install https://github.com/codebytes/skills). Don't copy their instructions or scripts into this repository.
| Task | Skill |
|---|---|
| Write or revise slides, notes, order, or layouts | marp-authoring |
| Charts, Mermaid diagrams, or other visuals | marp-visuals |
Editable .drawio.svg diagrams (stored in slides/img/) |
drawio-diagrams |
| Check overflow, clipping, and HTML/PDF parity before presenting or publishing | marp-slide-review |
dotnet build feature-flags.sln
dotnet run --project feature-managementappconfig-sample/global.jsonpins an older SDK for that project; check it before upgrading packages.- LaunchDarkly SDK keys and App Configuration connection strings come from configuration or secrets; never commit them.
- Keep the readme sections in this order: Slides, Recordings, Resources, Contact.
- When a new recording of the talk is published, add it at the top of
## Recordingsas- [Event Year](https://www.youtube.com/watch?v=VIDEO_ID). When the video's title differs from the talk's, add an em dash and the recorded title after the event. Keep the list newest first. - The talk also appears on https://chris-ayers.com/speaking/ (source:
content/speaking.mdin codebytes/codebytes.github.io); new events and recordings belong there too.
- Keep changes scoped to the request; don't reformat unrelated slides or code.
- Never commit secrets, keys, or connection strings. Demo placeholders must be obviously fake.