A system designed for content creation might not be suited best for publishing and delivering content to the end user.
The Two-Stack CMS architecture pattern has the idea of using two separate software stacks for editing/creation and publishing/delivery of content. This separation has the great advantage of matching different scalability and security requirements for each stack.
Can Neos be used as a Two-Stack CMS? And what are the implications for the editor and developer? In this talk I will present a production-ready solution using a Redis based content store with different frontend implementations and an outlook for an even more decoupled publishing architecture.
