Vapid

Vapid is an intentionally simple, open-source content management system that lets developers create a custom admin dashboard directly inside HTML files, without leaving the markup. The project is built on Node.js, requires node v10 or higher, and is installed globally via npm as @vapid/cli. It is distributed under the MIT license and was previously hosted on GitHub under the Vapid organization. The repository is now read-only and no longer maintained, meaning issues and pull requests are not answered, but the code remains available for forking.

What is Vapid?

Vapid is a content management system that derives its admin interface from the HTML you write, using special attributes or comments to mark editable regions. It takes HTML, Sass, and JavaScript files as input, and produces a working website with a custom dashboard, with content stored in a local SQLite database. The server runs on Node.js and can be started with the vapid start command, which includes live reloading as you edit source files. The dashboard is generated automatically from the HTML, which is the core idea: you build a custom dashboard without ever leaving the HTML.

Key Features

• Custom dashboard from HTML — Define editable content regions directly in your HTML; Vapid generates a matching admin panel automatically, so there is no separate dashboard configuration.
• Node.js CLI — Install with npm install -g @vapid/cli and use commands like vapid new to scaffold a project and vapid start to launch the development server.
• SQLite storage — Content and uploaded images are stored in a local SQLite database inside the data folder, with no external database setup required.
• Live reload — The development server automatically refreshes the website when source files change, speeding up local development.
• Webpack compilation — Files with .pack.js, .pack.scss, or .pack.sass extensions are compiled by Webpack, allowing you to use modern JavaScript and Sass in your project.
• Static site export — Run vapid build to export the entire site as static files, which can then be hosted on S3, Surge, or similar static hosting.
• Config via package.json — Your package.json holds project information and Vapid configuration options, keeping project setup conventional.
• Deploy to any Node.js host — The project runs on any hosting service that supports Node.js, with Heroku and Glitch listed as examples.

Who is it for?

Developers who want a lightweight alternative to full-featured CMS platforms and enjoy working directly in HTML. Front-end designers who need to give clients a simple editing interface without building a separate admin panel. Small studios building brochure sites or blogs that need a custom dashboard tailored to the site's content model. Anyone looking for a Node.js-based CMS that can be deployed to conventional hosting or exported to static files.

What can you do with Vapid?

• Build a blog or news site — Mark article content, titles, and images as editable regions in your HTML, and the generated dashboard lets non-technical editors update posts without touching code.
• Create a portfolio or company site — Use Vapid as a simple CMS for a marketing site, with live reload during development and a static export for production hosting.
• Prototype a custom dashboard — Because the dashboard is derived from HTML, you can rapidly prototype an admin interface that matches your data model exactly, without learning a separate admin framework.
• Test-drive a CMS on Glitch — The project provides a one-click remix on Glitch with a SECRET_KEY environment variable, making it easy to experiment in the browser.

How does Vapid work?

First, install the command-line tool globally with npm install -g @vapid/cli. Second, create a new project with vapid new path/to/project/folder, then start the development server with vapid start .. The server serves your www folder, compiles .pack.js and .pack.scss files, and shows a dashboard based on the editable regions you've defined in your HTML. When you're done, run vapid build to export a static version of the site.

Pros and cons

• Pros — The dashboard is generated from HTML, which is simple and transparent; the system uses SQLite for zero-configuration storage; live reload and Webpack integration speed up development; deployment is flexible via Node.js hosting or static export.
• Cons — The project is no longer maintained, so bug fixes and security updates will not be released; the type=image directives do not work on ephemeral file systems like Heroku's, because uploaded files are not persisted.

FAQ

Is Vapid free?

Yes, Vapid is open-source and released under the MIT license. You can install it via npm and use it in commercial and personal projects without licensing fees.

Does Vapid use a database?

Yes, Vapid stores content in a local SQLite database located in the data folder. Uploaded images are also stored in the same folder, making backups a matter of copying that directory.

How do I deploy a Vapid site?

You can deploy to any hosting service that supports Node.js, such as Heroku or Glitch. Alternatively, use vapid build to generate static files and host them on services like S3 or Surge.

Is Vapid still maintained?

No, the repository is no longer maintained. Issues and pull requests are not answered, and the repository is read-only, though it remains available for forking and use in other projects.

What Node.js version does Vapid require?

Vapid requires Node.js version 10 or higher. The server will not run on older versions of Node.