viertelweise is designed for city apartment agencies and urban holiday stays. Berlin, Hamburg and Düsseldorf with six apartments and three houses are fictional sample data, not product limits.
All designs offer the same functionality: accommodation search with filters and favourites, houses, offers, fixed available stays, a map, alternative dates, availability calendars, category ratings, and booking and enquiry flows with guest details, extras, drafts and a payment summary. The preview uses sample data only.
The preview has no production CMS or data connection. Bookings, enquiries, payments and reviews are not submitted. The map loads external data only after a click. Binding prices, availability and bookings require project-specific integration with Web-Modul Core and your CMS.
Properties and offers use local sample data. Binding prices, availability and bookings will be connected through Web-Modul Core. After an explicit click, the map loads external vector tiles from OpenFreeMap; the style and markers belong to the template. No local OpenStreetMap database is stored. CMS adapters for October CMS, Joomla and TYPO3 require separate implementation.
Yes. viertelweise combines locally hosted Poppins typography, lime and graphite with city photography, split desktop views and subtly tinted liquid glass. Colours and glass tokens are maintained centrally. CSS blur remains available as a fallback; additional edge refraction is enabled in supported Chromium browsers. Booking components remain shared across all designs.
Küstenzeit, Schlüsselkomplizen, Fernwerk and viertelweise differ in design and tone, not functionality. There are no feature packages based on template size. Pricing depends on the implementation effort for your project.
The local viertelweise demo includes an accessibility information page as a customer template and settings for text size, stronger contrast and reduced motion. OpenDyslexic is locally included as an optional reading font. A documented sample audit does not replace a full conformance assessment. Operator details, real content, contact channels and production booking and payment services must be completed and assessed before publication.
A shared consent manager provides essential storage and separate options for Matomo and Google Analytics. Optional services are off by default, and preferences can be changed at any time in the footer. The demo stores the decision only for the current browser-tab session and loads no tracking services even after consent. Production integration and the corresponding privacy information must be implemented for each project.