Which guided research path matches my goal?

Choose a focused path, then work through its stages to make the next design or frontend decision with useful context.

Guided research paths

Each path makes its goal, audience, and intended decision clear.

SaaS landing-page references
Goal
Focused references for studying SaaS positioning, landing-page structure, pricing presentation, proof, copy, and conversion patterns.
Outcome
A defensible SaaS landing-page direction covering positioning, page structure, proof, and pricing.
Audience
Founders, product marketers, and designers preparing or revising a SaaS marketing site.
Stages
3
Expected decision
Decide how to present price, plans, and proof before implementation.
Typography and font tools
Goal
A practical starting set for finding typefaces, studying real typography and pairings, and exploring open and commercial font libraries.
Outcome
A practical typography direction with licensed candidate fonts, real-world references, pairing rationale, and implementation options.
Audience
Designers and frontend teams choosing type for a brand, marketing site, or product interface.
Stages
3
Expected decision
Select the primary and supporting families to prototype and test.
Motion starter pack
Goal
A balanced introduction to interface animation, interactive vectors, JavaScript motion, WebGL, and browser-based 3D workflows.
Outcome
A motion approach matched to the interaction goal, runtime constraints, authoring workflow, and team stack.
Audience
Designers and frontend engineers deciding how to add purposeful interface motion, vector animation, or browser 3D.
Stages
3
Expected decision
Select the implementation layer that fits the framework, performance budget, and maintenance capacity.
Open-source UI libraries
Goal
Open-source component systems and primitives for building accessible, composable, and implementation-ready web interfaces.
Outcome
A component-library strategy that balances accessibility, styling ownership, speed, animation needs, and long-term maintenance.
Audience
React product teams selecting primitives, copyable components, or higher-level UI building blocks.
Stages
3
Expected decision
Choose where expressive components add value without fragmenting the system.
Accessible colour tools
Goal
Tools for building colour systems, checking contrast, understanding visual-access needs, and evaluating interface accessibility.
Outcome
A colour system that communicates the intended brand while surviving contrast, visual-impairment, and page-level checks.
Audience
Designers and frontend teams defining or auditing interface colour systems.
Stages
3
Expected decision
Approve, revise, or reject the colour implementation based on contextual evidence.
Design systems worth studying
Goal
Public design systems that demonstrate foundations, tokens, content guidance, accessibility, component architecture, and product-specific patterns.
Outcome
A documented set of design-system decisions grounded in relevant public systems rather than copied visual conventions.
Audience
Product designers, design-system teams, and frontend leads defining foundations, components, content, and governance.
Stages
3
Expected decision
Define the accessibility, content, and governance standards required for the project.