picocms.org

What It Is

Pico is a flat-file CMS built with PHP. It does not provide a traditional admin backend and does not rely on a database. Instead, site content is stored as Markdown files in the content directory; creating a .md file is essentially the same as creating a page. Page metadata is placed in a YAML header at the top of the file, while the presentation layer is handled by Twig templates. The official positioning makes it clear that Pico is not a “one-click” ready-made website solution, but rather a simple architecture designed for speed, flexibility, and low maintenance.

Core Features and Developer Experience

In terms of functionality, Pico’s core revolves around Markdown content management, YAML metadata, Twig themes, and PHP plugins. It supports Markdown Extra and also allows HTML inside content. Themes can implement dynamic rendering through Twig, and the default theme is better viewed as a starting point for development rather than a production-ready template. The plugin system is based on event hooks, allowing developers to modify behavior during stages such as page loading; DummyPlugin provides examples of available hooks. Installation options include Composer, pre-packaged releases, and a Git repository workflow, making it suitable for self-hosting on web space that supports PHP 5.3.6+ along with the dom and mbstring extensions.

Pricing, Open Source, and Ecosystem

Pico is completely free and open source under the MIT License. The source material does not mention any commercial edition, hosted version, or paid support, so its costs mainly come from servers, domains, and maintenance time. In terms of ecosystem, Pico has community themes and plugins, and it integrates closely with Composer, Packagist, GitHub, and Git-based workflows. The documentation covers installation, upgrades, content creation, blog usage, themes, plugins, URL rewriting, and Apache/Nginx/Lighttpd configuration, making it generally developer-friendly.

Pros, Cons, and Who It’s For

Its advantages are that it is lightweight, database-free, easy to migrate, and allows content to be managed with Git, while also having a relatively small security surface. It is well suited to personal websites, documentation sites, portfolios, and small content sites. The downsides are also clear: there is no admin interface, so it is not ideal for teams that depend on visual editing and complex permission workflows. Features such as blogging, authentication, tags, and pagination require plugins or custom implementation. If you are not familiar with PHP, Twig, HTML, or server configuration, you will still need to spend time reading the documentation before getting started.

Access from China and Alternatives

The crawled text does not provide information about access from mainland China, mirrors, payments, or CDN support, so its access status is marked as unknown. Since Pico is self-hosted open-source software, Chinese users can deploy it on domestic servers, and payment considerations mainly depend on the chosen cloud provider. If you need a more mature backend, WordPress may be a better fit; if you prefer a flat-file CMS, Grav is worth comparing; and if you lean more toward static site generation, Hugo, Jekyll, and similar tools are alternatives to consider.