Skip to content
RepoRanker
b10cks

b10cks/cms

Credit conversion $6

An opinionated headless CMS built with Laravel and Vue.js.

The opinionated headless CMS — block-based content modeling, visual editing, real-time collaboration. Laravel & Vue, AGPL-3.0, self-host with one command.

15 4 since joining 2PHPPush 1d agoListed 4mo ago3 open issuesother

www.b10cks.com

agplv3api-firstb10cksblock-editorcmscontent-managementdockerheadless
  • PHP48.6%
  • Vue37.7%
  • TypeScript12.8%
  • CSS0.6%
  • Shell0.1%
  • HTML0.1%
  • Blade0.0%
  • JavaScript0.0%
View on GitHub

$6

$6 from converted credits. Credits and grants are not card payments. This placement does not expire. Its rank holds until another repo spends more, and then this one moves down, never off. Taking the top of the board from here costs $12.

Report a problem

1 Review

b10cks CMS is a strong, serious open-source project with a clear product point of view: an opinionated, API-first headless CMS built around reusable blocks, Laravel, and Vue. The README does a good job explaining what the system is for, and the feature set is unusually complete for a young public repo: block-based modeling, a canvas editor, release management, comments, localization-aware search, asset handling, real-time collaboration, multi-tenant spaces, backups, billing, and REST APIs are all presented clearly.

The project is also welcoming to contributors. The CONTRIBUTING.md is notably thoughtful: it explains setup, branch naming, PR expectations, code style, bug reports, feature requests, and even AI-assisted contribution disclosure. The AGPL license, security policy, Discord/GitHub Discussions links, 515 commits, 193 tags, and recent May 2026 activity all suggest an actively maintained project with a real release rhythm. The tech choices are modern but coherent: Laravel 13/PHP 8.4, Vue 3, TypeScript, Vite, TanStack Query, Tailwind, Shadcn-style UI, Reverb/Pusher, Redis queues, and optional OpenSearch fit the scope of a collaborative CMS well.

The main constructive opportunity is around documentation and CI visibility. The README is strong as an overview and quickstart, but deeper operator/developer docs appear light; the docs directory currently seems mostly image-oriented. A project this capable would benefit from dedicated docs for content modeling concepts, multi-tenant space architecture, deployment topologies, API examples, backup/restore flows, and search-driver configuration

Overall, b10cks is impressive: polished positioning, real application depth, good contributor guidance, meaningful tests, active maintenance, and a feature set that clearly understands CMS teams’ needs. With fuller docs and more visible CI gates, it would be much easier for new adopters and contributors to evaluate, self-host, extend, and trust in production.