Where Does Pico CMS Store Content?
Pico CMS stores pages as Markdown in content folder and settings in config. Themes live in themes folder.
Last updated
Pico has no database. Markdown pages live in content at the site root. Each .md file becomes a page. Subfolders become subpages. That makes backup a plain file copy.
Site settings live in config/config.yml. Themes live in themes. Plugins live in plugins. For a full move, copy content, config, and any custom theme folder. Core Pico files can be fresh. Back up the full Pico root on first setup, then keep content and config in version control for daily changes. Test page routes after restore, since theme and plugin versions must match the content format.
Where Pico CMS stores this, by platform
/var/www/html/pico/content
All Markdown pages. Copy this folder for content backup. File names map directly to page URLs.
/var/www/html/pico/config/config.yml
Main settings file. Holds site title, theme, and plugin options. Back it up alongside content for a full restore.
Frequently asked questions
how do i move a pico site
Copy content, config, and themes into the new Pico root. Keep the same Pico version to avoid theme API drift. Clear any Twig cache if pages render stale.
can i version pico content with git
Content pages are plain .md files with YAML front matter. Any file sync or git workflow works. Include config/config.yml so routes and metadata stay intact.
Notice an outdated path? Let us know.