@wernerglinka/in-situ-editor
v0.11.1
Published
In-site section-builder editor for Metalsmith structured-content sites, with Chrome built-in AI and Netlify Identity publishing. Run `npx @wernerglinka/in-situ-editor` inside a starter-derived site to install it.
Downloads
2,177
Maintainers
Readme
@wernerglinka/in-situ-editor
The in-situ editor: an in-site, section-builder admin for Metalsmith structured-content sites, with Chrome built-in AI and Netlify Identity publishing.
This package is the editor's published, editor-only instance. It is generated
from the editor's dev fixture by export-editor.mjs; do not hand-edit the
copied surface here — change it in the fixture and re-export.
Install
Inside a freshly cloned starter-derived site:
npx @wernerglinka/in-situ-editorThis vendors the editor into your site (you own and commit the copied files — that is the point of an in-situ editor) and prints the remaining wiring:
npm install metalsmith-site-data metalsmith-bundled-components- Wire the plugins into
metalsmith.js(emit the editor schema frommetalsmith-bundled-componentswithschema: { enabled: true }; placepagesArtifact()beforecollections()anddataArtifact()after it, beforepermalinks()). - Make sure the site loads its data files into
metadata().databeforedataArtifact()runs. - Set up Netlify Identity + the publish Function's GitHub PAT (the PAT lives only in the Function, never the client).
- Review the POC globals in
lib/layouts/admin.njk(window.AUTHORS, locales). - Build, then open
/admin/?admin=true. Sign in to edit and publish.
Re-run with --force to overwrite an existing install.
Add --dev to also copy the distribution scripts into the site, turning it into
a self-contained dev fixture you can develop the editor in and re-export from
(node scripts/export-editor.mjs <dir>). A plain content install omits it.
