Skip to main content

Design Language

WebHostingUI should feel simple, professional, and operationally credible.

Core principles​

  • Prefer clean geometry over decorative effects.
  • Use spacing and typography to create trust before adding motion.
  • Write like a hosting company that understands uptime, migrations, and support queues.
  • Keep surface styling restrained so teams can adapt components quickly.

Visual direction​

  • Light-first presentation with strong contrast
  • Soft blue-cyan accents rather than loud gradients
  • Rounded cards with controlled shadows
  • Dense but readable information blocks

Content direction​

Use copy that sounds specific to hosting:

  • "NVMe storage"
  • "free migration"
  • "99.99% uptime"
  • "priority chat"
  • "daily backups"
  • "named engineer"

Avoid vague marketing filler that could belong to any startup.

Code direction​

  • Favor one self-contained component per snippet
  • Keep data arrays close to the top of the file
  • Do not introduce unnecessary abstractions
  • Make shadcn adaptation obvious

Review check​

Before publishing a new component, ask:

  1. Would a hosting buyer or hosting operator immediately understand where this fits?
  2. Does the code still read clearly after copy-paste?
  3. Is the layout professional without depending on excessive decoration?