Pico CMS Setup: Server Configuration, Plugins, and Twig Cache

A typical scenario: a client wants a "simple site without a database" but runs into WordPress slowdowns (LCP > 4 s) or heavy frameworks. The solution is Pico CMS, a flat-file CMS in PHP with TTFB ~0.3 s. No database needed—content is stored in Markdown files. But deploying it correctly isn't just copying files: mistakes in .htaccess or nginx config kill performance. We'll show you how to install Pico CMS, set up the server (Nginx or Apache), add plugins, and speed it up with Twig cache. You'll get a site that loads faster than 95% of competitors on the same hosting, while saving up to 70% on hosting compared to WordPress. Contact us and we'll help configure Pico for your project.

How to Install Pico CMS via Composer?

Use Composer—it guarantees the latest version and simple updates. Alternatively, you can download the archive, but we recommend Composer. The code is available in the GitHub repository.

composer create-project picocms/pico-composer /var/www/mysite
cd /var/www/mysite

Five steps to a working site:

1. Install Pico via Composer.
2. Set permissions on config, content, cache folders (755 for folders, 644 for files).
3. Create a web server config (Nginx or Apache).
4. Open the site—you should see a placeholder.
5. Add your first content in content/index.md.

Why Pico CMS Beats WordPress?

Pico CMS outperforms WordPress: on one project we replaced WordPress with Pico—TTFB dropped from 3.2 s to 0.2 s, and LCP went from 4 s to 0.5 s. The absence of a database reduces server load and simplifies backups—content is just files. Also, Pico doesn't require constant updates like heavy CMSs. Hosting savings can reach 70%, and page load speed improves Core Web Vitals (LCP, CLS) into the green zone. For example, after deploying Pico on shared hosting, TTFB rarely exceeds 0.3 s even at 10,000 visits per day.

What's Needed for Pico CMS Server Setup?

Nginx

Standard config with redirection to index.php and protection of service directories:

server {
    listen 80;
    server_name mysite.com;
    root /var/www/mysite;
    index index.php;

    location / {
        try_files $uri $uri/ /index.php?$query_string;
    }

    location ~ ^/(config|content|lib|vendor|\.git) {
        deny all;
        return 404;
    }

    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.1-fpm.sock;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        include fastcgi_params;
    }
}

Apache

Pico ships with a ready .htaccess. Just enable mod_rewrite:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ index.php [QSA,L]

<FilesMatch "\.(md|yml|yaml|twig)$">
    Order allow,deny
    Deny from all
</FilesMatch>

Configuring config.yml and Plugins

The config/config.yml file defines site title, theme, date format, page order, and enabled plugins. Example working config:

site_title: My Site
base_url: ~                 # auto-detect
theme: my-theme
twig_config:
  autoescape: false
  cache: false              # enable in production: 'cache/twig'
  debug: false
date_format: 'd.m.Y'
timezone: 'Europe/Minsk'
locale: ru_RU.UTF-8
rewrite_url: true
pages_order:
  by: alpha
  asc: true

Plugins go in plugins/. Manual install: copy the plugin folder or use Composer. Pico automatically detects all plugins with a {PluginName}.php file. Essential plugins:

Content Structure and Page Management

Content lives in content/. Files have .md extension. Sorting is by file name; to force order, use a numeric prefix: 01.about.md, 02.services.md. Files starting with _ are hidden from navigation (e.g., _navigation.md). Example structure:

content/
  index.md
  404.md
  _navigation.md
  about.md
  services/
    index.md
    web-dev.md
    mobile.md
  blog/
    index.md
    %year%/
      my-post.md         # /blog/2024/my-post

How to Enable Twig Cache in Production?

In config.yml, change cache: false to cache: 'cache/twig'. The directory must exist and be writable. When content or templates change, clear the cache: rm -rf /var/www/mysite/cache/twig/*. This typically cuts page generation time by 50%.

Configuration Checklist

• PHP 8.0+ with mbstring and dom extensions.
• Permissions on cache and config folders: 755.
• RewriteEngine enabled (for Apache).
• Access to service folders denied.
• Twig cache active.

What's Included in the Pico CMS Setup Service

We don't just install Pico—we configure it for your project. The service includes:

• Deployment on the server (Composer or archive).
• Nginx/Apache configuration with optimization (compression, caching).
• Installation and configuration of basic plugins (sitemap, feed).
• Enabling Twig cache for faster page loads.
• Creating a content structure with sample pages.
• Documentation for management.
• Stability guarantee: over 5 years of experience with Pico, 10+ implementations.

Comparison with WordPress: Pico's TTFB is 8 times lower, and server load is minimal. Save up to 70% on hosting.

Order Pico CMS setup — get a ready-to-use site in 1 day. Contact us for a consultation.

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.