Neos as hybrid CMS / beyond Neos

In recent years, there have been discussions and developments in the area of static sites. Today, the editor doesn't need to write the plain HTML, but he can use static site generators like Jekyll, Next, Hugo or Gatsby. The generated pages are really fast, even without caching on the server-side.

This leads us to our topic of the talk: Why should I generate a static site? Which tools could I use? We would like to show you two different approaches based on Neos for content editing.

With Photon, Christopher developed a package that enables Neos itself to generate static sites and you get the benefit of the great editor user experience and the fast site.

In the second approach we use Neos as a content aggregator and Gatsby consumes the content via a GraphQL API to generate the static site. So here Neos is not used for rendering, but for curating and aggregating content.