HackMD Slide Authoring

Produce Markdown that can be pasted into a HackMD note and presented in Slide mode. HackMD supplies the presentation shell and plugins; do not generate an HTML document, install reveal.js, or call Reveal.initialize().

Authoring workflow

1. Use the requested topic, audience, language, duration, and source material. Ask only for missing information that materially changes the deck; otherwise state a reasonable assumption. Preserve facts and citations when converting an existing note.
2. Build a narrative around the audience's takeaway: context, a few main ideas, supporting evidence or a demonstration, and a conclusion. Use one main idea per slide. Move detailed explanations into speaker notes or optional vertical slides rather than shrinking text.
3. Prefer short headings, brief bullets, small tables, and focused code examples. Use Markdown first. Add images, backgrounds, and fragments only when they help explain the content. Keep contrast readable and avoid animation on every element.
4. Read syntax and compatibility for settings, backgrounds, code highlighting, media, or advanced behavior. Adapt the six-slide example when a complete starting point helps; its length and outline are examples, not requirements.
5. Deliver the deck as Markdown. If a file location is requested, write a .md file with no enclosing code fence. In chat, use an outer fence longer than any code fences inside the deck so the user can copy the source intact. Keep usage instructions outside the deck.

Creating or editing a local deck does not require an online note. Create or update a HackMD note only when requested, using an available HackMD tool or CLI; keep account operations separate from content authoring.

Core syntax