# CMS

Manage the CMS that [`vela enable cms`](/enable/cms) adds to a project: who can sign in to the admin bar, and when a hosted site is rebuilt with what they publish.

### Syntax

```
$ vela cms <command>
```

- [`editor`](/cms/editor) - Manage who can sign in to the admin bar
- [`deploy`](/cms/deploy) - Rebuild the hosted site with the latest published content

### Two shapes

Where the CMS lives decides which command applies. An app that runs as a Node server, with a PocketBase backend or on `@sveltejs/adapter-node` alone, hosts the CMS itself, in a SQLite database in its data directory; `vela cms editor` writes to that database, and the app reads published content live, so there is nothing to deploy. A static site reads from a CMS hosted on velastack.dev instead, which manages its own editors; what they publish reaches visitors once the site is built again, which is what `vela cms deploy` asks for.

Neither command needs a PocketBase backend, so both work in a static project.