Pico

Pico — less is more

Pico takes the concept of simplicity to its logical extreme. Weighing in at roughly 50 KB, Pico is a stupendously small Flat File CMS that does one thing and does it well: it renders Markdown files as web pages using Twig templates. There's no admin panel, no plugin manager, no visual editor — you create and edit content by writing Markdown files and uploading them to your server.

Key features

Pico's feature list is intentionally short. Content is written in Markdown with YAML front matter (meta data at the top of each file). Twig templates control the presentation. URL routing is based on the file structure — the file content/blog/my-post.md becomes yoursite.com/blog/my-post. Pico supports basic plugins for extending functionality, and theming is straightforward if you know HTML and Twig. There's a simple navigation system and basic pagination support. That's essentially it — and that's the point.

Admin panel

There is no admin panel. This is a fundamental design choice, not a missing feature. You manage content by editing Markdown files in your preferred text editor (VS Code, Sublime Text, Notepad++) and uploading them via FTP or Git. For developers who live in their code editors, this workflow feels natural. For anyone else, it's a dealbreaker.

Content management

Create a .md file in the content directory, add YAML front matter (title, date, template), write your content in Markdown, upload. That's the entire workflow. The simplicity is beautiful if you appreciate it, frustrating if you don't. There's no media management — images go in a folder and you reference them in Markdown. There's no content scheduling, no drafts (unless you build it yourself with templates), and no WYSIWYG editing.

Pros

Incredibly lightweight (~50 KB). Near-zero attack surface. Virtually no learning curve for developers. Fast — there's almost nothing to slow it down. Free and open source (MIT license). Perfect for documentation sites and developer blogs. Clean, predictable file structure.

Cons

No admin panel — non-technical users cannot manage content. No built-in media management. Very limited plugin ecosystem. No visual editing of any kind. Not suitable for sites that need to be updated by non-developers. Requires FTP/Git access for every content change.

Pricing

Free and open source under the MIT license. Zero cost beyond hosting.

Best for

Developers building personal sites or documentation who prefer editing files directly. Projects where an admin panel is unnecessary. Sites where minimal footprint and maximum security are priorities.