Back to help overview
Help center
Pages & display options
How frontend content is structured, exposed and kept useful for navigation and SEO.
At a glance
Page types, navigation, widgets and SEO notes for the frontend.
Current status
Frontend pages, navigation and content structure
- The help now mirrors the current mix of home, landing, shop and service pages.
- Menu and visibility notes were aligned with the active header/footer structure.
- SEO and maintenance guidance now reflects today’s content building blocks.
- Footer pages can be placed separately in the main footer menu or in the lower legal bar.
- Page content can now be maintained in the backend with rich text fields and Media Center images, giving editors more freedom in how sections are composed.
- New: The admin theme module keeps frontend design changes strictly separated from backend layout handling.
- An HTML theme import with follow-up slot mapping is now available for controlled frontend layout onboarding.
- New: System-wide interaction and pageview analytics capture visitors, sessions, IP-based usage profiles, referrers, devices, browsers, operating systems and countries (including GeoLite2 lookup when available) for analysis, conversion evaluation and diagnostics across frontend and backend.
- Top interactions can now be drilled down in the admin to account/attempt identifier, IP, country, browser, route, path and payload; login successes and failures are recorded as dedicated events.
Structure
Page types at a glance
- Landing pages for campaigns and focused entry points.
- Category and product pages with dynamic shop data.
- Static pages such as imprint, privacy or terms.
- Special pages for help, contact or service content.
- Cart grid sections for flexible card layouts with columns, image and text.
Navigation
Menus and visibility
- Create and publish pages in the backend.
- Define the position inside the main menu, main footer menu or lower legal bar.
- Control visibility cleanly for the relevant area.
- Keep slug, title and meta data consistent.
Legal shop pages such as terms, cancellation policy, payment methods, shipping policy and battery law notices usually belong in the lower legal bar.
Menus are built dynamically in the frontend. Changes become visible immediately after saving; the page editor creates a revision automatically.
Layout
Widgets, blocks and visual hierarchy
- Use reusable content blocks for repeated content.
- Place sliders and teasers intentionally on home and landing pages.
- Work with a clear order: hero, content, CTA.
- Test on mobile and desktop so spacing and order stay clean.
Frontend design
Imported themes and local resources
- Imported HTML, live and WordPress themes affect frontend presentation only; backend design remains unchanged.
- Header, main content and footer are detected automatically. If an area is missing, project navigation and the project footer remain authoritative.
- Stylesheets, scripts, images and fonts are delivered locally through the protected theme asset route. External CSS imports and webfonts are mirrored automatically during import.
- Technical WordPress customizer, editor and admin files are not included in the shop frontend.
Quality
SEO and technical notes
- Maintain unique titles and meta descriptions.
- Avoid duplicate slugs and duplicate content.
- For Page Builder images, maintain descriptive filenames and alt texts in the Media Center.
- Internal linking improves orientation and discoverability.
- Review larger changes in preview and live mode.