Choosing the base template
First of all, this template has multiple parameters
allowing you to adapt it to
||If this parameter is present, the template will include a sidebar
Allows you to define which tab is active.
nav1 sets the top level (portal, shop, verlag) and nav2 the second level
For the possible values of the parameters please take a look at the data-pons-tab attributes
in the html code.
We don't know all the items here, so we may display placeholders for the second level (
applies to shop).
||If this parameter is present, the template should be free of ads
Allows you to define where and how the search form appears (currently only applicable when sidebar is present).
By default, the search form appears as a widget.
If this parameter is top, the search form should appear on the top, over the main content.
If this parameter is shop, the search form is prepared for usage in the shop.
||If this parameter is present, the template will (responsively) support mobile devices
||If this parameter is present, the template will be using the whole page
||If this parameter is present, the template will have the szm/ivw tag available (tracking)
Tabs and footer
We've observed that most template changes are needed because of changes that only affect the tabs or footer.
So we've added the possibility to download the tabs
- tabs supports the nav2 parameter (as described above)
- tabs should correspond to the template-element NAV (see below)
- footer should correspond to the template-element FOOTER (see below)
We propose that you separate the NAV / FOOTER elements into separate partials (html snippets) so you are able
to update these individually.
Adapting this template to your application
If you take a look at the html source, you can see that we've insert comments around certain
areas in the template, which look like this:
<-- <template-element data-section="[name]"> -->
<-- </template-element> /[name] -->
This allows you to do replace these lines with this regular expression:
[matched group 1]
This should convert the commented lines to 'real' tags and you can now feed the template
to any html/xml processor and should have easy access to the sections surrounded by
Of course you can also choose to not go this route and adapt the template based on regular
expressions (or do both processing steps).
To make your life easier, we provide a helper ruby gem that handles both processing
Please ask us for github access and further instructions.
Available sections in the template
Important sections - you should handle those:
||Around stylesheet tags in <head>
||Around minimized assets
||Around the link to register
||(TODO) Around a link to the order page on the shop - should only be displayed...
||Around the (second-level) navigation
||Around the content - includes MAIN_CONTENT and optionally SIDEBAR_CONTENT
||Around the main content
||Around the sidebar content
||Around the footer at the bottom of the page
||Around the login status of the user: Includes both LOGGED_IN and NOT_LOGGED_IN - your application should only show one of these at the same time (based on the user's login status)
||A Section that is shown to users who are logged in
||A section that is shown to users who are not logged in
||Around ad initialization code
||Around the leaderboard ad (top)
||Around the skyscraper ad (right)
||Around the medium-rectangle ad (only applies to templates with sidebar)
||Around the ad in the footer (bottom)
Sections you should consider to support:
||Around links to apps (appstores) <head>
||Around window.Infos object in <head>
||Around the link to login
||Around the link to logout
||Around the link to the profile
||Around the username
||Around the link to the terms of service
||Around the footer links within the footer
||Around the dictionary search form
||Around the locale selector (uses the links provided in LOCALE_LINKS)
||Around the actual locale links (triggered by LOCALE_SELECT)
||Around the "alternate hreflang" links (for seo)
Sections for "nice-to-have" or cosmetic features:
||Around meta tags in <head>
||Around icon tags in <head>
||Around the status of unread messages
||Around the count of unread messages
||Around the copyright notice at the bottom of the page
||Around the year in the copyright header
||Tracking - may appear multiple times
||Around original assets - the purpose here is to hint at the used libraries (which are minimized in the corresponding MINIMIZED_ASSETS section)
||Around instructions (for developers)
Thank you for reading.