DEV Community: Wellington Pragidi

I Didn't Set Out to Build an Open Source CMS. I Just Needed One

Wellington Pragidi — Mon, 07 Sep 2026 15:18:58 +0000

Initially born out of practical necessity and real headaches, not from a romantic idea of something like “revolutionary free software”. I have been working on it alone for quite some time, creating, updating, and managing websites with the same system. I decided to open-source it because if it works well for me, it may work well for others too.

How the project started

I used to maintain an entertainment website that started on Blogger and later moved to WordPress. As the project grew, I needed to customize themes, create my own plugins, and extend its functionality. Eventually, the WordPress ecosystem started to make the process feel restrictive.

That was when I decided to build a system from scratch, tailored specifically to what I needed.

The problem came later: I decided to run that same system on my agency's website (webship). Suddenly, I had two similar but separate systems running in parallel. The only documentation that existed was my own memory and a few comments in the code. Updating both became a nightmare.

To avoid going crazy maintaining duplicated code, I decided to unify everything into a generic codebase. And it was this need to get things organized that eventually turned OpusCore into an Open Source project on GitHub.

(Note: I still take WordPress jobs when a client specifically asks for it. Let's just say I don't exactly enjoy it.)

I'm not trying to compete with established frameworks or CMSs, but rather to have autonomy. Of course, comparisons with WordPress are inevitable, first because of the problem described above, and then for the obvious reason that it is the most widely used CMS in the world. But this isn't about competing for its space. They are different approaches. WordPress has its enormous ecosystem. OpusCore follows a different path: more freedom to build without crutches and without asking for permission.

Technical decisions

Layered performance: I treat performance like security: you don't get a fast system by applying a single isolated optimization. It requires continuous attention at every layer.

Visible SQL (without excessive abstraction): I don't like the idea of hiding SQL behind huge ORM abstraction layers. In OpusCore, database queries remain visible, simple, and straightforward.

If maintaining code is already work, imagine hiding that code behind unnecessary abstractions.

Simple dependency injection: The system uses a container for instances, taking advantage of what modern frameworks do well. The difference from something like Laravel or Symfony is that here it is a lean class, without dozens of stacked dependencies.

Environment structure: The code does not use namespaces. It is organized and separated into three clear environments: web (public), dashboard (administration panel), and dist (distribution).

The goal is to provide the essentials needed to run a complete website without having to install anything from a few plugins to dozens of third-party plugins for basic features.

Native OpusCore features

Integrated SEO: Automatic generation and updating of meta tags and sitemap.xml, with configurable options directly from the dashboard.

CSS management: Stylesheets can be loaded in <style> or <link> blocks, with minification and conditional loading (when using blocks).

Context Architecture: A publishing block in the dashboard that can be injected into any route through a keyed function in the template.

Security and Users: Login routes are separated from the site's administration, with a user.php file for user profiles.

Optimized Media: Featured images are handled separately by entity, avoiding the creation of multiple unnecessary image sizes that clutter the server's disk.

Optional native features: An asynchronous comment system, conditional script loading, an SVG helper, and integrated sharing buttons.

The main reason I'm sharing this here is that developing and maintaining a system of this size alone for years creates the famous “blind spot”: you get used to your own code and stop seeing its flaws, sometimes even the obvious ones.

OpusCore has room for improvement, and it will. That's one of the reasons I opened the project to the community.

If you're looking for, or interested in, a tool and management system for building your own projects, rather than a tool that tries to build them for you, take a look at OpusCore.

Technical feedback, suggestions, and criticism are welcome and necessary.

GitHub:
https://github.com/wellingtonpragidi/opuscore

Download:
https://opuscore.dev/download

Do you really need all of this to build a website?

Wellington Pragidi — Tue, 18 Aug 2026 02:06:10 +0000

You need to build a site.

So you install a CMS, and then:

• You need an SEO plugin

• Then another plugin for forms

• Yet another one for user management

• And one for optimization

• Image manipulation

• And suddenly, a plugin requires even more plugins. Before you know it, that simple site has a whole population of plugins living inside it.

Opus Core was born from a different perspective.
What if the foundation already came equipped with the essentials you need to build?

An open-source Web Content Manager built with PHP, featuring:
✓ Clean and intuitive control panel

✓ User profiles and commenting system

✓ Instance container

✓ Fully integrated SEO

✓ Asynchronous loading lists

✓ Stylesheet loading via <style> and/or <link> blocks, with minification and conditional loading

✓ Automated manifest.json generation

✓ Contexts

And much more...

The system relies on a database for most tasks, utilizing file storage where it genuinely makes sense.

Each approach is applied based on its practical value within the system.

Without trying to be everything to everyone.

Keep in mind that while the tool provides structure and direction, it doesn't strictly enforce how you use it.

How each developer leverages the system remains their own responsibility.

No architecture can replace technical judgment.

Opus Core is available.

Download it. Install it. Inspect the code. Test it out.

Download: https://opuscore.dev/download

GitHub: https://github.com/wellingtonpragidi/opuscore

Você realmente precisa de tudo isso para fazer um site?

Wellington Pragidi — Tue, 18 Aug 2026 00:33:11 +0000

Você precisa construir um site.
Aí então instala um CMS, e depois:

Precisa de um plugin para SEO
Depois outro plugin para formulário
Mais um para usuários
E para otimização
Manipulação de imagens
E então um plugin requer mais plugins Quando percebe, aquele site simples já tem uma população de plugins morando dentro dele.

O Opus Core nasceu de uma ideia diferente.

E se a base já viesse preparada com o essencial para você construir?

Um Gerenciador Web open source em PHP, com:
✓ Painel de controle limpo e intuitivo
✓ Perfil de usuários e comentários
✓ Container de instância
✓ SEO totalmente integrado.
✓ Listagem por carregamento assíncrono.
✓ Carregamento de folhas de estilo por bloco <style> e/ou <link>, com compactação e carregamento condicional.
✓ Geração de arquivo manifest.json
✓ Contexts
E muito mais..

O sistema utiliza banco de dados na maior parte, e armazenamento em arquivos onde isso realmente faz sentido.
Cada abordagem é utilizada conforme sua utilidade prática dentro do sistema.

Sem tentar ser tudo para todos.

Lembrando que a ferramenta oferece estrutura e direção, mas não controla completamente quem a usa.
A forma como cada desenvolvedor utiliza o sistema continua sendo responsabilidade do próprio desenvolvedor.

Nenhuma arquitetura substitui critério técnico.

O Opus Core está disponível.
Baixe. Instale. Abra o código. Teste.

Download
GitHub

Apresentando o Opus Core, um CMS open source em PHP, feito para quem gosta e colocar a mão na massa e ter controle Sem depender de addons Nascido de necessidades reais Download: http://opuscore.dev/download GitHub: github.com/wellingtonpragidi/opuscore

Wellington Pragidi — Wed, 12 Aug 2026 00:56:27 +0000

opuscore.dev / download