01 · Architecture
What the site is for, who it is for, and the routes that actually matter.
Capability · 03
Web Design
We design websites as editorial objects, not as a stack of sections. Information architecture, pacing, design systems, the difference between a page that performs and a page that is merely large.
How we hold it
Pages that know when to be quiet.
Art direction for the screen. We design in systems so the fifth page does not invent a new language, then we make the first artefacts feel inevitable. Type, image, motion, the scroll — treated as craft, not decoration on a template.
If the design cannot be built well, we will say so before it leaves Figma. Engineering sits in the same conversation from the first layout.
What you leave with
The work, not a slide about the work.
02 · Art direction
Pacing, type, image and the moments that should not look like a section library.
03 · System
Components honest enough for a CMS, considered enough for a homepage.
04 · Prototype
Clickable, paced, ready for development — not a deck of pictures of a website.
Built by the same studio
We do not hand a design over a wall. Dark Spark develops what Dark Spark designed. If you already have an engineering team, we will work in their stack and stay as art direction through launch.
In the work
Where this discipline showed up.
Browse