Editing content
Editing content
Everything you do in the control panel — writing, publishing, images, forms.
This section is for the people who write the site. Everything in it happens in the control panel at /admin in
your browser. Nothing here needs a terminal, and nothing here can break the site’s code.
If someone has just given you an account, start with Entries — writing a page is most of the job — then Drafts and publishing, which explains why what you typed is not on the site yet.
The pages
| Page | What it covers |
|---|---|
| Entries | writing a page, the fields you see, URLs, deleting |
| Drafts and publishing | drafts, previews, revisions, scheduling, review |
| Assets | uploading images and files, cropping, and reusing them |
| Navigation | building the menus visitors use to get around |
| Forms | what people sent you, and where it goes |
| Redirects and SEO | titles and descriptions, sitemaps, and not breaking old links |
Finding your way around
The sidebar is grouped: your content at the top, then structure (globals, navigation), then tools (forms, redirects, trash), then people. You only see what your role allows, so a shorter sidebar than a colleague’s is not a fault.
Search is at the top of every screen, or press Ctrl-K. It searches your content, not just page titles.
Your account is under the menu in the top right: your password, your sessions, and two-factor authentication.
Two ideas worth five minutes
Collections and blueprints. A collection is a kind of content — Pages, Posts, Guides. A blueprint is the list of fields one of those has. Both are decided by whoever builds the site, which is why the form you see fits the content rather than being a general-purpose box. A collection can have more than one blueprint, so a “Guide” and a “Gallery” can live in the same place and look nothing alike.
Nothing is lost. Saving a live page creates a draft rather than changing the site. Every publish keeps a revision you can go back to. Deleting moves something to the trash, where it waits rather than disappearing. You would have to work quite hard to lose anything.
If a page is read-only
Some collections are written as files by the developers — documentation, usually. Those pages open so you can read them, but the fields are locked, and the page tells you which file it comes from. That is deliberate, not a permission problem: an edit there would be overwritten the next time the site is deployed. See Content written as files.