Skip to content

FAQ

Yes. Vault CMS is headless: it manages Markdown in your content folder and does not change theme templates. For Starlight, Chiri, Slate, and others, use a preset when the installer asks, or pass --template.

Yes. Vault CMS is a preconfigured Obsidian vault plus plugins. Download Obsidian at obsidian.md.

Yes. Vault CMS is open source (MIT). Some bundled plugins from the same author offer optional Patreon support.

As .md files in your Astro content directory (often src/content/). No Vault CMS database—files on disk and in Git.

Yes. Clone the repo, run the installer on each machine if needed, and open the same vault path in Obsidian.

From your project directory:

Terminal window
npx create-vaultcms

This refreshes .obsidian and _bases. Your Markdown content in collections is not removed by that process—still use Git and backups as usual.

The workflow targets .md. Astro Composer can expose .mdx in the explorer via settings; you can still author MDX manually if your theme uses it.

It contains Home.base, which powers the CMS-style home grid. Do not delete _bases if you want that view.

You can edit locally without Git, but one-click publish from Obsidian expects a remote. Without Git, copy or deploy files by another path.

Ctrl/Cmd + PVault CMS: Open Wizard.