Publish and share

Manteen registries need no registry account or central directory. Publish public/r/ through any static HTTPS host that serves the item and index documents as JSON.

GitHub Pages

This minimal workflow builds the registry before uploading it. Pin versions according to your own repository’s maintenance policy.

1
name: Deploy registry
2

3
on:
4
  push:
5
    branches: [main]
6

7
permissions:
8
  contents: read
9
  pages: write
10
  id-token: write
11

12
jobs:
13
  build:
14
    runs-on: ubuntu-latest
15
    steps:
16
      - uses: actions/checkout@v7
17
      - uses: actions/setup-node@v7
18
        with:
19
          node-version: "24"
20
          cache: npm
21
      - run: npm ci
22
      - run: npx manteen-kit build
23
      - uses: actions/configure-pages@v6
24
      - uses: actions/upload-pages-artifact@v5
25
        with:
26
          path: public
27

28
  deploy:
29
    needs: build
30
    runs-on: ubuntu-latest
31
    environment:
32
      name: github-pages
33
      url: ${{ steps.deployment.outputs.page_url }}
34
    steps:
35
      - id: deployment
36
        uses: actions/deploy-pages@v5

After deployment, verify both URLs directly:

1
https://acme.github.io/manteen-registry/r/registry.json
2
https://acme.github.io/manteen-registry/r/release-panel.json

A consumer can install an item URL without changing manteen.json:

1
npx manteen info https://acme.github.io/manteen-registry/r/release-panel.json
2
npx manteen add https://acme.github.io/manteen-registry/r/release-panel.json

The item can still contain multiple files, npm dependencies, package styles, and a theme fragment. It must not contain a bare or namespaced registry dependency that the consumer has not configured. A direct URL has no namespace from which Manteen could resolve a bare dependency.

For repeated use, discovery, private-request configuration, or items that depend on other items, the consumer adds a namespace to manteen.json:

1
{
2
  "registries": {
3
    "@acme": {
4
      "url": "https://acme.github.io/manteen-registry/r/{name}.json",
5
      "index": "https://acme.github.io/manteen-registry/r/registry.json"
6
    }
7
  }
8
}

Keep the existing aliases, styles, theme, and tsconfig fields generated by manteen init. The abbreviated object above shows only the registry entry being added.

Consumers can now discover and install by name:

1
npx manteen list @acme
2
npx manteen info @acme/release-panel
3
npx manteen add @acme/release-panel

When a kit-authored item uses another local item, manteen-kit compiles the catalog namespace into that dependency. Treat the catalog’s namespace as the public collection name in that case. A self-contained registry may be assigned a different consumer-side name, but changing the name of a dependency-bearing kit registry leaves its compiled references pointing at the original namespace.

Read URLs and namespaces for the complete decision boundary.

Publish and share

GitHub Pages

Share one self-contained item

Share the collection