Skip to main content

AOVIS Design System Index

This file is the local AI-readable design reference for the AOVIS storefront. It exists so coding agents and UI tools can index the active product look, feel, and support-entry rules before changing interfaces.

Reference lineage:

  • Inspired by the public VoltAgent/awesome-design-md collection
  • Aligned to the current AOVIS storefront, not a generic template

Product Identity​

  • Brand: AOVIS
  • Active sub-brand: NEXA
  • Style: premium consumer ecommerce, editorial spacing, clean white surfaces, slate neutrals, restrained teal accents
  • Do not convert the storefront into a card-wall or dashboard-style layout
  • Preserve the current product-led structure and visual hierarchy

Visual Direction​

  • Use generous whitespace and clear section separation
  • Keep product imagery prominent
  • Prefer rounded but controlled corners
  • Use subtle elevation and light borders instead of heavy panels
  • Keep the interface calm, modern, and trustworthy
  • Avoid decorative motion that does not improve comprehension

Typography​

  • Headings should stay bold, legible, and editorial
  • Body copy should remain easy to scan on mobile and desktop
  • Keep labels concise and action-oriented
  • Avoid condensed or overly stylized typography in support surfaces
  • Primary CTAs should be clear, direct, and action-based
  • Secondary actions should be visually lighter than the primary CTA
  • Support buttons should be large enough for touch interaction
  • Use accessible contrast and readable copy for all interactive elements

Support and Contact Rules​

  • The primary web support action is Chatwoot
  • Prefer the labels Chat with Us or Get Support for primary support buttons
  • If a button routes to a support hub page, label it Support Center
  • Keep support@aovis.us as a secondary fallback and small-text contact option
  • Do not make email the primary support CTA when Chatwoot is available
  • Keep privacy, DMCA, and legal mailboxes as separate, purpose-specific routes

Support UX Guardrails​

  • Support pages should lead with the fastest path to help
  • The website widget should remain the first interactive support channel
  • Help-center pages can still provide FAQ and documentation
  • Do not add extra support navigation rows or duplicate support surfaces
  • Preserve the existing storefront style while updating support entry behavior

Do​

  • Keep support entry labels short and explicit
  • Keep the contact hierarchy: Chatwoot first, support page second, email third
  • Reuse the current AOVIS palette and spacing system
  • Keep support fallback text small and understated

Don't​

  • Do not redesign the homepage
  • Do not replace the whole support system with a new information architecture
  • Do not promote email above Chatwoot when the widget is available
  • Do not introduce new card-heavy support surfaces
  • Do not change unrelated business flows while adjusting contact UI