Content is king, we’ve been hearing this for decades. But as the Internet evolved, the meaning of content broadened. Any time we create a new website, web application or mobile app, we have to care about content. Gone are the days of build-it-once chuck-it-in static content. Content now is richer, more engaging, interactive, and ever-changing. It breathes.
And as a developer, that raises some questions: Where should I store our content? How can I add or edit rich (and not only text) content? How can I evolve our data model without breaking existing pages?
The obvious answer is to adopt a content management system. Originally a CMS gave you a way to store your data and manage how to display your content. However, in the past couple of years, there's been a trend to move away from traditional content management systems to headless CMS solutions. This approach helps you decouple your presentational layer from your data and makes it easier to display your content in any medium you want to.
But this leads to a new problem: we should be able to define what part of our content is loaded for different applications.
There are quite a few headless CMS services already, but we were not satisfied what they offer. They contain too many limitations that poorly impact both developers and content editors. We believe that you shouldn't have to compromise between the developer experience of managing a CMS and the need for editors and designers to create the best content for their product or service.
This is why we created Mozaik. We introduce some new and familiar concepts which we believe can liberate editors, designers, and developers and help them create more innovative solutions.
In the coming days, we will be posting more in-depth details about the current features and our plans for the future. Until then, if you have any questions or you'd like to request a feature, just send us an email at firstname.lastname@example.org and we're happy to help.