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.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.