Chapter 01
Challenge
01
Replace disconnected public pages with a single platform that keeps discovery, quoting, payments, tools, and account follow-through connected.
Back to archive
Internal PlatformsPlatform DesignTailwind + Framer MotionA connected product without copy-paste pages
Exhibition page
Attnom Public Platform Refresh
A public-platform rebuild focused on clearer routing, faster decision paths, and one reusable system across marketing, tools, payments, and account flows.
Connected flow
Discovery -> account
Visitors can go from a case study to a quote, payment, and project updates without losing context.
Design reuse
Shared primitives
New routes ship faster because cards, layout rules, and action states are built from one visible grammar.
Brand signal
Unified, not generic
The shared system keeps every page consistent while allowing each product to keep its own look.
design
What this case covers
Platform DesignStack focus: Tailwind + Framer MotionOutcome focus: A connected product without copy-paste pagesService: Refresh a digital productTool: Responsive systems notePublic reference build
Next step
Browse the archive to see how the same design principles adapt to very different products.
Exhibition notes
Industry: Platform Design
Related: Refresh a digital product / Responsive systems note
Outcome: The platform now looks unified because the system is explicit about tokens, layout primitives, and governance choices.
This exhibition can be used as a public reference for similar work.
Chapter 02
System
02
Rebuilt the main public pages around requests, pricing, and project-linked payments.
Introduced shared page components for the homepage, portfolio, tools, pricing, and account.
Tightened motion, loading states, and mobile behavior so the platform stays readable under real use.
Chapter 03
Interface
03
Primary capabilities: Platform Architecture, Conversion Flow, Design Systems.
Signature stack markers: Tailwind 4, Framer Motion, Custom Token Layer.
design
Annotation
Platform Architecture
Annotation
Conversion Flow
Annotation
Design Systems
Chapter 04
Outcome
04
Visitors can go from the first page to a quote, payment, and account without starting over.
Shared components now make public and internal pages faster to build.
Platform updates ship faster because navigation, cards, forms, and state patterns are reusable.
layers
Pattern system layers
The case shows how the platform stays unified without repeating the same layout everywhere.
Token layer
Color, type, and motion rules define the shared language underneath every product area.
Layout primitives
Route mastheads, cards, shells, and rails create consistent structure without identical composition everywhere.
Governance layer
Design choices stay coherent because primitives and review rules shape how new routes are added.
In short
Visible design patterns
The strongest version of this case explains the system in concrete route-level terms.
Related pages
Public, tools, exchange, account
Each route can flex while still feeling related because the core grammar is explicit.
Governance payoff
Delivery faster
Reusable components make it easier to improve related pages without losing visual consistency.
Brand trust
Consistency visible
The platform feels intentional because the rules behind it are strong enough to survive growth.
Related archive drawer
Choose the next step that fits this case.
crypto
Crypto & DeFi
Rexter Exchange: full crypto desk
A multi-chain exchange website, KYC flow, and operator console.
Open exhibitioncrypto
Crypto & DeFi
Tethrex: DeFi yield routing
Yield aggregator front end with route comparison, slippage transparency, and a real-time vault dashboard.
Open exhibitionweb
Web & Platforms
Attnom Tools: utility OS
A free, browser-native suite of file, image, OCR, and archive utilities that work entirely client-side.
Open exhibition