Architecture

onion.net consists of several building blocks:

• In the onion.net information server all information, schemata, users and rights are administrated centrally
• The onion.net editor is the web application in which contents, schemata, users and rights are clearly administered
• The onion.net render engine is the central transformation tool for information utilisation, e.g. the output of a website
• The onion.net client API supports the development of own components and provides each function of the onion.net information server without exception

You can connect as many onion.net render engines, onion.net editors and onion.net client API applications to the onion.net information server as you wish, which can all run on different machines. onion.net can be well scaled and is also suitable for very large projects.

It is important to understand, that onion.net is a de-coupled CMS, i.e. it separates the repository and the presentation tiers. If you don't want to publish to the web, or just fell in love with the headless CMS approach, you can use the onion.net information server and the editor headless. However, we'd suggest to use the onion.net render engine for web publishing - elsewise we would'nt have bothered to build it.