The power of GraphQL schema definition language

by Peter Balazs on 11/10/2018

We wanted to build Mozaik in a way that enables content type schema management programmatically. The first version made it possible to define content types as JSON objects and to make calls to the API to manage schema. Although it was a safe first step, there were a few issues: on a larger project or when there are multiple content types that are dependent on each other. It was a must to calculate a dependency tree and run the API calls to create the different types and fields in that order. Also with many content types, the content type declaration becomes way too verbose and harder to manage or understand. So we turned to the GraphQL Schema Definition Language (SDL) for help.


Content preview for Gatsby projects

by Peter Balazs on 28/09/2018

Previewing content before publishing changes is an essential part of content editing workflow. However, this was a missing piece of the content editing workflow supported by Mozaik. But not any more. Today, we're are excited to announce closer integration with Gatsby, and out of the box content preview support.


Schema definition with GraphQL SDL

by Peter Balazs on 02/08/2018

With the release of our Javascript SDK, you can now define your project's schema with the GraphQL schema definition language. Later on, you can change this schema file to evolve your project, and the SDK will take care of handling the migration.


Mozaik Javascript SDK

by Peter Balazs on 30/07/2018

One of our primary goals is to give the best tools and experience to developers. To make your work as productive as possible. This is why we've created an SDK and CLI tool that you can use for managing workspaces and projects either from custom scripts or using the command line.


Integrating Mozaik API into an existing GraphQL schema

by Peter Balazs on 12/03/2018

The main benefit of GraphQL is that you can query all of your data in one request. However, when you want to add a new service to your application you either need to update your existing GraphQL schema and implement all resolvers to map the new service or expose another endpoint. Both cases can result in a lot of extra work. Especially when the new service you want to integrate into your application already has a GraphQL API. This is the problem that you can quickly solve with Apollo schema stitching.


Building static sites with Mozaik and Gatsby

by Peter Balazs on 21/02/2018

Building static sites with Gatsby and Mozaik can't be easier: download our source-plugin and get your project started! Our example project has all the answers: query definition, programmatic page generation, automatic deployment to Netlify.


Content type schema as code

by Peter Balazs on 05/02/2018

In a CMS it is a must for editors to have full control over the content. To be able to create drafts, publish immediately or schedule for a given time, to be able to check the version history, rollback to a previous version if necessary. If they have these controls, why can’t developers have similar?


What comes next?

by Peter Balazs on 05/12/2017

In the past couple of weeks, we've been busy cleaning up the content editor UI, fixing small issues, and doing some work on our backend and infrastructure. But we thought it would be useful to lay out our future plans for the features we want to deliver for the best content management experience for both developers and content editors.


Introducing Mozaik

by Peter Balazs on 14/11/2017

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.