The example JeaseCMS is built on top of a content management framework (CMF) which provides the building blocks to develop content-driven web-applications very easily.

If you're starting with Jease, it is a good idea to skip the CMF and dive directly into the CMS. Later on you can come back and learn what is going on under the hood.

The CMF is divided into three layers:

jease.cmf.domain
Here you'll find the central definition for a Node, which is the common super class from which all custom content types needs to be derived. A Node stores an id, a reference to a parent and an array of the children of a Node to let you build and manipulate tree-like data-structures very easily. A Node is mostly a simple Pojo, which doesn't know anything about persistence or rendering its contents.

jease.cmf.service
The service-layer provides means to persist Nodes into the persistence storage (= object database).

jease.cmf.web
All out-of-the-box gui-components for your CMS (e.g. tree navigation, searchable tables, editors, drag&drop, ...) are wired together in the main Jease-Object which is something like a meta-component and pulls its configuration out of a custom JeaseConfig which is stored in a JeaseSession.