It’s 2016 — Rethink CMS
The xpos.it manifesto
The open-source CMSs that exist today must change. Why? Because they do not meet the demands of the users. Websites are more complex, the demand for simplicity is higher and — most importantly — the people who build these systems, have changed beyond recognition. The systems that we all know have changed so far. Still WordPress, Drupal, and others were developed by developers for developers. When designers were pushed into a corner, the functionality was imposed on them, they were forced to use pre-written templates, and felt generally limited.
Today the situation is different — the lines between design and coding are becoming blurred, web designers are taking over the development process with the introduction of new tools that make coding a snap. When it comes to converting the static files into dynamic CMS, here comes the pain.
You can call this process data binding, or whatever, and it can only be done by a developer who knows the specific CMS “rules”. It takes a lot of time, developers want to focus on real functionality, not on binding data into design, while designers want to focus on design, and bring great experiences to their clients, the content managers.
We want to bridge this gap.
The cutting-edge solution is xpos.it — a visual web creation platform. It empowers designers to easily bind any static design to a database while developers can focus on the real code, and content editors can enjoy a “Zen” in-place editing experience. Design can go to execution in a snap; it makes ideas become reality, fast. We actually say — “Bring your HTML and we will take care of the rest”.
While others focus on content management as a back office product with complex development integrations and complex dashboards, xpos.it’s agenda is to form these habits by connecting the content with the ability to build and manage it, by keeping it visual as much as possible — it’s the natural thing to do.
We have the opportunity of re-thinking the whole idea of CMS, the way people publish content and building experiences for the web, it demands strong tools, not only a CMS. We want to do it, to connect the front-end with the back-end, and draw a clear line between each layer in the stack, to start getting it in a visual way.
In other words — It’s 2016, rethink CMS. Design now defines the process.