@axerity/cli 0.1.3 → 0.2.0

package/src/content/demo/api/user/get-user.md

@@ -1,69 +0,0 @@
----
-title: Get user by username
-description: Return a single user.
-icon: user
-layout: api
-method: GET
----
-
-<script>
-	import { Api, Endpoint, ParamField, ResponseField, RequestExample, ResponseExample, ObjectExample } from '$lib';
-</script>
-
-# Get user by username
-
-Get user details based on the username. Use `user1` for testing.
-
-<Api>
-
-<Endpoint method="GET" path={'/user/{username}'} baseUrl="https://petstore3.swagger.io/api/v3" />
-
-## Path parameters
-
-<ParamField name="username" type="string" required>
-
-The name of the user to fetch.
-
-</ParamField>
-
-## Returns
-
-Returns the [User](/api/user/user-object).
-
-<ResponseField name="id" type="integer">
-
-Unique id for the user.
-
-</ResponseField>
-
-<ResponseField name="username" type="string">
-
-The user's login name.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl https://petstore3.swagger.io/api/v3/user/user1
-```
-
-</RequestExample>
-
-<ResponseExample title="200 OK">
-
-```json
-{ "id": 10, "username": "user1", "email": "john@email.com" }
-```
-
-</ResponseExample>
-
-<ResponseExample title="404 Not Found">
-
-```json
-{ "code": 404, "message": "User not found" }
-```
-
-</ResponseExample>
-
-</Api>

package/src/content/demo/api/user/login.md

@@ -1,80 +0,0 @@
----
-title: Log in
-description: Log a user into the system.
-icon: user
-layout: api
-method: GET
----
-
-<script>
-	import { Api, Endpoint, ParamField, ResponseField, RequestExample, ResponseExample } from '$lib';
-</script>
-
-# Log in
-
-Log a user into the system. On success the response headers include rate limit
-and token expiry information.
-
-<Api>
-
-<Endpoint method="GET" path="/user/login" baseUrl="https://petstore3.swagger.io/api/v3" />
-
-## Query parameters
-
-<ParamField name="username" type="string">
-
-The user name for login.
-
-</ParamField>
-
-<ParamField name="password" type="string">
-
-The password for login in clear text.
-
-</ParamField>
-
-## Returns
-
-<ResponseField name="token" type="string">
-
-A session token, returned as the response body.
-
-</ResponseField>
-
-<ResponseField name="X-Rate-Limit" type="integer">
-
-Calls per hour allowed for the user. Returned as a response header.
-
-</ResponseField>
-
-<ResponseField name="X-Expires-After" type="string">
-
-The date in UTC when the token expires. Returned as a response header.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl "https://petstore3.swagger.io/api/v3/user/login?username=theUser&password=12345"
-```
-
-</RequestExample>
-
-<ResponseExample title="200 OK">
-
-```json
-"logged in user session: 1640995200000"
-```
-
-</ResponseExample>
-
-<ResponseExample title="400 Bad Request">
-
-```json
-{ "code": 400, "message": "Invalid username/password supplied" }
-```
-
-</ResponseExample>
-
-</Api>

package/src/content/demo/api/user/logout.md

@@ -1,45 +0,0 @@
----
-title: Log out
-description: Log out the current session.
-icon: user
-layout: api
-method: GET
----
-
-<script>
-	import { Api, Endpoint, ResponseField, RequestExample, ResponseExample } from '$lib';
-</script>
-
-# Log out
-
-Log the current user out of the system.
-
-<Api>
-
-<Endpoint method="GET" path="/user/logout" baseUrl="https://petstore3.swagger.io/api/v3" />
-
-## Returns
-
-<ResponseField name="code" type="integer">
-
-The HTTP status code of the result.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl https://petstore3.swagger.io/api/v3/user/logout
-```
-
-</RequestExample>
-
-<ResponseExample title="200 OK">
-
-```json
-{ "code": 200, "message": "ok" }
-```
-
-</ResponseExample>
-
-</Api>

package/src/content/demo/api/user/meta.json

@@ -1,14 +0,0 @@
-{
-	"title": "User",
-	"icon": "user",
-	"pages": [
-		"user-object",
-		"create-user",
-		"create-with-list",
-		"login",
-		"logout",
-		"get-user",
-		"update-user",
-		"delete-user"
-	]
-}

package/src/content/demo/api/user/update-user.md

@@ -1,69 +0,0 @@
----
-title: Update a user
-description: Update an existing user.
-icon: user
-layout: api
-method: PUT
----
-
-<script>
-	import { Api, Endpoint, ParamField, ResponseField, RequestExample, ResponseExample } from '$lib';
-</script>
-
-# Update a user
-
-This can only be done by a logged in user.
-
-<Api>
-
-<Endpoint method="PUT" path={'/user/{username}'} baseUrl="https://petstore3.swagger.io/api/v3" />
-
-## Path parameters
-
-<ParamField name="username" type="string" required>
-
-The name of the user to update.
-
-</ParamField>
-
-## Body parameters
-
-<ParamField name="email" type="string">
-
-The user's email address.
-
-</ParamField>
-
-<ParamField name="password" type="string">
-
-The user's password.
-
-</ParamField>
-
-## Returns
-
-<ResponseField name="code" type="integer">
-
-The HTTP status code of the result.
-
-</ResponseField>
-
-<RequestExample title="cURL">
-
-```bash
-curl -X PUT https://petstore3.swagger.io/api/v3/user/theUser \
-  -H "Content-Type: application/json" \
-  -d '{ "email": "new@email.com" }'
-```
-
-</RequestExample>
-
-<ResponseExample title="200 OK">
-
-```json
-{ "code": 200, "message": "ok" }
-```
-
-</ResponseExample>
-
-</Api>

package/src/content/demo/api/user/user-object.md

@@ -1,85 +0,0 @@
----
-title: The User object
-description: The shape of a User resource.
-icon: user
-layout: api
----
-
-<script>
-	import { Api, ResponseField, ObjectExample } from '$lib';
-</script>
-
-# The User object
-
-A User is an account in the store.
-
-<Api>
-
-## Attributes
-
-<ResponseField name="id" type="integer">
-
-Unique id for the user.
-
-</ResponseField>
-
-<ResponseField name="username" type="string">
-
-The user's login name.
-
-</ResponseField>
-
-<ResponseField name="firstName" type="string">
-
-The user's first name.
-
-</ResponseField>
-
-<ResponseField name="lastName" type="string">
-
-The user's last name.
-
-</ResponseField>
-
-<ResponseField name="email" type="string">
-
-The user's email address.
-
-</ResponseField>
-
-<ResponseField name="password" type="string">
-
-The user's password.
-
-</ResponseField>
-
-<ResponseField name="phone" type="string">
-
-The user's phone number.
-
-</ResponseField>
-
-<ResponseField name="userStatus" type="integer">
-
-The user status.
-
-</ResponseField>
-
-<ObjectExample title="The User object">
-
-```json
-{
-	"id": 10,
-	"username": "theUser",
-	"firstName": "John",
-	"lastName": "James",
-	"email": "john@email.com",
-	"password": "12345",
-	"phone": "12345",
-	"userStatus": 1
-}
-```
-
-</ObjectExample>
-
-</Api>

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` |