Standard URL generation

Generation schedules allow specification of the manner in which paths are to be generated for FirstSpirit elements. The URLs the FirstSpirit contents can be accessed with later on are in turn based on these paths.

This page describes the results of a generation process in the "Default URLs" mode.

Each language and each template set is provided with a directory positioned at the top level, i.e.

../de/...

and

../de_1/...

for two presentation channels (e.g. HTML and PDF) in the language DE and

../en/...

and

../en_1/...

for two presentation channels (e.g. HTML and PDF) in the language EN.

Menu levels and page references

Within the language directories, the Site Store objects to be included are filed hierarchically. This means that every released page reference is generated including the folder path (menu levels). Menu levels without page reference are not included in the generation process as long as they do not contain any other menu levels with released page references. Their name is derived from the file name assigned to the page reference in the Site Store, and from the reference name in the case of folders. As both file names and reference names are language-independent, URLs cannot be generated in a completely multilingual fashion, e.g.

../de/startpage/mithras_home.html

and

../en/startpage/mithras_home.html

Owing to the creation of menu levels per drag and drop from the Page Store, reference and file names in the Site Store are frequently formed from the reference names of folders and pages in the Page Store.

Page groups

If page groups are used, the page references contained are filed in a folder below the respective language folder. The reference name is relied upon in the process, i.e.

../de/pagegroup/pressemitteilung_1.html
../de/pagegroup/pressemitteilung_2.html
../de/pagegroup/pressemitteilung_3.html

and

../en/pagegroup/pressemitteilung_1.html
../en/pagegroup/pressemitteilung_2.html
../en/pagegroup/pressemitteilung_3.html

Data records

If data records are output across several pages by way of a content projection ("Content" tab on menu levels), a number will be added to the file name of the page reference where the content projection is output. If one data record is output per page, this will be the ID of the data record, e.g.

../de/press/pressreleases/press_releases_details_128.html

and/or

../en/press/pressreleases/press_releases_details_128.html

If several data records are output in one page, consecutive numbers are added, e.g.

../de/press/pressreleases/pressreleases.html
../de/press/pressreleases/pressreleases_1.html
../de/press/pressreleases/pressreleases_2.html

and

../en/press/pressreleases/pressreleases.html
../en/press/pressreleases/pressreleases_1.html
../en/press/pressreleases/pressreleases_2.html

Media

If media are included in the generation process (activated option "Generate media in generation directory" in the generation schedule) they will also be filed in a directory of their own at the top level:

../media/...

The Media Store media to be included will be filed in this directory hierarchically. Media folders will also be included in the directory structure, e.g.

../media/products/powerinverter/control-panel.jpg

The file name is used for media and the reference name for media folders. Images are furthermore filed in the used resolutions, with the name of the resolution appended to the file name of the image, e.g.

../media/products/powerinverter/control-panel_Produktteaser.jpg

Language-dependent media will be filed in separate language directories, e.g.

../media/de/products/downloaddokumente/produktuebersicht.doc

and

../media/en/products/downloaddokumente/produktuebersicht.doc

Inside these language directories, the structure of the Media Store is included again, i.e. the folder structure down to the media in question is also being mapped.

The file names and reference names are also language-independent in the Media Store so that URLs cannot be generated in a completely multilingual fashion.