@lakshmanshankar/pagwrite-astro

Astro integration for fetching Pagewrite CMS content at build time and writing it as MDX files into your Astro content directory.

This package is currently focused on the Astro fetch/write integration. The lower-level fetch and staging functions are exported so they can later be reused by another adapter, such as Next.js or Fumadocs.

How It Works

Pagewrite CMS                  User's Astro project
-------------                  --------------------
siteId, token           --->    @lakshmanshankar/pagwrite-astro config
                                  |
                                  v
                               astro build
                                  |
                                  v
                         fetch static file tree
                         fetch paginated file documents
                                  |
                                  v
                         src/content/docs/*.mdx

Installation

pnpm add @lakshmanshankar/pagwrite-astro

Setup

Configure the integration before content-related integrations in astro.config.mjs:

import { defineConfig } from "astro/config";
import mdx from "@astrojs/mdx";
import pagewriteAstro from "@lakshmanshankar/pagwrite-astro";

import { loadEnv } from "vite";
const env = loadEnv(process.env.NODE_ENV!, process.cwd(), "");

export default defineConfig({
  integrations: [
    pagewriteAstro({
      siteId: "your-site-id",
      token: env.PAGEWRITE_BUILD_TOKEN, // or Pagewrite build token
    }),
    mdx(),
  ],
});

Options

| Option | Type | Default | Description | | ------ | ---- | ------- | ----------- | | siteId | string | required | Pagewrite site to fetch and stage. | | token | string | required | Build token value. | | outputDir | string | src/content/docs | Directory where MDX files are written, relative to the Astro project root. | | clean | boolean | false | Remove outputDir before writing fetched files. | | verbose | boolean | false | Reserved for more detailed sync logging. |

Examples

Custom Output Directory

pagewriteAstro({
  siteId: "your-site-id",
  outputDir: "src/content/blog",
});

Clean Sync For CI

pagewriteAstro({
  siteId: "your-site-id",
  clean: true,
});

Ad-Hoc Fetching

You can fetch content outside the Astro build by running the CLI in a predeploy step, CI job, or local verification command:

pagewrite-content fetch --site-id your-site-id --token rmx_live_xxxxxxxxxxxx --out src/content/docs

For CI, wire it before your framework build:

{
  "scripts": {
    "content:fetch": "pagewrite-content fetch --site-id $PAGEWRITE_SITE_ID --token $PAGEWRITE_BUILD_TOKEN --out src/content/docs --clean",
    "prebuild": "pnpm content:fetch",
    "build": "astro build"
  }
}

To verify the remote content without keeping files on disk, use dry run:

pagewrite-content fetch --site-id your-site-id --token rmx_live_xxxxxxxxxxxx --dry-run

CLI options mirror the integration defaults: --token, --clean, --page-size, and --timeout-ms are available.

See CLI.md for the full command reference and CI examples.

Lower-Level API

The package also exports the reusable content staging primitives:

import {
  fetchStaticFileTree,
  fetchAllFileDocuments,
  stageSiteContent,
} from "@lakshmanshankar/pagwrite-astro";

await stageSiteContent("your-site-id", "rmx_live_xxxxxxxxxxxx", "./content/docs");

stageSiteContent fetches the static file tree and paginated file documents, converts file tree paths into safe MDX file paths, upserts title and slug frontmatter, and writes files to the target directory.

Publishing

Package publishing is handled by GitHub Actions. Configure an NPM_TOKEN repository secret with permission to publish @lakshmanshankar/pagwrite-astro, then publish a GitHub release to run the npm publish workflow.

The workflow installs dependencies with pnpm, runs typecheck, tests, and build, then publishes to the npm registry with provenance enabled. It can also be started manually from the Actions tab with workflow_dispatch.

Security Notes

• Never commit build tokens.
• Build tokens should be read-only and scoped to fetch site content.
• File tree paths are normalized and checked before writing.
• Missing tokens, API failures, invalid tree responses, and disk write errors fail the Astro build.