Insights
Best practices & feedback
Ongoing insights from design reviews, user feedback and implementation. Newest first.
- Visual· design review
Namespace isolation for fonts
To prevent font conflicts between Swiss-grid (Outfit/Inter) and legacy SAR (Montserrat), we map Tailwind theme defaults dynamically via .swiss-page and .sar-page classes. This keeps classes like font-display and font-body 100% DRY.
- Visual· brand update
Fluid Art palettes and meaning
Fluid Art combines liquid backgrounds with monoline vector overlays to add an organic layer to the Swiss-grid. Always use the correct palette for each educational level (Brand for general, Bachelor for BA, AD for Associate Degree, Master for MA).
- UX· navigatie-review
Calm modular menu
Programme cards (BA/AD/MA) come first. No animated decor on menu tiles; a subtle fluid-art strip is fine. Language switch header-only — not in the overlay menu.
- Monoline· ZER asset handoff
Single monoline source
Use only `assets/monoline-icons/` → `MonoIcon` / `public/images/monoline/`. No parallel icon sets on Swiss pages. Colour via `currentColor`, not baked into the SVG.
- Copy· partnerpositionering
Introduction, not recruitment
Partner CTAs lead to contact/introduction. No Studielink, programme picker or “Become a partner” in the header. Use collaboration wording instead of DBE jargon.
- Motion· accessibility pass
Motion off by default
Cursor trail is off (`SWISS_CURSOR_TRAIL_ENABLED`). Menu animations respect `prefers-reduced-motion`. Production kinetic stays GSAP on story routes, not on overview pages.