An edition is a collection of items, typically articles. An edition belongs to a product.
There are different types of products, like front page, magazine, and print. The type of product determines how you view and edit the editions within that product.
A content schema defines what properties are available for editing in the edition view, and what data you will receive when fetching editions from the DrEdition API.
A content source is used to give DrEdition access to the content of your CMS/article system. DrEdition expects the content source to return JSON data, but it has few requirements to how your data is structured, which is handled by the mapper function.
It's based on a URL template, with optional default parameters, content queries and a mapper function.
Content queries are more refined queries against a Content Source. It could be the 50 latest published articles, or only from a specific category, tag, etc.
You can have multiple Content Queries towards a single Content Source.
A product url can be used to link from an edition to related resources. The classic example is a url where you can preview the edition, but you can also configure urls for where to find statistics, plan the edition etc.
Event callbacks are urls which will be triggered at certain events, ie. when an edition is published.
An editorial groups represents a logical grouping of products, users and settings. They help you manage the complexity of your organisation by providing your users with just the views they need.
With automations, you can schedule updates to your editions based on new content available in your content sources. This can be used to partly or completely automate your editions.
Transformations can transform a flat list of items into a list of groups, based on a very flexible set of rules.