UMONO

View on Github Roadmap

Umono is an open source content management system. It is already under development to be a real-world content management system. But you can demo or build production its released v0.4.0. View on github repository for more tecnical details.

Features

• 🍃 Pure & Robust
• 🚀 Too Fast
• Component Based
• Compatible with CommanMark
• A domain-specific language, UmonoLang

Why and how did I decide to start Umono Project?

I want to tell something about content management systems. In this way you will understand my motivation to start developing Umono.

Content management systems are useful for non-programmer people who want to build own blog, e-commerce etc. website themselves. It is necessary for content management systems to be ready to use out of the box and to run correctly, but that alone is not enough. They also must keep rights, responsibilities and limits of website owner, users, plugin developers and theme developers from each other. Otherwise:

• A plugin developer may knowingly or unknowingly write a bloatware plugin. The plugin can make the website slow or break it.
• When a site owner uses a third party theme, if the theme developer stopped developing the theme project the website becomes defenseless from undiscovered security vulnerabilities.
• Users' personal data can be stolen by a plugin that must not have authority to reach database table containing sensitive data.
• A site owner can encounter theme or plugin updates that change his website functionality or appearance.

We can add more points.

In the ideal scenario plugins, themes and contents of a website should be separated from each other with dark lines. The method provides site owners freedom to change current theme, plugins or contents. The method also provides developers flexible and free development environments. When developers have completed their stable projects, they expect it to run correctly for each instance. In an environment that tightly coupled, developers cannot be sure what their projects run correctly or not for each instance.

Actually, the main problem is the tight coupling between themes, plugins, and content. I aim to solve this problem with the Umono Project by using isolated and loosely-coupled layers.

You can support me in developing Umono Project, which I'm currently working on alone, by starring my GitHub project and providing feedback.

Yunus Emre Bulut

Made with Umono ♥️