Using Drupal 8, PostgreSQL 9.6.5, PHP 7.1 and Apache 2.4.6
The articles have a mandatory field called "Category" that is used to create the URL path and to filter them.
There are two images fields, the rectangular and the square, depends on the design we will use the one or the other.
The editor can use the field Tags, used in the Archiv page "/content/journal/archiv" to search by the Facet Tag.
There are two fields where the author can write text, the body and the marginal. The first one it is displayed in the center of the page,
and the second one is used to create the right sidebar of the page.
Uses when it is selected the detail page of the content
As the name says, it is used in the Journal Overview Page to create the teaser with Square Image.
As the name says, it is used in the Journal Overview Page to create the teaser with Rectangular Image.
Uses the image with size L in the list by category of articles
Uses the image with size M in the /journal/archiv page
Uses the image with size M in the block "You might also be interested in"
This content is only editable for the Drupal Administrators, and it was created to create in Drupal the Person and the Kalenderblatt blocks that later it will be filled with content in the Frontend.
It is also used to create the /journal page, that is a collection of blocks when this page was created, the Panels module was not ready to be used.
Uses the module Panelizer to create the HTML structure of /journal
As the name says, it is used in the Journal Overview Page to create the teaser with Square Image, uses for Person and Kalenderblatt.
As the name says, it is used in the Journal Overview Page to create the teaser with Rectangular Image, uses for Person and Kalenderblatt.
It is used to create general pages content that is not articles, it has only two fields, body and marginal and they are used as the ones in Articles.
Uses when it is selected the detail page of the content
Using the simplenews module it was created this content type with a specific field structure to follow the DDB Newsletter design.
Some part of this content is filled it by default like the footer, these contents can be sent as a normal newsletter.
This content uses Paragraphs in is structure, in order to have more than one element with the same HTML structure but allow the editor to decide how many elements want to create in each content.
Uses when it is selected the detail page of the content
The version of the content uses when the newsletter is sent.
What makes different this content are the fields Date period, Place and Category Event.
The place is a simple text but the Category Event is a taxonomy, that when the user type in the field will check if exits already in the system.
Those fields are used as facets in the Events page /ueber-uns/termine that includes a facet calendar.
Uses when it is selected the detail page of the content
Teaser
This display mode is used in /ueber-uns/termine in each item of the list.
This content type is used only to create in DDB Journal some teasers list, but the detail page of those contents are not available from anonymous users,
it is used the external link URL to link those exhibitions with the element from http://ausstellungen.deutsche-digitale-bibliothek.de
As the name says, it is used in the Journal Overview Page to create the teaser with Square Image.
As the name says, it is used in the Journal Overview Page to create the teaser with Rectangular Image.
This display mode is used in /journal/ausstellungen in each item of the list. Uses the Image Square L as the category list pages of articles
Created using the FAQ module from Drupal. It has a category field to be used as a filter.
Uses when it is selected the detail page of the content
It has the same fields as Basic Page, created as another content type in order to have the content separated.
Uses when it is selected the detail page of the content
/admin/structure/views/view/fragen_und_antworten?destination=/de/admin/structure/views
Custom Module "DDB Journal" that is a sub-theme from the Bootstrap Theme, that it uses Bootstrap 3.
Drupal Cron runs every 3 hours, checking the current status of the site, including checking the new version of modules/core.
The global configuration of the cache for all the pages is 1 day, apart of that we are using a module called "Advanced page expiration" to decide which pages
should not be cached, we are using it to don't cache the /journal page, in order to see the person block rotate.
We have learned that the module is very sensitive and if the URL that you don't want to cache uses some parameters you have to put all the options with all the parameters to don't be cached.
More Info: https://cms.deutsche-digitale-bibliothek.de/en/admin/config/development/performance/ape
The DDB anonymous users don't use DDB Journal to subscribe to the newsletter but it uses to send the newsletters created also in DDB Journal.
The DDB Journal Editors before sending the newsletter will take that newsletter subscriptions list and it will import them into DDB Journal
under https://cms.deutsche-digitale-bibliothek.de/de/admin/people/simplenews/import
The DDB Journal Editors create a new content DDB Newsletter and will send to the subscribers, two versions of newsletters will be created,
the email version and the browser version. To create the email version it is used inline CSS and absolute URL for the images.
There are some background images used in the title that it will appear only in the Browser version but not in the email.
If a content is published in the production DDB Journal automatically it will be published in the Frontend.
If the URL in DDB Journal of the content is https://cms.deutsche-digitale-bibliothek.de/de/journal/aktuell/title-content
The URL in the Frontend is https://deutsche-digitale-bibliothek.de/content/journal/aktuell/title-content
Frontend knows if it is a DDB Journal Page if the path starts with /content, then I will get the Drupal Page and it will rewrite the relative URL from the
images, files, links to make it absolute linked to the DDB Journal URL instead of the Frontend URL.
All these functions are done in the ContentService, ContentController... in ddb-common
The Frontend is calling depending on the current language to these REST API to get the menus and to save it in the cache.
https://cms.deutsche-digitale-bibliothek.de/en/api/menu_items/main?client=DDB-NEXT&_format=json
https://cms.deutsche-digitale-bibliothek.de/en/api/menu_items/footer?client=DDB-NEXT&_format=json
https://cms.deutsche-digitale-bibliothek.de/de/api/menu_items/main?client=DDB-NEXT&_format=json
https://cms.deutsche-digitale-bibliothek.de/de/api/menu_items/footer?client=DDB-NEXT&_format=json