NextGuide Add-ons

Account Mode marketplace

Browse signed content add-ons, manage reviewed versions and understand executable-extension restrictions.

Account Mode add-ons

Reviewed Markdown add-ons

The Account Mode studio now supports signed content-only v1 add-on installation, version pinning, enable/disable state, verified updates, rollback and uninstall. These actions are available only to a signed-in site owner and require the independent registry's Ed25519 signature. Enabled reviewed Markdown pages are published through a dedicated Account Mode route, with registry and stored-archive verification on every request. Executable v2 add-ons remain disabled.

Connect a reviewed registry

Configure the trusted catalog on a persistent Account Mode Node server:

Account Mode registry environmentShell
NEXTGUIDE_ADDON_REGISTRY_URL=https://your-approved-registry.example/v1/registry
NEXTGUIDE_ADDON_REGISTRY_PUBLIC_KEY_B64=YOUR_BASE64_ENCODED_TRUSTED_PUBLIC_ED25519_PEM

The Base64 value contains a PEM-format public key, retrieved through a separately trusted channel. Never load the signing key from unsigned registry metadata or expose the configuration through a NEXT_PUBLIC_ variable. Your NEXTGUIDE_DATA_DIR must point outside the Next.js site, and the runtime must have access to its own persistent private storage.

The registry must issue a newly signed index at least once an hour: stale metadata refuses installation, enabling and rollback, rather than silently using potentially revoked information.

Install and manage content

  1. Sign in to Account Mode and open Add-ons.
  2. Search or filter reviewed releases and open View details.
  3. Check publisher identity, license, NextGuide compatibility and requested permissions.
  4. Confirm Install reviewed content. The site downloads only the signed GitHub Release and verifies its bytes before writing immutable files to private storage.
  5. Use Enable/Disable to control whether the reviewed Markdown pages can be opened at your site's /docs/addons/<publisher.addon>/ route. Each request re-verifies signed approval and local archive integrity.
  6. Use Update when a higher reviewed version is available, or Roll back to a previously saved, still-approved version. Rollback leaves the add-on disabled for explicit re-enabling.
  7. Uninstall clears its installed entry but preserves separate private settings and historical archive blobs for recovery.

Compatibility and executable permissions

Published v1 examples currently declare NextGuide >=1.0.0 <2.0.0. A site still running 0.0.1-alpha.2 is intentionally shown as incompatible, not allowed to bypass the publisher's declared version range. This is a release gate, not a failed install. Code-capable extensions, React widgets, secret handles and server jobs still require additional review, sandbox hardening and permission approvals.

Security and rollback

The server validates owner sessions and request origin on every mutation. Installed data is never placed in content/docs or public assets. The journal checks the signed release metadata, exact SHA-256, compatible package version and current approval status. Conflicting update requests are rejected using an installation revision, and a damaged archive cannot be enabled.

The UI uses NextGuide's native Account Mode components. Pages are rendered with NextGuide's safe Markdown subset, not MDX, so raw HTML and JavaScript are never executed. Disabled, revoked, invalid or stale releases are not served. Add-on pages do not automatically enter the public docs sidebar or search index yet. No Docker requirement or new npm package is introduced.

See Updates and removal, Security and permissions, and runtime API. Follow roadmap #101 for executable v2 and public rendering integration.