One of Frontender’s key features is its what-you-see-is-what-you-get graphical user interface. With this interface, you can create webpages — even when you know nothing about web technology. The process is disarmingly simple: just insert the desired interface containers onto a “webpage” and publish.
At Frontender, we are very excited about this feature as it realises our vision for Frontender as a tool for communication professionals to create and manage websites without the help of a developer.
I am a smart piece of software for making enterprise websites. One part of me lives on your computer. You use that part of me to create all your websites. The second part of me lives on your server. That part serves your sites to your users.
My strong point is my interface. I am a lot of fun to use. I have a genuinely what-you-see-is-what-you-get interface for composing and publishing websites. You don’t need to be a rocket scientist or a web developer to use me. You can even customise me to fit your workflow.
Design systems — and by extension pattern libraries — have become an integral part of our daily job as web developers and designers. Developers use pattern libraries to create new interfaces, reusing the interface components and their source codes to maintain consistent styling and user experience between publications.
What is surprising to me is that pattern libraries are not exposed to marketing and communication professionals. While this group of digital experts has less use for the higher levels of abstraction in the pattern library (or the code), they would benefit from a practical overview of available interface components.
Traditionally, a content management system (CMS) is a data store, an editorial interface and a templating engine in a single system. A headless CMS is optimised for editing and storing content and does not have an incorporated frontend templating system. Presentation of its content relays to another application like Frontender.
A headless web system consists of multiple self-governing applications like this, that communicate with each other. That is what makes headless a highly flexible and extensible infrastructure, where parts are replaced quickly and new elements slot in as and when needed.
Output requirements often drive website architecture; in my experience…