@axerity/cli 0.1.4 → 0.2.1

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

@@ -1,54 +0,0 @@
----
-title: Icon
-description: Drop a Lucide icon inline in a sentence or heading.
-icon: flag
----
-
-<script>
-	import { Icon } from '$lib';
-</script>
-
-# Icon
-
-Use the `Icon` component to place a single glyph anywhere in your text. It pulls
-from [Lucide](https://lucide.dev/icons), so any icon name on that site works here.
-
-## Inline
-
-Icons sit on the text baseline, so they read well inside a sentence. Save your
-work often <Icon icon="save" /> and ship when the tests pass <Icon icon="check" color="oklch(0.6 0.16 155)" />.
-
-## Sizing
-
-Pass `size` in pixels. The default is 16.
-
-<Icon icon="flag" size={20} /> <Icon icon="flag" size={28} /> <Icon icon="flag" size={36} />
-
-## Color
-
-By default an icon takes the color of the surrounding text. Pass `color` with any
-CSS color to override it.
-
-<Icon icon="heart" color="oklch(0.62 0.22 25)" size={24} />
-<Icon icon="star" color="oklch(0.7 0.16 75)" size={24} />
-<Icon icon="droplet" color="oklch(0.62 0.2 250)" size={24} />
-
-## Usage
-
-```svelte
-<script>
-	import { Icon } from '$lib';
-</script>
-
-Save your work <Icon icon="save" /> often.
-
-<Icon icon="flag" size={32} color="oklch(0.62 0.22 25)" />
-```
-
-## Props
-
-| Prop    | Type     | Description                         |
-| ------- | -------- | ----------------------------------- |
-| `icon`  | `string` | Lucide icon name (required)         |
-| `size`  | `number` | Size in pixels (default 16)         |
-| `color` | `string` | Any CSS color (defaults to inherit) |

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

@@ -1,28 +0,0 @@
----
-title: Keyboard
-description: Show keyboard keys and shortcuts.
-icon: keyboard
----
-
-<script>
-	import { Kbd } from '$lib';
-</script>
-
-# Keyboard
-
-Wrap a key name in `Kbd` to render it as a physical keyboard key. It is handy
-for documenting shortcuts inline.
-
-## Example
-
-Press <Kbd>⌘</Kbd> <Kbd>K</Kbd> to search, or <Kbd>Esc</Kbd> to close a dialog.
-
-## Usage
-
-```svelte
-<script>
-	import { Kbd } from '$lib';
-</script>
-
-Save with <Kbd>Ctrl</Kbd> <Kbd>S</Kbd>.
-```

package/src/content/demo/components/meta.json

@@ -1,26 +0,0 @@
-{
-	"title": "Components",
-	"icon": "blocks",
-	"pages": [
-		"callout",
-		"cards",
-		"accordion",
-		"tabs",
-		"code-group",
-		"tooltip",
-		"tree",
-		"icon",
-		"frame",
-		"video",
-		"steps",
-		"columns",
-		"badge",
-		"kbd",
-		"update",
-		"roadmap",
-		"type-table",
-		"api",
-		"webhooks",
-		"websockets"
-	]
-}

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

@@ -1,86 +0,0 @@
----
-title: Roadmap
-description: Show what you are building, in progress, and shipped.
-icon: map
----
-
-<script>
-	import { Roadmap, RoadmapItem } from '$lib';
-</script>
-
-# Roadmap
-
-A roadmap is a list of items, each with a status and an optional target. Use it
-on a public roadmap page so readers can see what is planned, what you are working
-on now, and what already shipped.
-
-## Example
-
-<Roadmap>
-
-<RoadmapItem title="Versioned content" status="shipped" eta="June 2026">
-
-Keep separate v1 and v2 content trees with a switcher that follows the reader
-across versions.
-
-</RoadmapItem>
-
-<RoadmapItem title="Search filters" status="in-progress" eta="Q3 2026">
-
-Filter results by section and tag.
-
-</RoadmapItem>
-
-<RoadmapItem title="Offline reading" status="exploring">
-
-Bundle pages into a service worker so docs stay available without a connection.
-
-</RoadmapItem>
-
-<RoadmapItem title="PDF export" status="planned" />
-
-</Roadmap>
-
-## Usage
-
-Wrap the items in `<Roadmap>` and give each `<RoadmapItem>` a `title` and a
-`status`. The body is optional, and so is the `eta`.
-
-```svelte
-<script>
-	import { Roadmap, RoadmapItem } from '$lib';
-</script>
-
-<Roadmap>
-	<RoadmapItem title="Versioned content" status="shipped" eta="June 2026">
-		Separate content trees with a version switcher.
-	</RoadmapItem>
-
-	<RoadmapItem title="Search filters" status="in-progress" eta="Q3 2026">
-		Filter results by section and tag.
-	</RoadmapItem>
-
-	<RoadmapItem title="PDF export" status="planned" />
-</Roadmap>
-```
-
-## Status
-
-Each status has its own color and label.
-
-| Status        | Label       |
-| ------------- | ----------- |
-| `planned`     | Planned     |
-| `exploring`   | Exploring   |
-| `in-progress` | In progress |
-| `shipped`     | Shipped     |
-
-## Props
-
-### RoadmapItem
-
-| Prop     | Type     | Description                                         |
-| -------- | -------- | --------------------------------------------------- |
-| `title`  | `string` | The item name                                       |
-| `status` | `string` | `planned`, `exploring`, `in-progress`, or `shipped` |
-| `eta`    | `string` | Optional target, e.g. `Q3 2026`                     |

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

@@ -1,72 +0,0 @@
----
-title: Steps
-description: Numbered, vertical walkthroughs.
-icon: list
----
-
-<script>
-	import { Steps, Step } from '$lib';
-</script>
-
-# Steps
-
-Steps lay out a sequence of instructions as a numbered, vertical walkthrough.
-Numbering is automatic.
-
-## Example
-
-<Steps>
-	<Step title="Install">
-
-Add Axerity to your project:
-
-```bash
-pnpm add axerity
-```
-
-    </Step>
-    <Step title="Create a page">
-
-Drop a Markdown file into `src/content/docs`.
-
-    </Step>
-    <Step title="Run it">
-
-Start the dev server with `pnpm dev` and open the page.
-
-    </Step>
-
-</Steps>
-
-## Usage
-
-Wrap `Step`s in `Steps`. Each `Step` takes an optional `title`. Keep the blank
-lines around content so the Markdown is parsed:
-
-````md
-<script>
-	import { Steps, Step } from '$lib';
-</script>
-
-<Steps>
-	<Step title="Install">
-
-    ```bash
-    pnpm add axerity
-    ```
-
-    </Step>
-    <Step title="Run it">
-
-    Start the dev server.
-
-    </Step>
-
-</Steps>
-````
-
-## Props
-
-| Component | Prop    | Description             |
-| --------- | ------- | ----------------------- |
-| `Step`    | `title` | Step heading (optional) |

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

@@ -1,146 +0,0 @@
----
-title: Tabs
-description: Switch between alternative content in place.
-icon: layers
----
-
-<script>
-	import { Tabs, Tab } from '$lib';
-</script>
-
-# Tabs
-
-Tabs let readers switch between alternative content, package managers, OSes, or
-languages, without leaving the page.
-
-## Example
-
-<Tabs>
-	<Tab title="pnpm">
-
-```bash
-pnpm add axerity
-```
-
-    </Tab>
-    <Tab title="npm">
-
-```bash
-npm install axerity
-```
-
-    </Tab>
-    <Tab title="yarn">
-
-```bash
-yarn add axerity
-```
-
-    </Tab>
-
-</Tabs>
-
-The first tab is selected by default.
-
-## Icons
-
-Give a `Tab` an `icon` (any Lucide name) to show a glyph next to its label:
-
-<Tabs>
-	<Tab title="TypeScript" icon="code">
-
-```ts
-export const x: number = 1;
-```
-
-    </Tab>
-    <Tab title="Config" icon="file-text">
-
-```json
-{ "x": 1 }
-```
-
-    </Tab>
-
-</Tabs>
-
-## Shared & persistent groups
-
-Give multiple `Tabs` the same `group` and they sync, picking a tab in one
-switches every other group on the page, and the choice is **remembered across
-reloads** (via `localStorage`). Tabs are matched by title.
-
-<Tabs group="pm">
-	<Tab title="pnpm">
-
-```bash
-pnpm add axerity
-```
-
-    </Tab>
-    <Tab title="npm">
-
-```bash
-npm install axerity
-```
-
-    </Tab>
-
-</Tabs>
-
-<Tabs group="pm">
-	<Tab title="pnpm">
-
-```bash
-pnpm dev
-```
-
-    </Tab>
-    <Tab title="npm">
-
-```bash
-npm run dev
-```
-
-    </Tab>
-
-</Tabs>
-
-Switch one of the two blocks above, the other follows.
-
-## Usage
-
-Import `Tabs` and `Tab`, then give each `Tab` a `title`. Remember the blank
-lines around tab content so the Markdown inside is parsed:
-
-````md
-<script>
-	import { Tabs, Tab } from '$lib';
-</script>
-
-<Tabs>
-	<Tab title="pnpm">
-
-    ```bash
-    pnpm add axerity
-    ```
-
-    </Tab>
-    <Tab title="npm">
-
-    ```bash
-    npm install axerity
-    ```
-
-    </Tab>
-
-</Tabs>
-````
-
-## Props
-
-| Component | Prop    | Description                                     |
-| --------- | ------- | ----------------------------------------------- |
-| `Tabs`    | `group` | Sync + persist selection across same-group tabs |
-| `Tab`     | `title` | Tab label (required)                            |
-| `Tab`     | `icon`  | Optional Lucide icon name                       |

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

@@ -1,44 +0,0 @@
----
-title: Tooltip
-description: Show a short hint when a reader hovers or focuses a word.
-icon: message-circle
----
-
-<script>
-	import { Tooltip } from '$lib';
-</script>
-
-# Tooltip
-
-Tooltips attach a short note to a word or phrase. The note stays hidden until the
-reader hovers the trigger or moves keyboard focus onto it. Use them for quick
-definitions and asides that would clutter the sentence if written inline.
-
-## Example
-
-The request returns a <Tooltip tip="JavaScript Object Notation, a plain text data format.">JSON</Tooltip> body with the pet record. Hover the dotted word to read the hint.
-
-## Usage
-
-```svelte
-<script>
-	import { Tooltip } from '$lib';
-</script>
-
-The request returns a <Tooltip tip="JavaScript Object Notation.">JSON</Tooltip> body.
-```
-
-The text between the tags is the trigger. It gets a dotted underline so readers
-know there is more to see. The `tip` text is the note that appears above it.
-
-## Keyboard and screen readers
-
-The trigger is a real button, so it is reachable with the Tab key and the note
-shows on focus as well as hover. The `tip` is also exposed as the button's label,
-so screen readers announce it.
-
-## Props
-
-| Prop  | Type     | Description              |
-| ----- | -------- | ------------------------ |
-| `tip` | `string` | The hint text (required) |

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

@@ -1,83 +0,0 @@
----
-title: File tree
-description: Show a folder and file layout the way it looks on disk.
-icon: folder-tree
----
-
-<script>
-	import { Tree, Folder, File } from '$lib';
-</script>
-
-# File tree
-
-A file tree shows how files and folders are arranged. Use it to point readers to
-the right place in a project without making them guess.
-
-## Example
-
-<Tree>
-	<Folder name="src" defaultOpen>
-		<Folder name="content">
-			<Folder name="docs">
-				<File name="index.md" />
-				<File name="installation.md" />
-			</Folder>
-		</Folder>
-		<Folder name="lib">
-			<File name="index.ts" />
-		</Folder>
-		<File name="app.html" />
-	</Folder>
-	<File name="axerity.json" />
-	<File name="package.json" />
-</Tree>
-
-Click a folder to open or close it. Pass `defaultOpen` to a folder to show its
-contents on load.
-
-## Usage
-
-```svelte
-<script>
-	import { Tree, Folder, File } from '$lib';
-</script>
-
-<Tree>
-	<Folder name="src" defaultOpen>
-		<Folder name="content">
-			<File name="index.md" />
-		</Folder>
-		<File name="app.html" />
-	</Folder>
-	<File name="package.json" />
-</Tree>
-```
-
-## Custom icons
-
-By default folders use a folder glyph and files use a file glyph. Pass `icon`
-with any Lucide name to override either one.
-
-<Tree>
-	<Folder name="images" icon="image" defaultOpen>
-		<File name="logo.svg" icon="file-image" />
-	</Folder>
-	<File name="README.md" icon="book-open" />
-</Tree>
-
-## Props
-
-### Folder
-
-| Prop          | Type      | Description            |
-| ------------- | --------- | ---------------------- |
-| `name`        | `string`  | Folder name (required) |
-| `icon`        | `string`  | Lucide icon name       |
-| `defaultOpen` | `boolean` | Expand on load         |
-
-### File
-
-| Prop   | Type     | Description          |
-| ------ | -------- | -------------------- |
-| `name` | `string` | File name (required) |
-| `icon` | `string` | Lucide icon name     |

package/src/content/demo/components/type-table.md

@@ -1,77 +0,0 @@
----
-title: Type Table
-description: Document an object's properties in a configurable table.
-icon: tag
----
-
-<script>
-	import { TypeTable } from '$lib';
-</script>
-
-# Type Table
-
-`TypeTable` documents the shape of an object, component props, config options,
-API parameters, from a single object. The **Default** column hides itself when
-no property defines one.
-
-## Example
-
-<TypeTable
-type={{
-		title: {
-			type: 'string',
-			description: 'The heading shown at the top.',
-			required: true
-		},
-		icon: {
-			type: 'string',
-			description: 'A Lucide icon name shown beside the title.'
-		},
-		open: {
-			type: 'boolean',
-			description: 'Whether the panel starts expanded.',
-			default: 'false'
-		},
-		variant: {
-			type: "'flat' | 'boxed'",
-			typeDescription: 'Controls the container width.',
-			default: "'flat'"
-		},
-		legacy: {
-			type: 'boolean',
-			description: 'No longer used.',
-			deprecated: true
-		}
-	}}
-/>
-
-## Usage
-
-```svelte
-<script>
-	import { TypeTable } from '$lib';
-</script>
-
-<TypeTable
-	type={{
-		title: { type: 'string', description: 'The heading.', required: true },
-		open: { type: 'boolean', default: 'false' }
-	}}
-/>
-```
-
-## Per-property fields
-
-<TypeTable
-type={{
-		type: { type: 'string', description: 'Shown as a code chip.' },
-		description: { type: 'string', description: 'Short prose under the name.' },
-		typeDescription: {
-			type: 'string',
-			description: 'Longer note shown muted under the type.'
-		},
-		default: { type: 'string', description: 'Shown as a code chip in the Default column.' },
-		required: { type: 'boolean', description: 'Adds a "required" badge.' },
-		deprecated: { type: 'boolean', description: 'Strikes the name and adds a badge.' }
-	}}
-/>

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

@@ -1,48 +0,0 @@
----
-title: Update
-description: A timeline entry for changelogs and release notes.
-icon: history
----
-
-<script>
-	import { Update, Badge } from '$lib';
-</script>
-
-# Update
-
-`Update` renders a single entry on a vertical timeline. Stack several to build a
-changelog. Pair it with a `date` in the page frontmatter.
-
-## Example
-
-<Update label="v1.1.0" date="June 1, 2026">
-
-Added the `Update` component. <Badge color="success">new</Badge>
-
-- Timeline entries with a label and optional date.
-- Reads nicely on a dedicated changelog page.
-
-</Update>
-
-<Update label="v1.0.0" date="May 1, 2026">
-
-The first stable release.
-
-</Update>
-
-## Usage
-
-```svelte
-<script>
-	import { Update } from '$lib';
-</script>
-
-<Update label="v1.1.0" date="June 1, 2026">What changed in this release.</Update>
-```
-
-## Props
-
-| Prop    | Type     | Description                           |
-| ------- | -------- | ------------------------------------- |
-| `label` | `string` | Heading, usually a version (required) |
-| `date`  | `string` | Optional date shown next to the label |