@axerity/cli 0.1.4 → 0.2.1

package/src/content/demo/changelog.md

@@ -1,44 +0,0 @@
----
-title: Changelog
-description: What's new in Axerity.
-icon: history
-date: 2026-06-01
-updated: 2026-06-01
----
-
-<script>
-	import { Update, Badge } from '$lib';
-</script>
-
-# Changelog
-
-Every notable change, newest first.
-
-<Update label="v1.0.0" date="June 1, 2026">
-
-The first stable release. <Badge color="success">stable</Badge>
-
-- Component kit: callouts, cards, accordions, tabs, code groups, steps, columns, badges, roadmaps, and type tables.
-- Media: framed images with click to zoom, video embeds, and inline icons.
-- API docs: generate a full reference from an OpenAPI spec, plus webhook and WebSocket components.
-- Versioned content with a switcher that follows the reader across versions.
-- The `axerity` CLI: `init`, `dev`, `build`, and `preview`, so there is nothing to clone.
-- Mermaid diagrams, Twoslash type hovers, and YAML highlighting.
-- Build-time search, an RSS feed, and edit links on every page.
-
-</Update>
-
-<Update label="v0.9.0" date="May 15, 2026">
-
-Release candidate. <Badge color="info">beta</Badge>
-
-- Config-driven logo, banner, footer, and social links.
-- Dropdown navigation with per-area sidebar tabs.
-
-</Update>
-
-<Update label="v0.5.0" date="April 2, 2026">
-
-- First public preview with Markdown rendering, dark mode, and the flat layout.
-
-</Update>

package/src/content/demo/components/accordion.md

@@ -1,70 +0,0 @@
----
-title: Accordion
-description: Collapsible sections for FAQs and progressive disclosure.
-icon: list
----
-
-<script>
-	import { Accordion, AccordionGroup } from '$lib';
-</script>
-
-# Accordion
-
-Accordions hide secondary content until it's needed, perfect for FAQs, optional
-details, and long reference material.
-
-## Single accordion
-
-<Accordion title="What is Axerity?">
-
-Axerity is a documentation site generator for Svelte. You write Markdown and get a
-fast static site.
-
-</Accordion>
-
-## Grouped
-
-Wrap multiple accordions in an `<AccordionGroup>` to render them as connected
-rows. Pass `open` to expand one by default, and `icon` for a Lucide glyph.
-
-<AccordionGroup>
-	<Accordion title="Installation" icon="download" open>
-
-Run `pnpm install` then `pnpm dev`. See [Installation](/installation) for
-the full walkthrough.
-
-    </Accordion>
-    <Accordion title="Writing content" icon="pencil-line">
-
-Drop Markdown files into `src/content/docs`. Folders become sidebar sections.
-
-    </Accordion>
-    <Accordion title="Components" icon="blocks">
-
-Import kit components in a page's `<script>` block and use them inline.
-
-    </Accordion>
-
-</AccordionGroup>
-
-## Usage
-
-```svelte
-<script>
-	import { Accordion, AccordionGroup } from '$lib';
-</script>
-
-<AccordionGroup>
-	<Accordion title="Installation" icon="download" open>
-		Run `pnpm install` then `pnpm dev`.
-	</Accordion>
-</AccordionGroup>
-```
-
-## Props
-
-| Prop    | Type      | Description                      |
-| ------- | --------- | -------------------------------- |
-| `title` | `string`  | Header text (required)           |
-| `icon`  | `string`  | Optional Lucide icon name        |
-| `open`  | `boolean` | Expand by default (uncontrolled) |

package/src/content/demo/components/api.md

