@zap-cms/app

ZAP APP

What is it

An injectable admin ui that enables the use of the ZAP CMS. The zap app should:

• Be spawned as an SPA in the /cms route of a given site (this is done with the zap-lancher package).
• Be able to read the CMS content & settings as files under the public /cms route.
• Create, validate and edit it's own settings.
• Validate the CMS content.
• Initialize the CMS content.
• Manage the content (both as a developer creating a schema and an author filling it out):
  • Pages (with SEO) & Dynamic pages
  • Catalogs
  • Images & files
  • I18n
  • Routes
• Use the updater module as its auth provider.
• Use the updater module as to update the CMS content.
• Offer two diffrent UI for developpers and editors.

Development

The package uses vite as a bundler, which bundles it in a single js file. pnpm dev will launch a HMR vite dev server but it might be useless as it need to be called in a working website to be interacted with.

Using the package in the zap-playground might be better.

Publisihing

As it's a single file SPA, only the dist/zap.js gets pubblished. Run pnpm build and pnpm publish to achive that.