mdeck 2.3.0

package/docs/site/content/theme-repository.md

@@ -0,0 +1,76 @@
+# Install or share a theme
+
+Besides the themes and palettes that come with mdeck, other people share theirs in the **theme repository**: <https://github.com/tilman-schieber/mdeck-themes>. A shared theme or palette comes as a **pack**: one theme with the palettes made for it, or a set of palettes.
+
+## Find and install one
+
+See what there is:
+
+```sh
+mdeck themes search
+mdeck themes search warm
+```
+
+Install a pack beside your slides:
+
+```sh
+mdeck themes install solarized my-talk.md
+```
+
+It is copied into the `extensions` folder next to `my-talk.md`, like a theme you made yourself, so the slide folder keeps working on any computer. Then choose it in the deck settings (`palette: solarized`) or in the editor's **Deck** tab.
+
+The design page has the repository too: open it with `mdeck design my-talk.md`, and under **From the theme repository** press **Show what others made**. Each pack shows a picture and an **Install** button.
+
+## For every deck
+
+With `--global`, a pack is installed once for all your decks, in a folder in your home folder (`~/.mdeck/extensions`):
+
+```sh
+mdeck themes install solarized --global
+```
+
+A slide file that uses it works only on your computer. `mdeck check` reminds you, and `mdeck themes install solarized my-talk.md` puts a copy beside the slides. When a deck has its own copy, that one is used.
+
+## Update and remove
+
+```sh
+mdeck themes list my-talk.md       # what is installed, here and for every deck
+mdeck themes update my-talk.md     # newer versions of everything installed here
+mdeck themes remove solarized my-talk.md
+```
+
+Add `--global` to work on the packs for every deck. If you changed an installed file by hand, `update` and `remove` stop and tell you which one, so your change is not lost; add `--force` to go ahead anyway.
+
+## What a pack may contain
+
+Packs hold only theme and palette settings (`extension.toml`) and theme stylesheets (`styles.css`). They never contain code that runs in your slides. Fonts may come only from Google Fonts or Bunny Fonts, and stylesheets may not load anything from the web. mdeck checks this again when it installs a pack, and refuses a pack that does not match the checksum the repository lists for it.
+
+## Share your own
+
+1. Make the theme or palette as described in [Create a theme or palette](theme-authoring.html), and fine-tune it with `mdeck design`.
+2. Fork the theme repository and add a folder `packs/<your-pack>/` with a `pack.toml` and one folder per theme or palette:
+
+```text
+packs/
+  harbour/
+    pack.toml
+    harbour/             a theme
+      extension.toml
+      styles.css
+    harbour-night/       its palette
+      extension.toml
+```
+
+```toml
+schema = 1
+id = "harbour"
+title = "Harbour"
+description = "Navy and brass, with a serif for headings."
+version = "1.0.0"
+author = "Your Name"
+license = "MIT"
+mdeck = ">=2.3.0"
+```
+
+3. Check it the way the repository will: `mdeck themes build packs -o site --check` shows every theme and palette in the pack on every kind of slide, light and dark, and fails on text that does not fit or is hard to read.
+4. Open a pull request. Once it is merged, `mdeck themes search` lists it. For a new version, raise `version` in `pack.toml`.

package/docs/site/content/troubleshooting.md

