@act-spec/plugin-eleventy

Eleventy plugin for ACT (Agent Content Tree). Wraps the ACT generator pipeline (@act-spec/generator-core) against Eleventy 2.0+ via the addPlugin API and the eleventy.after build hook. Component bindings are explicitly out of scope for Eleventy — for component-driven workflows use @act-spec/plugin-astro, the Next.js generator, or @act-spec/plugin-nuxt. The markdown adapter is consumed unchanged from @act-spec/adapter-markdown.

A parseMode opt-in lets developers select 'eleventy-templates' to walk Eleventy's template registry as the source of truth, in addition to the default 'markdown-fs' mode that delegates to the markdown adapter.

Status

ACT v0.1 internal hand-test candidate. Public release lands at v0.2.

Install

Unpublished in v0.1. Consume via the workspace:

// package.json
{ "dependencies": { "@act-spec/plugin-eleventy": "workspace:*" } }

Usage

// .eleventy.js / eleventy.config.mjs
import actPlugin from '@act-spec/plugin-eleventy';

export default function (eleventyConfig) {
  eleventyConfig.addPlugin(actPlugin, {
    baseUrl: 'https://example.com',
    manifest: { site: { name: 'Example' } },
    urlTemplates: {
      indexUrl: '/act/index.json',
      nodeUrlTemplate: '/act/n/{id}.json',
    },
    parseMode: 'markdown-fs',     // or 'eleventy-templates'
    conformanceTarget: 'core',
  });
  return { dir: { input: '.', output: '_site' } };
}

The plugin runs after the Eleventy build completes (eleventy.after), emits the ACT file set into the configured output directory, and writes a BuildReport adjacent to the index for downstream gating.

Programmatic API (test harnesses, custom orchestration):

import { runActBuild, resolveConfig } from '@act-spec/plugin-eleventy';

const resolved = resolveConfig(opts, eleventyConfigLike);
const report = await runActBuild(resolved, payload);

Conformance / what's tested

Every public API has a citing test in the package's test suite, including the Eleventy version gate (enforceEleventyVersion), the watch re-entry guard, the permalink-filtered warnings path, the parseMode selector, and the bindings rejection. The conformance gate runs @act-spec/validator against the emitted file set.

pnpm -F @act-spec/plugin-eleventy conformance

Configuration (selected)

| Option | Default | Notes | | --- | --- | --- | | baseUrl | (required) | Site base URL used in the manifest. | | urlTemplates | (required) | indexUrl + nodeUrlTemplate. | | manifest | (required) | Manifest seed (site name, etc.). | | parseMode | 'markdown-fs' | 'eleventy-templates' walks Eleventy's registry. | | conformanceTarget | 'core' | 'core' \| 'standard' \| 'strict'. | | outputDir | Eleventy's output dir | Override per resolveOutputDir. | | bindings | (rejected) | Eleventy is template-driven; no component bindings. |

Peer dependencies

| Peer | Range | | --- | --- | | @11ty/eleventy | >=2.0.0 <4.0.0 |

Optional from npm's perspective; the plugin is a no-op without Eleventy.

Links

• Generator core: @act-spec/generator-core
• Markdown adapter: @act-spec/adapter-markdown
• Repository: https://github.com/act-spec/act