BigTree CMS

cms

PHP/MySQL CMS focused on developer ergonomics. Modular field types, a clean admin UI, and multi-site support built in — designed to be straightforward to customise without a steep learning curve

#cms#php#mysql#self-hosted

Quick Start

git clone https://github.com/bigtreecms/BigTree-CMS.git && cp BigTree-CMS/site/index.php . && # configure database in /site/config.php

Overview

BigTree CMS is a PHP/MySQL content management system built with developer workflow in mind. Rather than layering functionality through plugins, BigTree provides a structured field type system where developers define the exact inputs editors see for each content type. Text fields, image uploaders, repeater groups, date pickers, and custom field types are defined in code and rendered as a clean admin interface.

The admin UI is genuinely clean. There are no menus full of options editors will never touch, no plugin settings pages with confusing toggles. What is visible in the admin is what the developer decided to expose. For agencies building sites they will hand off to clients, this predictability reduces support requests.

Multi-site support is built into the core, not an add-on. A single BigTree installation can manage multiple domains with separate content, separate user permissions, and separate templates. For agencies running a portfolio of small client sites, this can simplify infrastructure compared to running separate WordPress installations per client.

The limitations are tied to the project’s size. With 222 GitHub stars and an infrequent release cadence, BigTree is a niche tool. The ecosystem of ready-made integrations, payment modules, and e-commerce features that exists for WordPress or Craft CMS does not exist here. Any integration with a third-party service means custom development. The documentation is solid for what it covers, but community help beyond that is limited to GitHub issues.

For developers who want a lean, predictable CMS foundation without WordPress’s weight and are willing to build custom functionality, BigTree is functional. For projects that need breadth of integrations or an active support community, the tradeoff is significant.

Use Cases

Specific ways to use BigTree CMS for your workflow.

01
Build a content-managed site where developers want clean field type control without wrestling with a plugin ecosystem
02
Run multiple sites from a single install using the built-in multi-site management
03
Create a structured content admin for a custom application where the front end is handled separately
04
Hand off a site to a client with a clean admin panel that does not expose unnecessary complexity

Deployment Strategy

Recommended ways to host BigTree CMS in your own environment.

docker
self-hosted