@@ -0,0 +1,92 @@
+# When something goes wrong
+
+Most problems come from a filename, a small settings mistake, or a preview that is no longer running. Start with the message you see below.
+
+If an AI assistant wrote or changed the slides, ask it first. It can run `mdeck check`, read the message and fix the file:
+
+```prompt
+The picture on the title slide is missing. Run mdeck check and fix
+what it reports.
+```
+
+## The command is not recognized
+
+If the terminal cannot find `mdeck`, open the mdeck project folder and run `npm link`. Close and reopen the terminal if needed, then try `mdeck --help`.
+
+If it cannot find `npm` or `node`, Node.js needs to be installed or made available in your terminal first. Ask the person who manages your computer if you do not normally install software yourself.
+
+You can still run the checkout directly from its project folder with `node bin/mdeck.js --help`. This runs the same command.
+
+## The slide file cannot be found
+
+Check that the terminal is open in the folder containing your talk. Look at the filename carefully: a plain-text editor may have saved `my-talk.md.txt` instead of `my-talk.md`.
+
+For a file in another folder, give its path:
+
+```sh
+mdeck run "talks/my garden talk.md"
+```
+
+## The preview does not update
+
+Save the slide file, and check that the terminal running `mdeck run` is still open. Make sure you are viewing the browser address printed by that command.
+
+If you changed the file's name or moved it, stop the old preview with `Ctrl+C` and start it with the new path.
+
+## It says the port is in use
+
+This is usually harmless. Another local preview is using that address, so mdeck chooses the next available port. Open the address shown in the terminal, for example `http://localhost:5174/`.
+
+“Re-optimizing dependencies” is also a normal development message after mdeck's setup changes. You do not need to do anything.
+
+## It mentions files in the public directory
+
+This warning can appear for deck-local layout files in the current slide development server. It comes from how that server serves the presentation folder. If the slides render, you do not need to rewrite the paths suggested in the warning.
+
+It is a known slide-preview configuration issue; the documentation server is separate. If a layout fails to render, check for a more specific error below the warning and run `mdeck check my-talk.md`.
+
+## A picture is missing
+
+Check its path relative to the slide file, including capital letters. For `./img/garden.jpg`, there must be an `img` folder beside the slide file with `garden.jpg` inside it.
+
+Run `mdeck check my-talk.md` for a list of missing local assets. If you are opening a built presentation, keep the whole output folder together.
+
+## There is a settings error
+
+A message such as `my-talk.md:12:1` points to line 12, column 1 of your file. Look there for a missing quote, an incorrect setting name, or inconsistent spaces.
+
+Use spaces rather than tabs. Quote text with punctuation, such as `title: "Plans: a fresh start"`.
+
+For new slides, a settings block should begin with `:::meta` and end with `:::`. Content goes underneath it. A notes or slot block also needs its own closing `:::`.
+
+## Text is missing or does not fit
+
+A slide has a fixed amount of space. Split a long explanation over two slides, shorten a paragraph, or try a simpler layout. The current checker does not automatically detect visual overflow; tell your assistant which slides overflow.
+
+If you see an “unknown region” error, check that the layout supports the named area you used. For example, `left` and `right` work with `split`, but not with `title`.
+
+## The colors change back
+
+Appearance changes in the presenter view are temporary. Save the theme and palette you want in your slide file's settings. See [Change the look](appearance.html).
+
+## A video or live example does not work offline
+
+Online videos and live Python need a network connection. A self-contained build embeds local media; it does not download an entire external service. Use a local video file if you need to play it offline.
+
+## Phones cannot open the poll
+
+The QR code points at your computer when you present with `mdeck run my-talk.md --network`. The phones must be in the same network. Many large Wi-Fi networks, often at universities, do not let devices reach each other, even when both are connected.
+
+Try a phone hotspot that both your computer and the phones join, or use a server on the internet as described in [Ask your audience](audience.html#use-it-in-a-real-session). If the slide says phones cannot reach it, you started without `--network`.
+
+## I want an earlier version of my slide file
+
+Before its first change in each session, the visual editor saves a copy of the file in a `.mdeck-backups` folder next to it, named with the date and time. Open the copy you want, and copy the text you need back into your slide file. The folder may be hidden in your file manager because its name starts with a dot.
+
+## A component from another folder is missing
+
+If a tag such as `<chart />` shows nothing, run `mdeck check my-talk.md`. It reports a folder listed under `components:` that does not exist. Paths are relative to the slide file. The tag is the file name in lowercase: `<chart>` comes from `Chart.jsx` or `chart.jsx`. See [sharing components between decks](components.html#share-components-between-decks).
+
+## Still stuck?
+
+Keep the exact error message and a small copy of the slide that causes it. Include the command you ran and whether the problem happens in the live preview or a built file. Those details make it much easier for someone, or an AI assistant, to help.

package/docs/site/content/views.md

@@ -0,0 +1,56 @@
+# Views, commands and servers
+
+mdeck has a few commands that start a server or make files, and a few views of the same slides that you choose in the browser. This page puts them side by side.
+
+## Views
+
+Every build and every preview contains all views. The address picks one with `?view=`:
+
+| Address | View | For |
+|---|---|---|
+| `?view=deck` | Standalone slides with drawing controls | Slides opened from the reader view or a built file |
+| `?view=presenter` | Current and next slide, notes and timer, and a button that opens the audience window | You, while presenting |
+| `?view=audience` | Slides without notes, with navigation synced to the presenter view | The projector |
+| `?view=reader` | The reader view: an outline, **Slides** and **Read** modes, a **Look** menu and a PDF | People you send the talk to |
+
+Ways to switch between them:
+
+- The **Overview** link in the corner of the deck opens the reader view. Its outline is the overview of all slides.
+- **Present** in the reader view opens standalone slides at the current slide.
+- The presenter view's audience-window button opens the audience view in a new window. Navigation in either window updates the other, in the same browser or on a paired iPad: see [Draw on your slides](drawing.html#present-from-an-ipad).
+- The launch page of `mdeck run`, at the preview's plain address, offers Presenter, Audience and Reader. Its presenter and audience buttons belong together.
+- Fullscreen is a control inside a view (**F** or its fullscreen button). For a single screen, use the presenter view's slide-only layout.
+- A poll's QR code opens the server's answer page, not the slides: see [Ask your audience](audience.html).
+
+## Commands
+
+| Command | What it does | Where it runs |
+|---|---|---|
+| `mdeck run my-talk.md` | Preview that reloads when you save; launch page; server for polls | Your computer. Add `--network` to reach it from phones in the same network, or `--server` to reach it from an iPad on any network through your own server |
+| `mdeck edit my-talk.md` | Visual editor that saves into the file and keeps a backup | Your computer only. The launch page can start it too |
+| `mdeck build my-talk.md` | A `dist` folder to host or copy | Anywhere afterwards; no mdeck needed |
+| `mdeck send my-talk.md` | One file to send, without notes, with a PDF inside | Opens on its own |
+| `mdeck pdf my-talk.md` | A PDF, one page per slide | Needs Chrome or Chromium while building |
+| `mdeck server` | The server for polls in hosted presentations, and for presenting from an iPad through it | A web server |
+| `mdeck docs` | These guides | Your computer |
+
+The [command guide](commands.html) lists every option.
+
+## What needs a server
+
+**Presenting.** While you work, use `mdeck run`. A built folder can be presented from any ordinary web server; `mdeck build my-talk.md --launchers` adds a small one that needs Python. A self-contained file for readers opens on its own.
+
+**Editing and the launch page.** These run only while `mdeck edit` or `mdeck run` is running, and only answer on your own computer.
+
+**Polls.** Only a server must be reachable by the phones; they never load the slides. You present from your own computer, with the slides as they are right now.
+
+| Situation | Server | Settings |
+|---|---|---|
+| Rehearsing, small group | Built into `mdeck run my-talk.md --network` on your laptop | None. Phones must be in the same network |
+| Lecture hall | `mdeck server` on a web server, once for all your talks | `server`, and the key `MDECK_SERVER_KEY` when you start `mdeck run` |
+
+Many large Wi-Fi networks do not let devices reach each other. If phones cannot reach your laptop, use a phone hotspot or a server on the internet. Details are in [Ask your audience](audience.html).
+
+**Drawings.** `mdeck run` saves them in `my-talk.drawings.json` next to the slides. An iPad next to your laptop pairs with `mdeck run --network` through a QR code on the launch page, or from any network with `mdeck run --server`; the audience window on the laptop then follows it. See [Draw on your slides](drawing.html).
+
+**PDFs.** Only building one needs Chrome. The PDF shows interactive slides finished. Polls show the answers the deck's `server` had at that moment; without one, they show their question and options, marked as answered live during the talk.

package/docs/site/content/welcome.md

@@ -0,0 +1,71 @@
+# Make your next presentation.
+
+Bring what you already have: old PowerPoint slides, a PDF, a Word document, a paper, or a page of notes. An AI assistant turns it into a clean, well-designed deck, and mdeck presents it in a web browser, with your notes, and sends it as one file or a PDF.
+
+The content stays yours. The assistant works from your material, not from its own idea of the topic: it chooses layouts, tidies wording, moves detail into speaker notes and checks the file. You do not need to know how to program. The slides are a plain text file, so you can read every word, change any of it yourself, or ask for something different.
+
+[Make your first presentation](getting-started.html)
+
+<!-- preview -->
+
+## Bring your material, then shape it
+
+Put your files in a folder, open your assistant there, and point it at them:
+
+```prompt
+/write-slides Turn lab-notebooks.pptx and my notes in notes.md into
+a 15-minute talk for new lab students. Keep my examples, reuse the
+photos from the old slides, and add one poll at the start.
+```
+
+The assistant reads your files, keeps your structure, facts and pictures, picks a layout for each slide, writes speaker notes from what you wrote, checks the file with mdeck, and tells you how to open it. From there you keep talking: “make slide 4 a big statement”, “use a dark look”, “the third section of the PDF is missing”.
+
+## The slides are a text file
+
+mdeck slides are written in Markdown, the format AI assistants already answer in. That is why they are good at it: no slide software to operate, no file format to reverse-engineer, just the kind of text they write all day. What the assistant writes looks like this:
+
+```markdown
+# A small idea
+
+Every good talk starts somewhere.
+
+---
+
+# What comes next?
+
+- Explain the idea.
+- Show an example.
+- Invite questions.
+```
+
+The `#` makes a heading. The line with `---` starts another slide. A dash before a sentence makes a list item. Knowing these few marks lets you fix a word in seconds without asking anyone. [Read and adjust your slides](writing.html) explains the rest.
+
+## Find what you need
+
+- **Starting from scratch?** Follow [Make your first presentation](getting-started.html).
+- **Already use an AI assistant?** [Work with an AI assistant](claude-skill.html) shows how to set it up for mdeck and how to ask for good slides.
+- **Already have a slide file?** Learn to [add pictures](pictures-and-video.html) or [change the look](appearance.html).
+- **Getting ready to speak?** Set up [your notes and audience screen](notes-and-presenting.html).
+- **Want the room to take part?** [Ask your audience](audience.html) with polls, scales, word clouds and open questions they answer on their phones.
+- **Want to mark up a slide?** [Draw on your slides](drawing.html) with a pen, a finger or an iPad pencil, live or ahead of time.
+- **Sending your talk to someone?** Choose a [sharing or printing option](sharing.html).
+- **Which view or server do I need?** See [Views, commands and servers](views.html).
+- **Something looks wrong?** Try [the troubleshooting guide](troubleshooting.html).
+
+## What mdeck does today
+
+mdeck gives you ready-made slide layouts, different visual themes, speaker notes, pictures, videos, a separate presenter view, drawing on slides (also from an iPad), polls and other questions your audience answers on their phones, and a reader view with a PDF for people you send the slides to. It can also use layouts, themes and colors made for your team, and your assistant can make new ones for a single talk.
+
+`mdeck run` opens a launch page for your talk with all of this in one place: the presenter view, the editor, these guides, buttons that make the files to share, and a check for missing pictures.
+
+Whoever writes the slides, your assistant, a text editor, or the built-in browser editor (`mdeck edit`), the file stays the single copy, and the preview updates as it changes.
+
+## Keep this guide nearby
+
+Open these pages again with:
+
+```sh
+mdeck docs
+```
+
+The documentation runs on your own computer. No account or hosted service is needed.

package/docs/site/content/writing.md

@@ -0,0 +1,121 @@
+# Read and adjust your slides
+
+Whether your assistant wrote the slides or you did, they are a plain text file in **Markdown**: a way to add simple formatting to plain text. A few marks alongside the words tell mdeck what is a heading, a list, or a new slide.
+
+You do not have to write Markdown yourself. But knowing these marks lets you read what the assistant wrote, check it, and fix a word or a number without asking. Markdown is also what AI assistants write most naturally, which is why mdeck uses it.
+
+## Headings and paragraphs
+
+Put `#` and a space before the main heading. Use `##` and a space for a smaller heading. Leave a blank line between paragraphs.
+
+```markdown
+# Our next adventure
+
+This is a paragraph of ordinary text.
+
+## Where we are going
+
+This paragraph explains a little more.
+```
+
+Keep each slide focused on one idea. If your words do not fit, make another slide rather than making all the text smaller.
+
+## Start another slide
+
+Write three dashes on a line of their own:
+
+```markdown
+# The first idea
+
+Some words about it.
+
+---
+
+# The next idea
+
+Some more words.
+```
+
+## Lists, emphasis, and links
+
+| You write | What it means |
+|---|---|
+| `- A point to remember` | A bullet point |
+| `1. First step` | A numbered list item |
+| `**important words**` | Bold words |
+| `*a little emphasis*` | Emphasized words, styled by your theme |
+| `[Visit our website](https://example.com)` | A clickable link |
+
+Put each list item on its own line:
+
+```markdown
+- Bring a notebook.
+- Ask **one good question**.
+- Share what you learn.
+```
+
+## Give a slide some settings
+
+You can tell mdeck which layout to use. Put this small settings block at the beginning of a slide:
+
+```markdown
+:::meta
+layout: focus
+:::
+# One idea worth remembering.
+```
+
+The opening `:::meta` and closing `:::` mark the settings. The line between them asks for the `focus` layout: a large statement slide. The words beneath the block are the slide's content.
+
+You do not need a settings block on every slide. The [layout guide](layouts.html) gives you complete examples to copy.
+
+## Give a slide a lasting link
+
+Add an `id` when you want to link directly to a particular slide:
+
+```markdown
+:::meta
+id: questions
+:::
+# Your questions
+```
+
+You can then add `#questions` to the presentation's address. IDs must be unique within the talk and start with a letter. Use letters, numbers, hyphens, or underscores, with no spaces.
+
+## Settings for the whole presentation
+
+A settings block at the very top of the file controls the whole presentation. It uses `---` around its contents:
+
+```markdown
+---
+theme: neue
+palette: swiss
+meta:
+  title: "Our next adventure"
+  author: "Alex Morgan"
+---
+
+---
+:::meta
+layout: title
+:::
+# Our next adventure
+## A plan we can share
+```
+
+Keep the spaces before `title` and `author`: they put those values inside the `meta` group. Use spaces rather than tabs. Quoting text is helpful when it contains punctuation.
+
+For a talk in German, add `lang: de` to these settings. The page is then marked as German, which helps screen readers and hyphenation, and the words mdeck adds for your audience, such as the buttons for readers and polls, are German too.
+
+## Reading older examples
+
+Older decks put slide settings between `---` lines too:
+
+```markdown
+---
+layout: focus
+---
+# One idea worth remembering.
+```
+
+This still works. For new slides, the explicit `:::meta` form makes it easier to see where settings end and writing begins.

package/docs/site/examples/first-talk.md

@@ -0,0 +1,88 @@
+---
+theme: editorial
+show:
+  organization: none
+  author: none
+---
+
+---
+:::meta
+layout: title
+id: hello
+:::
+# Write it down.
+## Why every lab keeps a notebook
+
+:::notes
+Ask who has ever repeated an experiment because nobody remembered how it was done.
+:::
+
+---
+:::meta
+layout: split
+props:
+  ratio: [1, 1]
+:::
+# A notebook answers three questions.
+
+- What did I do?
+- What did I see?
+- What would I change?
+
+:::notes
+Everything else in a good notebook serves one of these three questions.
+:::
+
+---
+:::meta
+layout: focus
+attribution: "A saying in many labs"
+:::
+# If it is not written down, it did not happen.
+
+---
+:::meta
+layout: chapter
+number: 1
+part: "Good habits"
+:::
+# Write as you work.
+
+Two habits that make a notebook useful a year later.
+
+---
+:::meta
+layout: split
+props:
+  ratio: [1, 1]
+:::
+# Two habits that pay off
+
+:::slot left
+## Date every page
+The date and the experiment's name come first, before anything else.
+:::
+
+:::slot right
+## Record what went wrong
+Failed runs explain the successful ones. Never tear out a page.
+:::
+
+---
+:::meta
+layout: image-text
+image: ./notebook.svg
+alt: "An open lab notebook with written steps, a results table and a plot"
+:::
+# One page per experiment
+
+Aim, materials, steps, results and a short conclusion. Glue in printouts so nothing gets lost.
+
+---
+:::meta
+layout: full-bleed-image
+image: ./notebook.svg
+alt: "An open lab notebook with written steps, a results table and a plot"
+overlay: true
+:::
+# Your future self will thank you.

package/docs/site/examples/notebook.svg

@@ -0,0 +1,58 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="1000" viewBox="0 0 1600 1000">
+  <!-- An open lab notebook on a dark desk: ruled pages with entries, a results table, a plot and a pen.
+       The lower part of the picture stays dark so a heading can sit on it. -->
+  <defs>
+    <linearGradient id="desk" x1="0" y1="0" x2="0" y2="1">
+      <stop offset="0" stop-color="#4a3b30"/>
+      <stop offset="1" stop-color="#211a15"/>
+    </linearGradient>
+    <linearGradient id="spine" x1="0" x2="1">
+      <stop offset="0" stop-color="#fbf8f1" stop-opacity="0"/>
+      <stop offset=".5" stop-color="#b9ad98"/>
+      <stop offset="1" stop-color="#fbf8f1" stop-opacity="0"/>
+    </linearGradient>
+    <pattern id="rule" width="10" height="40" patternUnits="userSpaceOnUse">
+      <line x1="0" y1="39.5" x2="10" y2="39.5" stroke="#bfd3e6" stroke-width="2"/>
+    </pattern>
+  </defs>
+  <rect width="1600" height="1000" fill="url(#desk)"/>
+  <g transform="translate(260 40) scale(.68) rotate(-3 800 500)">
+    <rect x="150" y="90" width="1300" height="830" rx="14" fill="#1b2533"/>
+    <rect x="170" y="105" width="625" height="800" fill="#fbf8f1"/>
+    <rect x="805" y="105" width="625" height="800" fill="#fbf8f1"/>
+    <rect x="770" y="105" width="60" height="800" fill="url(#spine)"/>
+    <rect x="170" y="180" width="625" height="700" fill="url(#rule)"/>
+    <rect x="805" y="180" width="625" height="700" fill="url(#rule)"/>
+    <line x1="240" y1="105" x2="240" y2="905" stroke="#e39a9a" stroke-width="3"/>
+    <line x1="875" y1="105" x2="875" y2="905" stroke="#e39a9a" stroke-width="3"/>
+    <g fill="none" stroke="#24304a" stroke-width="5" stroke-linecap="round">
+      <path d="M262 165 h120 M402 165 h70"/>
+      <path d="M262 245 h300" stroke-width="7"/>
+      <path d="M262 325 h420 M262 365 h380 M262 405 h300"/>
+      <path d="M262 485 h30 M310 485 h300 M262 525 h30 M310 525 h340 M262 565 h30 M310 565 h260 M262 605 h30 M310 605 h320"/>
+      <path d="M262 685 h400 M262 725 h360"/>
+      <path d="M262 805 h250" stroke="#b5452f"/>
+    </g>
+    <path d="M520 798 q20 -18 40 0 t40 0" fill="none" stroke="#b5452f" stroke-width="4" stroke-linecap="round"/>
+    <g fill="none" stroke="#24304a" stroke-width="4" stroke-linecap="round">
+      <path d="M897 165 h160"/>
+      <rect x="897" y="220" width="460" height="200"/>
+      <path d="M897 270 h460 M897 320 h460 M897 370 h460 M1050 220 v200 M1200 220 v200"/>
+      <path d="M915 247 h90 M1068 247 h90 M1218 247 h90" stroke-width="5"/>
+      <path d="M915 297 h60 M1068 297 h70 M1218 297 h50 M915 347 h60 M1068 347 h40 M1218 347 h80 M915 397 h60 M1068 397 h60 M1218 397 h60" stroke-width="3"/>
+      <path d="M917 820 V480 M917 820 H1360"/>
+      <path d="M930 800 C1010 790 1060 700 1110 610 S1240 500 1340 495" stroke="#2455c7" stroke-width="5"/>
+    </g>
+    <g fill="#2455c7">
+      <circle cx="960" cy="792" r="9"/><circle cx="1040" cy="742" r="9"/><circle cx="1105" cy="628" r="9"/>
+      <circle cx="1175" cy="545" r="9"/><circle cx="1260" cy="510" r="9"/><circle cx="1335" cy="500" r="9"/>
+    </g>
+    <g transform="rotate(32 1260 690)">
+      <rect x="1000" y="676" width="430" height="30" rx="14" fill="#1d2735"/>
+      <rect x="1330" y="676" width="34" height="30" fill="#c9a24b"/>
+      <path d="M1000 676 l-46 15 l46 15 z" fill="#e8dcc4"/>
+      <path d="M954 691 l14 -4 v8 z" fill="#1d2735"/>
+      <rect x="1080" y="668" width="150" height="10" rx="5" fill="#c9a24b"/>
+    </g>
+  </g>
+</svg>

package/docs/site/package.json

@@ -0,0 +1,9 @@
+{
+  "name": "@mdeck/docs",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "dev": "node ../../bin/mdeck.js docs",
+    "build": "node build.js"
+  }
+}