[BEGIN]
fyi: For [BEGIN] the format Heading 1A formatted text can be entered here. Within a text bolded texts can be inserted, also a text passage italic or underlined can be displayed. If a text is to be particularly emphasised, it can be bolded and italicised or even bolded and italicised and underlined For better readability, Links can be hidden behind text.
Individual lines or sections can be indented to further structure the text.
here are a few more indented lines of text.
This is the last indented line.
There are checklists....
fyi: For [There are checklists], the format Heading 2 was chosen- first entry in the checklist
- second entry in the checklist
- middle entry in the checklist
- fourth entry in the checklist with a total of five items
- last entry in the checklist
and enumerations
fyi: For [and bulleted lists] the format Heading 2 was chosen- first entry
- another slightly longer entry
- middle entry bolded and italicised for emphasis
- fourth entry
- last entry with rather long text, so the text may break. Does the presentation nevertheless remain neat?
[END]
.Good to know
Categories
Recovery
Wellness
Wellness and Health
Fit and Active
Romance
Gourmand
Advent / Christmas
Family
Culture
Hiking
Active
Nature
Winter
Hike Farm
Spring
Motorbike
Summer
Riding
Biking
Family and Children
Cities and Culture
Beer and Culinary
Fishing
Bike
Family Holiday
Culture and Delight
City Tours
Autumn
Special Offer
Culinary and more
Cross-Country Skiing
Ski-Alpin
Active-Winter
Specials
Payment Options
Directions & Parking facilities
Number of parking spaces | 20 |
---|---|
Handicapped parking spaces | 6 |
Bus parking spaces | 5 |
[BEGINNING]
This is a slightly longer description.
This is a wonderful way to check later in the frontend whether the display is also complete for longer texts and whether the layout is correct.
The structure of the description text is simple:
It starts with the data.destination.one field description
in square brackets.
The actual description text is then inserted between [BEGIN] and [END].
This makes it possible to see at first glance whether the text is complete.
[Start paragraph formatting with
]
This paragraph starts on a new line and ends with an empty line.
[End paragraph formatting with
[Start paragraph formatting with >br>]
Here, the paragraph formatted in this way begins with a blank line and also ends with a blank line.
[End paragraph formatting with ]
[Start paragraph formatting with line break manual]
This paragraph begins on a new line. Three manual line breaks, i.e. empty lines, now follow here.
This sentence is then also on a new line.
[End paragraph formatting with manual line break]
Here we are already at the last sentence. After this sentence, no more than the end mentioned above may be displayed.
[END]
Social Media
Price info
[BEGINNING]
This is a somewhat longer description.
This can be used later in the frontend to check whether the display is also complete for longer texts and the layout is correct.
The structure of the description text is simple:
The start is made by the data.destination.one field name
in square brackets.
The actual description text is then inserted between [BEGINNING] and [END].
This makes it possible to see at first glance whether the text is also complete.
[Start paragraph formatting with <p>]
This paragraph starts on a new line and ends with a blank line.
[End paragraph formatting with </p>]
[Start paragraph formatting with >br>]
Here the paragraph formatted in this way starts with a blank line and also ends with a blank line.
[End paragraph formatting with </br>]
[Start paragraph formatting with manual line break]
This paragraph starts on a new line. Three manual line breaks, i.e. empty lines, now follow.
This sentence is then also on a new line.
[End paragraph formatting with manual line break]
Here we are already at the last sentence. After this sentence, no more than the above-mentioned end may be displayed.
[END]
Persons
Services
[BEGINNING]
This is a somewhat longer description.
This is a great way to check later in the frontend whether the display is also complete for longer texts and the layout is correct.
The structure of the description text is simple:
The start is made by the data.destination.one field name
in square brackets.
The actual description text is then inserted between [BEGINNING] and [END].
This makes it possible to see at first glance whether the text is also complete.
[Start paragraph formatting with <p>]
This paragraph starts on a new line and ends with a blank line.
[End paragraph formatting with </p>]
[Start paragraph formatting with >br>]
Here the paragraph formatted in this way starts with a blank line and also ends with a blank line.
[End paragraph formatting with </br>]
[Start paragraph formatting with manual line break]
This paragraph starts on a new line. Three manual line breaks, i.e. empty lines, now follow.
This sentence is then also on a new line.
[End paragraph formatting with manual line break]
Here we are already at the last sentence. After this sentence, no more than the above-mentioned end may be displayed.
[END]
Itinerary
[BEGINNING]
This is a slightly longer description.
This is a great way to check later in the frontend whether the display is complete for longer texts and whether the layout is correct.
The structure of the description text is simple:
It starts with the data.destination.one field description
in square brackets.
The actual description text is then inserted between [BEGIN] and [END].
This makes it possible to see at first glance whether the text is complete.
[Start paragraph formatting with
]
This paragraph starts on a new line and ends with an empty line.
[End paragraph formatting with
[Start paragraph formatting with >br>]
Here, the paragraph formatted in this way begins with a blank line and also ends with a blank line.
[End paragraph formatting with ]
[Start paragraph formatting with line break manual]
This paragraph begins on a new line. Three manual line breaks, i.e. empty lines, now follow here.
This sentence is then also on a new line.
[End paragraph formatting with manual line break]
Here we are already at the last sentence. After this sentence, no more than the end mentioned above may be displayed.
[END]
Contact person
[KONTAKT:ANSPRECHPERSON:Firma] keine Mehrsprachigkeit
Author
[KONTAKT:AUTOR:Firma] keine Mehrsprachigkeit
Organization
[KONTAKT:ORGANISATION:Name] keine Mehrsprachigkeit
Dates
Thursday, the 01.05.2025
14:00 - 18:00
Friday, the 01.05.2026
14:00 - 18:00
Saturday, the 01.05.2027
14:00 - 18:00