What is our design process
We optimize for clarity and velocity on a static-first site: most work ships as HTML, CSS, and small JS—not a separate design “throw-over-the-wall” phase. The goal is honest narrative (what Neuro OS does, what it does not) with layouts that stay calm under long pages and dense copy.
Concept
Frame the job-to-be-done, the audience (builder vs exec vs learner), and the emotional tone. Explore with writing first, then sketches, optional Figma, or a quick branch with placeholder markup. Share early in team chat or a PR draft so engineering and marketing can react together.
- Prototype truth: mobile nav, theme toggles, and “machine” vs “human” views matter as much as hero art.
- Bring real content early—lorem breaks layout decisions that Neuro-specific copy would have caught.
- Invite dissent from Support and docs: they hear confusion first.
Implementation
Move into the repo quickly: structure in semantic HTML, tokens from landing.css (spacing, type, --pa-brand* accents), and progressive enhancement. Iterate in preview URLs; refactor CSS when patterns repeat rather than endlessly patching one-off pages.
- Prefer deleting unused markup over layering overrides.
- Accessibility is part of implementation: focus order, contrast, reduced-motion respect.
Polish
Once the skeleton is credible, tune motion, microcopy, and edge cases—empty states, long FAQ, link-heavy handbook. Dogfood on real devices and both light/dark themes when the template supports them.
- Polish is not vanity; it signals we treat AI operations seriously.
- Ship small follow-ups rather than one giant “design overhaul” branch.