@@ -1,185 +0,0 @@
----
-title: API components
-description: Document REST endpoints with fields, examples, and schemas.
-icon: code
----
-
-<script>
-	import { Api, Endpoint, ParamField, ResponseField, RequestExample, ResponseExample, ObjectExample, Expandable, EnumValues, Enum } from '$lib';
-</script>
-
-# API components
-
-These components build a reference for a REST API. Set `layout: api` in the page
-frontmatter to get the wide, two-column layout where examples sit in a sticky
-rail on the right.
-
-## Writing an API page
-
-Here is a complete page. Set `layout: api`, import the components you need, wrap
-the body in `<Api>`, and leave blank lines around each component so the Markdown
-inside is parsed:
-
-````md
----
-title: Create a pet
-layout: api
-method: POST
----
-
-<script>
-	import { Api, Endpoint, ParamField, ResponseField, RequestExample, ResponseExample, EnumValues, Enum } from '$lib';
-</script>
-
-# Create a pet
-
-<Api>
-
-<Endpoint method="POST" path="/pets" baseUrl="https://api.example.com/v1" />
-
-## Body parameters
-
-<ParamField name="name" type="string" required>
-
-The pet's name.
-
-</ParamField>
-
-<ParamField name="status" type="string" default="available">
-
-<EnumValues>
-	<Enum value="available">Ready to be adopted.</Enum>
-	<Enum value="pending">Adoption in progress.</Enum>
-</EnumValues>
-
-</ParamField>
-
-## Returns
-
-<ResponseField name="id" type="integer">
-
-The unique id of the created pet.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl -X POST https://api.example.com/v1/pets -d '{ "name": "Rex" }'
-```
-
-</RequestExample>
-
-<ResponseExample title="201 Created">
-
-```json
-{ "id": 10, "name": "Rex", "status": "available" }
-```
-
-</ResponseExample>
-
-</Api>
-````
-
-A few things to know:
-
-- The `method` in frontmatter is what shows as the colored badge in the sidebar.
-- Headings (`## Body parameters`) become the section labels; the fields below
-  each heading line up with the example rail on the right.
-- For a path parameter in braces, write it as an expression so Svelte does not
-  treat it as markup: `path={'/pets/{petId}'}`.
-
-That page renders like the example below.
-
-## Example
-
-<Api>
-
-<Endpoint method="POST" path="/pets" baseUrl="https://api.example.com/v1" />
-
-## Body parameters
-
-<ParamField name="name" type="string" required>
-
-The pet's name.
-
-</ParamField>
-
-<ParamField name="status" type="string" default="available">
-
-<EnumValues>
-	<Enum value="available">Ready to be adopted.</Enum>
-	<Enum value="pending">Adoption in progress.</Enum>
-</EnumValues>
-
-</ParamField>
-
-## Returns
-
-<ResponseField name="id" type="integer">
-
-The unique id of the created pet.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl -X POST https://api.example.com/v1/pets -d '{ "name": "Rex" }'
-```
-
-</RequestExample>
-
-<ResponseExample title="201 Created">
-
-```json
-{ "id": 10, "name": "Rex", "status": "available" }
-```
-
-</ResponseExample>
-
-</Api>
-
-## Components
-
-| Component                            | Purpose                                            |
-| ------------------------------------ | -------------------------------------------------- |
-| `Api`                                | Wraps a page so examples float into the right rail |
-| `Endpoint`                           | The method + path header with a copy button        |
-| `ParamField` / `ResponseField`       | A single parameter or response field               |
-| `RequestExample` / `ResponseExample` | A titled code example in the rail                  |
-| `ObjectExample`                      | A titled object/schema example in the rail         |
-| `Expandable`                         | A collapsible group for nested fields              |
-| `EnumValues` / `Enum`                | A list of allowed values for a field               |
-
-## Endpoint
-
-| Prop      | Type     | Description                                 |
-| --------- | -------- | ------------------------------------------- |
-| `method`  | `string` | HTTP method (default `GET`)                 |
-| `path`    | `string` | Request path; `{param}` segments are styled |
-| `baseUrl` | `string` | Base URL shown before the path              |
-
-Path parameters in braces need an expression so Svelte does not read them as
-markup: `path={'/pets/{petId}'}`.
-
-## ParamField and ResponseField
-
-| Prop         | Type      | Description                      |
-| ------------ | --------- | -------------------------------- |
-| `name`       | `string`  | Field name (required)            |
-| `type`       | `string`  | Field type, for example `string` |
-| `typeLink`   | `string`  | Link the type to another page    |
-| `required`   | `boolean` | Mark the field required          |
-| `deprecated` | `boolean` | Mark the field deprecated        |
-| `default`    | `string`  | Default value                    |
-
-The content between the tags is the field's description, and can hold nested
-`Expandable` groups or an `EnumValues` list.
-
-## Examples in the rail
-
-`RequestExample`, `ResponseExample`, and `ObjectExample` each take an optional
-`title` and render in the right-hand rail next to the fields they describe.
-`Expandable` takes a `title` and an `open` boolean. `Enum` takes the allowed
-`value`.

package/src/content/demo/components/badge.md

@@ -1,34 +0,0 @@
----
-title: Badge
-description: Small inline labels for status and tags.
-icon: tag
----
-
-<script>
-	import { Badge } from '$lib';
-</script>
-
-# Badge
-
-A badge is a small pill you can drop inline to label something, a status, a
-version, or a tag. It sits on the text baseline so it reads inside a sentence.
-
-## Colors
-
-Stripe is <Badge color="success">live</Badge>, billing is <Badge color="warn">in review</Badge>, and the old API is <Badge color="error">deprecated</Badge>. Use <Badge color="info">info</Badge> or the default <Badge>neutral</Badge> for everything else.
-
-## Usage
-
-```svelte
-<script>
-	import { Badge } from '$lib';
-</script>
-
-The new endpoint is <Badge color="success">stable</Badge>.
-```
-
-## Props
-
-| Prop    | Type     | Description                                      |
-| ------- | -------- | ------------------------------------------------ |
-| `color` | `string` | `neutral`, `info`, `success`, `warn`, or `error` |

package/src/content/demo/components/callout.md

@@ -1,83 +0,0 @@
----
-title: Callout
-description: Draw attention to important notes.
-icon: info
----
-
-<script>
-	import { Callout } from '$lib';
-</script>
-
-# Callout
-
-Callouts highlight notes, tips, warnings, and more. Import the component in a
-page's `<script>` block, then use it anywhere in your Markdown.
-
-## Variants
-
-<Callout type="info">
-
-This is the default **info** callout.
-
-</Callout>
-
-<Callout type="tip">
-
-A handy **tip** to make your life easier.
-
-</Callout>
-
-<Callout type="success">
-
-Everything worked, **success!**
-
-</Callout>
-
-<Callout type="warn">
-
-Careful, this is a **warning**.
-
-</Callout>
-
-<Callout type="error">
-
-Something went wrong, this is an **error**.
-
-</Callout>
-
-## Usage
-
-Leave a blank line between the tags and the content so the inner text is parsed
-as Markdown (an mdsvex requirement):
-
-```svelte
-<script>
-	import { Callout } from '$lib';
-</script>
-
-<Callout type="warn">Careful, this is a **warning** with a [link](/).</Callout>
-```
-
-## Types
-
-| Type               | Use for                          |
-| ------------------ | -------------------------------- |
-| `info` _(default)_ | General notes and asides         |
-| `tip`              | Helpful suggestions              |
-| `success`          | Confirmations and positive notes |
-| `warn` / `warning` | Things to be careful about       |
-| `error`            | Errors and destructive warnings  |
-
-## Custom title
-
-Pass a `title` to override the default heading:
-
-<Callout type="tip" title="Pro tip">
-
-You can set any heading you like.
-
-</Callout>
-
-```svelte
-<Callout type="tip" title="Pro tip">You can set any heading you like.</Callout>
-```

package/src/content/demo/components/cards.md

@@ -1,88 +0,0 @@
----
-title: Cards
-description: Rich, tappable cards for links and feature grids.
-icon: layout-grid
----
-
-<script>
-	import { Card, CardGroup } from '$lib';
-</script>
-
-# Cards
-
-Cards present links and information as rich, tappable blocks, great for "next
-steps" grids, feature overviews, and navigation.
-
-## Card
-
-A standalone `Card` with an icon, title, and description. Add `href` to make the
-whole card a link (it gains a hover state and an arrow):
-
-<Card title="Installation" icon="download" href="/installation">
-
-Get Axerity running locally in a minute.
-
-</Card>
-
-## Card group
-
-Wrap cards in a `CardGroup` to lay them out in a responsive grid. Use `cols` to
-set the number of columns:
-
-<CardGroup cols={2}>
-	<Card title="Quick Start" icon="rocket" href="/quick-start">
-
-Write your first page in two minutes.
-
-    </Card>
-    <Card title="Markdown" icon="file-text" href="/writing/markdown">
-
-Author content in Markdown and Svelte.
-
-    </Card>
-    <Card title="Components" icon="blocks" href="/components/callout">
-
-Explore the component kit.
-
-    </Card>
-    <Card title="GitHub" icon="code" href="https://github.com/axerity/axerity">
-
-Star the project on GitHub.
-
-    </Card>
-
-</CardGroup>
-
-## Horizontal
-
-Set `horizontal` to place the icon beside the content instead of above it:
-
-<Card title="Configuration" icon="tag" horizontal>
-
-A horizontal card is handy in tighter layouts.
-
-</Card>
-
-## Usage
-
-```svelte
-<script>
-	import { Card, CardGroup } from '$lib';
-</script>
-
-<CardGroup cols={2}>
-	<Card title="Quick Start" icon="rocket" href="/quick-start">
-		Write your first page in two minutes.
-	</Card>
-</CardGroup>
-```
-
-## Props
-
-| Component   | Prop         | Description                     |
-| ----------- | ------------ | ------------------------------- |
-| `CardGroup` | `cols`       | Number of columns (default `2`) |
-| `Card`      | `title`      | Card heading (required)         |
-| `Card`      | `icon`       | Optional Lucide icon name       |
-| `Card`      | `href`       | Makes the card a link           |
-| `Card`      | `horizontal` | Lay the icon beside the content |

package/src/content/demo/components/code-group.md

@@ -1,55 +0,0 @@
----
-title: Code Group
-description: Switch between related code blocks in a single tabbed panel.
-icon: code
----
-
-<script>
-	import { CodeGroup } from '$lib';
-</script>
-
-# Code Group
-
-A code group collapses several code blocks into one panel with a tab for each.
-It is handy for showing the same step across package managers or languages. Each
-tab takes its label from the block's `title`, so give every block one.
-
-## Example
-
-<CodeGroup>
-
-```bash title="npm"
-npm install axerity
-```
-
-```bash title="pnpm"
-pnpm add axerity
-```
-
-```bash title="yarn"
-yarn add axerity
-```
-
-</CodeGroup>
-
-## Usage
-
-Wrap the blocks in `<CodeGroup>` and leave a blank line around each one so the
-Markdown is parsed:
-
-````md
-<CodeGroup>
-
-```bash title="npm"
-npm install axerity
-```
-
-```bash title="pnpm"
-pnpm add axerity
-```
-
-</CodeGroup>
-````
-
-The `title` on each block becomes its tab. Without a title a block falls back to
-`Tab 1`, `Tab 2`, and so on.

package/src/content/demo/components/columns.md

@@ -1,42 +0,0 @@
----
-title: Columns
-description: Lay content out in a responsive grid.
-icon: columns-3
----
-
-<script>
-	import { Columns, Card } from '$lib';
-</script>
-
-# Columns
-
-Columns place their children in an even grid. On narrow screens the grid
-collapses to a single column so nothing gets cramped. Set `cols` to choose how
-many columns to show on wider screens.
-
-## Example
-
-<Columns cols={2}>
-	<Card title="Fast" icon="zap">Static output that loads instantly.</Card>
-	<Card title="Simple" icon="feather">Write Markdown, get a site.</Card>
-</Columns>
-
-## Usage
-
-```svelte
-<script>
-	import { Columns, Card } from '$lib';
-</script>
-
-<Columns cols={3}>
-	<Card title="One" />
-	<Card title="Two" />
-	<Card title="Three" />
-</Columns>
-```
-
-## Props
-
-| Prop   | Type     | Description                                 |
-| ------ | -------- | ------------------------------------------- |
-| `cols` | `number` | Columns on screens 640px and up (default 2) |

package/src/content/demo/components/frame.md

@@ -1,51 +0,0 @@
----
-title: Frame
-description: Wrap an image, video, or component in a styled border with a caption.
-icon: image
----
-
-<script>
-	import { Frame } from '$lib';
-</script>
-
-# Frame
-
-A frame puts a soft border and padding around whatever you place inside it, so a
-screenshot or diagram sits apart from the surrounding text instead of bleeding
-into it. Add a caption to label what the reader is looking at.
-
-Click a frame to open it full screen, then click anywhere or press `Escape` to
-close. Pass `zoom={false}` to turn that off.
-
-## With a caption
-
-<Frame caption="The dashboard after a fresh install">
-	<img src="https://placehold.co/720x360/png" alt="Dashboard screenshot" />
-</Frame>
-
-## Without a caption
-
-<Frame>
-	<img src="https://placehold.co/720x240/png" alt="A wide banner" />
-</Frame>
-
-## Usage
-
-Frame works with any content, an image, a video, or another component:
-
-```svelte
-<script>
-	import { Frame } from '$lib';
-</script>
-
-<Frame caption="The dashboard after a fresh install">
-	<img src="/screenshots/dashboard.png" alt="Dashboard" />
-</Frame>
-```
-
-## Props
-
-| Prop      | Type      | Description                            |
-| --------- | --------- | -------------------------------------- |
-| `caption` | `string`  | Text shown below the framed content    |
-| `zoom`    | `boolean` | Click to open full screen (default on) |