How I Built an Open-Source Modular CMS on Laravel 12 with a Visual Builder and OpenRouter AI
I wanted a CMS that felt modern: self-hosted, modular, with a real visual builder and AI built in rather than bolted on. So I built one. This is RJ CMS (NEXUS), an open-source CMS on Laravel 12, and this post covers what
I wanted a CMS that felt modern: self-hosted, modular, with a real visual builder and AI built in rather than bolted on. So I built one. This is RJ CMS (NEXUS), an open-source CMS on Laravel 12, and this post covers what it does, how it's structured, and what I learned.
Heads up: RJ CMS is under active development (v1.0.0-alpha). Expect bugs and breaking changes. It's not recommended for production yet. I'm sharing it early because feedback is what it needs most.
Repo: https://github.com/rj-nexus/rj-nexus
Live demo: https://rj-nexus.onrender.com
Why another CMS?
[Write 2-3 sentences in your own words: what frustrated you about WordPress / other CMSs, and what you wanted instead.]
My goals were:
- Self-hosted: you install it on your own server and own your data.
- Modular: features live in plugins that never touch the core.
- Builder-first: themes and pages are designed visually.
- AI-native: SEO, translation, and writing help built into the admin.
Tech stack
| Layer | Technology |
|---|---|
| Backend | Laravel 12, PHP 8.2 |
| Database | MySQL |
| Frontend | Blade, Tailwind CSS v3, Alpine.js |
| Build tool | Vite |
| AI engine | OpenRouter API |
I kept the frontend stack deliberately light: Blade and Alpine.js instead of a heavy SPA, so the admin stays easy to extend for any Laravel developer.
RJBuilder: the visual page builder
The centerpiece is RJBuilder, a drag-and-drop page editor. It includes:
- Responsive controls per breakpoint
- Nested containers
- Custom CSS/JS
- Dynamic tags
- Undo/redo history and animations
- 8 built-in widgets
[Add what was hardest here: state management, history, responsive controls, etc. A short code snippet or screenshot/GIF would work great.]
A plugin system that never touches the core
Plugins are fully isolated. Each one has its own routes, views, migrations, and assets, loaded through dynamic autoloaders and service providers. The core never needs to be modified, and updates are delivered through GitHub.
There's even a Plugin IDE: a built-in code editor in the admin with AI code review.
The first real plugin is a Form Builder (v1.1.0), which is how I'm stress-testing the plugin architecture: https://github.com/mr-ruhid/rj-plugin-form-builder
Theme architecture
Themes are builder-first: active theme loading, view namespaces, custom page templates, child themes, and dynamic asset injection. [Explain in a sentence why you chose this approach.]
AI with OpenRouter
AI is integrated through OpenRouter, which means you're not locked into a single model provider. The built-in tools can:
- Generate SEO meta tags
- Translate content
- Write text
- Suggest page layouts
- Run AI-powered SEO analysis
[Explain why OpenRouter: model choice, one API key, cost control. Mention how the API key is configured in Settings → AI.]
Multi-language and SEO
Built-in locales are AZ, EN, RU, and TR, plus dynamic locales. Posts, pages, categories, and SEO data are all translatable. On the SEO side you get control over titles, descriptions, Open Graph, Twitter cards, and schema markup.
Everything else included
- Media library with drag-and-drop upload and image optimization
- Multilingual categories and tags
- Menu system (header, footer, custom locations)
- Role-based access control with activity logging
- Settings for General, AI, SEO, Security, and more
Try it locally
Requirements: PHP 8.2+, Composer, Node.js, MySQL.
git clone https://github.com/rj-nexus/rj-nexus.git
cd rj-nexus
composer install
npm install
cp .env.example .env
php artisan key:generate
# set your DB credentials in .env
php artisan migrate --seed
npm run dev # in one terminal
php artisan serve # in another
Default local admin: [email protected] / admin123. These are for local development only, so change them immediately on anything reachable from the internet.
Roadmap
Done: auth, settings, media library, categories/tags, menus, posts/pages with AI, RJBuilder core, theme system, plugin engine, Plugin IDE.
In progress: Form Builder polish, admin UI for Post Types/Roles/Themes/Plugins, frontend views (single post, archive, loop cards), a dedicated AI Center.
Planned: role-based permission middleware, maintenance mode, RTL support, custom post type builder, custom fields (an ACF alternative), notifications.
Lessons learned
[Add 3 honest lessons, for example: what you'd do differently, a design decision you regret, something that surprised you about plugin isolation or AI prompts.]
Contribute
RJ CMS is MIT-licensed. If you try it, I'd love to hear what breaks. Open an issue, send a PR, or just drop a comment below. A star on GitHub also helps a lot:
👉 https://github.com/rj-nexus/rj-nexus
Live demo
You can see it running here: https://rj-nexus.onrender.com
The demo is hosted on Render, so the first load may take a few seconds if the instance was sleeping.
What would you want most from a modular Laravel CMS? Let me know in the comments.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.








