brand
Self-hosted Homarr users who need to evaluate the project, install it, connect services, find extensions, and reference its APIs. They move between the homepage, documentation, Workshop, API reference, and project updates as one continuous experience.
The site explains what Homarr does and gives users reliable paths to install, configure, extend, and operate it. Success means users can identify where they are, move between major surfaces without relearning the navigation, and read technical content comfortably.
Practical, technical, welcoming.
Avoid disconnected microsites, marketing-heavy copy, ornamental dashboards, hidden navigation, and dense long-form pages without visible structure.
- Keep one recognizable Homarr identity across every surface.
- Let navigation topology match the task while keeping labels and behavior consistent.
- Prioritize readable line lengths, strong heading hierarchy, and visible document structure.
- Make primary paths obvious without adding decorative UI.
- Preserve useful functionality on mobile, keyboard navigation, and reduced-motion settings.
Target WCAG 2.2 AA. Maintain keyboard access, visible focus states, sufficient contrast, semantic landmarks, touch-friendly controls, responsive layouts, and reduced-motion behavior.