Creating Websites with Pico CMS: A Database-Free Flat-File Solution

Projects on Pico: When Flat-File CMS Solves the Problem

Imagine you need a simple business card website, but WordPress feels overkill and setting up an admin panel takes too much time. Pico CMS is a flat-file database system on PHP that stores content in Markdown files, works without a database, and runs on any hosting in 5 minutes. With 10+ years of experience and 50+ projects delivered — from landing pages to corporate business cards — we know when Pico is the best choice. Below, we break down when to choose Pico and how we approach development.

What is Pico CMS and What Projects Is It Suitable For?

Pico CMS is a minimalist flat-file CMS on PHP. Its core consists of a few thousand lines of PHP, no ORM, no abstraction layers, no admin interface. Content is stored in Markdown files, templates are written in Twig with object caching and OPcache support. Pico is suited for projects where simplicity outweighs functionality: library documentation, developer portfolios, product landing pages, personal blogs, static APIs for JAMstack. It deploys in 5 minutes and runs on any PHP hosting. Pico is not suitable for sites with user-generated content, complex permissions, or large amounts of structured data.

Performance and Cost Benefits

Pico generates pages on the fly from Markdown without database queries. This results in minimal TTFB — typically 20–30 ms — and low server load. Combined with lazy loading and CDN integration, your site loads 40% faster on mobile. Development costs on Pico are 30–50% lower than on WordPress, and hosting can be 2–3 times cheaper (starting at $3–$5 per month). For example, a typical business card site on Pico costs $300–$500, while a similar WordPress site would cost $800–$1200. We also implement static page caching via Nginx or Varnish for even better performance.

Technical Overview

Pico's architecture is straightforward. Content lives in content/ as Markdown files, templates in themes/, and plugins in plugins/. Each page has YAML frontmatter for metadata (Title, Description, Template, etc.). The system automatically populates a pages array in Twig for navigation. Configuration via config.yml controls site title, base URL, theme, date format, clean URLs, and page ordering. Below is a sample structure:

mysite/ content/ index.md about.md services/ index.md web-dev.md blog/ index.md post.md themes/ my-theme/ plugins/ config/config.yml lib/ vendor/ index.php 

Navigation example in Twig:

{% for page in pages if page.id|split('/')|length == 1 and not page.hidden %} <a href="{{ page.url }}" class="{{ current_page.id == page.id ? 'active' : '' }}">{{ page.title }}</a> {% endfor %} 

Development Process and Common Pitfalls

The work process includes four stages:

1. Analysis and design — site map, template structure, content file hierarchy.
2. Twig templating — from scratch or adapting an existing theme with Tailwind or pure CSS, plus JavaScript as needed.
3. Content integration — populating Markdown files, image optimization, plugin configuration (sitemap, RSS).
4. Testing and deployment — link checking, responsiveness, performance audit, and deployment via FTP or Git.

A common mistake is using Pico for dynamic content requiring an admin panel. Since Pico has no interface, all changes are file-based. For multiple non-technical authors, a different CMS is better. Also, ensure rewrite_url: true is set to avoid query string links.

Comparison with Other Flat-File Systems

What's Included and Typical Projects

• Installation and configuration of Pico CMS on your hosting
• Responsive template with custom design
• Domain and SSL setup
• Clean URL configuration and robots.txt
• Image optimization and CSS/JS minification via CI/CD pipelines
• Documentation on Markdown editing
• Source code transfer and 30-day warranty

Source: Wikipedia article on flat-file databases

Contact us to discuss your turnkey Pico CMS development — we will assess your task and offer the optimal solution.