Recognize
Show Designers and Providers that the Registry understands the work behind their work.
Company system / Design
Design
Brand governs expression. Product governs the application. Website governs how the public story, proof and acquisition experience bring both systems together.
Public experience standard
A website that feels like the work:
considered, connected and clear.
The public website should feel editorial and human before it feels technological. It introduces a better way to operate, shows the platform as credible evidence and gives Designers and Providers a clear path into the Registry.
The website’s job
Turn recognition into trust—and trust into a qualified next step.
Reframe
Present fragmented operations as a solvable system, without making software the hero.
Prove
Use current workflows, participant evidence and specific outcomes to earn each claim.
Convert
Move the right participant into the right Application with clear expectations and no pressure theatre.
02
Information architecture
Organize by audience and job—not by company department.
Every route should answer who it serves, what becomes easier, what proof exists and what the visitor should do next. Product depth lives beneath audience clarity.
Make the Designer-first promise immediately understandable
Explore the platform · Apply freeShow how the Registry returns time and protects independence
Apply as a DesignerExplain category-specific workflow value and real Project context
Apply as a ProviderConnect Projects, people and commercial work without tech-company theatre
Explore workflowsExplain qualification, matchmaking and connected delivery
See how the network worksFrame the company through the problem it exists to solve
Read our point of viewPublish useful operating guidance and proof
Read field notesRoute each participant into the correct Application and pending account
Start an ApplicationAudience journeys
One company story. Four different reasons to care.
The public website must preserve the Designer-first position while giving every participant a credible, useful entry point. A visitor should never have to translate a generic platform pitch into their own work.
I am carrying too much operational work
See a calmer, connected way to run the Studio
Designer workflow · Project proof · independenceApply as a DesignerI need better briefs, approvals and payment visibility
See a portal shaped around my category of work
Category workflow · work order · delivery evidenceApply as a ProviderI want confidence without managing every handoff
Understand how the Designer remains the lead while work stays coordinated
Project visibility · decisions · schedule · communicationEnter through an invited ProjectI want to understand the company and its standard
See the mission, operating principles and evidence of care
Company point of view · Brand · current openingsExplore the company03
Homepage architecture
The opening chapter of the Registry—not a software catalogue.
The homepage answers one question: why does The Design Registry exist? The idea comes first, the work gives it emotional weight and the product appears only after the visitor understands what deserves to be preserved.
Every professionally designed project
deserves a Registry.
Designers create remarkable work. We believe every decision, every specification, every product and every milestone deserves one permanent place. That's The Design Registry.
Apply as a Designer
Beautiful work is often forgotten.
01Drawings02Emails03Folders04Photos05Specifications06Invoices07Memory
Everything scattered. Nothing remembers the whole story.
THE REGISTRY
Every Registry tells a story.
Projects begin with an idea. They grow through thousands of decisions. The Registry quietly preserves every one of them.
The thinking, choosing and making behind every finished space.
Designers
Create. Coordinate. Build the Registry.
Providers
Contribute craftsmanship. Build the Registry.
Clients
Experience. Approve. Follow progress. Own the Registry.
Projects finish.
The Registry doesn't.
The Registry becomes the permanent record of everything that made the project possible.
Beautiful work deserves
a beautiful record.
04
Page templates
Reusable story structures keep the site coherent.
Templates standardize narrative order, proof and conversion without forcing identical pages. Each page still earns its hierarchy from the visitor’s task.
Audience landing
Promise → professional reality → workflow proof → trust → application
Platform story
Job to be done → product capture → connected records → role-aware value → CTA
Workflow detail
Operational problem → canonical flow → participant views → evidence → related specification
Editorial article
Observation → useful argument → field evidence → practical guidance → related product
Application
Expectation → eligibility → progressive form → review → pending account
Trust page
Standard → qualification → privacy → commercial clarity → accountable owner
05
Website component system
Build once. Compose with editorial judgment.
Website components consume Brand tokens and Product interaction contracts. Their layouts are expressive; their content, accessibility and states remain governed.
Navigation
Announcement bar · primary header · audience menus · mobile menu · persistent Apply action
Editorial hero
Eyebrow · outcome-led headline · controlled italic accent · concise proof · one primary action
Audience card
Named participant · specific job · useful promise · evidence · destination
Platform frame
Approved Demo Workspace capture · feature-state label · caption · provenance · alt text
Workflow sequence
Numbered steps · owners · inputs · outputs · exception path · related product link
Proof block
Metric or observed result · source · date · owner · scope · qualification
Testimonial
Attributed person and Studio · approved quotation · role · optional portrait · no invented copy
Application CTA
Audience-specific expectation · free/core promise · review standard · clear next step
Form system
Visible labels · canonical shared fields · progressive sections · draft · validation · privacy context
FAQ
Real objection · direct answer · owner · last reviewed · related policy or workflow
Editorial card
Category · useful title · summary · evidence type · date · reading time
Global footer
Audience routes · company · resources · legal · platform sign-in · provenance
Section anatomy
Every section must earn its place in the argument.
Start with the visitor’s unresolved question. Choose the smallest section pattern that can answer it, support the answer with proof and point toward the next useful decision.
EyebrowNames the category or context; never carries the main promise.
HeadlineOne outcome-led idea. Maximum two clauses and one controlled italic accent.
Supporting copyExplains the professional reality in 35–65 words without feature dumping.
ProofCurrent interface, observed fact, attributed story or governed network standard.
Primary actionOne audience-specific next step written as a verb and expected outcome.
Secondary pathUseful exploration only; visually quieter and never equal to the primary action.
Content model
Structured content keeps the site accurate and AI-maintainable.
Every reusable content type has canonical fields, ownership and review dates. AI may draft and adapt; it may not invent evidence, release state, testimonials or policy.
Title · route · audience · job · promise · primary CTA · status · owner · review date
Canonical feature · release state · participant · workflow · image · caption · source
Name · professional job · workflow · qualification · service area · Application route
Subject · role · approved quote · evidence · consent · attribution · publish/expiry dates
Category · author · summary · body · related workflow · related CTA · reviewed date
Audience · objection · direct answer · owner · policy/source · reviewed date
Platform imagery
The interface is evidence—not wallpaper.
Use approved Demo Workspace captures at a readable size. Show one task, preserve enough context to identify the workflow and visibly label concept or planned features.
Open Platform Image Use and social examples →Designer Project Overview · Demo Workspace · August 2026
06
Forms and conversion
The Application should feel selective, useful and respectful.
Conversion does not mean pressure. Explain who the Registry is for, what information is needed, how review works and when the applicant will hear back.
Choose participant typeDesigner or one of nine Provider Categories
Confirm fitEligibility, location, standards and expectations
Complete progressive ApplicationShared core fields plus category-specific information
Create pending accountSave, return and verify identity
Review and decisionTransparent state and editable notifications
Provision WorkspaceApproved Entity, owner invitation and next-step onboarding
Responsive, accessible and fast
The mobile site is the same promise with a different composition.
Do not collapse desktop sections into tiny cards. Reorder around the visitor’s next decision, keep proof readable and preserve one clear action.
Single-column narrative · sticky Apply action only when helpful · no horizontal UI screenshots
Editorial rhythm with two-column proof · touch-first navigation · forms remain progressive
Generous scale · controlled asymmetry · readable product frames · deliberate whitespace
Semantic headings · keyboard navigation · visible focus · AA contrast · captions and alt text
Responsive images · reserved dimensions · limited scripts · measured Core Web Vitals
Unique metadata · canonical URLs · structured data · approved social preview · useful excerpt
Search, metadata and discovery
Every page should be understandable before it is visited.
Search results and shared links are part of the website experience. Titles and previews should communicate audience, outcome and source truth without clickbait.
Unique, specific and normally under 60 characters.
Useful excerpt; not a repeated tagline.
1200 × 630, high contrast, minimal text and correct capability state.
No markup for content that is not visible on the page.
Use descriptive link text and preserve a clear return path.
Canonical route and sitemap state owned at release.
Measurement framework
Measure qualified momentum, not vanity traffic.
Analytics should explain whether the right people recognize themselves, trust the model and enter the correct Application. Consent, privacy and data minimization apply to every event.
Acquisition
Qualified sessions by audience and sourceUnderstand who is arriving—not merely how many.
Recognition
Audience-page depth and proof engagementConfirm visitors recognize the problem and explore the model.
Intent
Application starts by participant typeMeasure meaningful next steps separately from generic clicks.
Completion
Application completion and qualified submission rateFind friction without weakening qualification.
Quality
Approval rate and activation after approvalOptimize for useful network growth rather than raw volume.
Trust
Return visits, direct traffic and referred ApplicationsTrack whether reputation compounds through the network.
08
Release governance
A public page is a product promise.
Marketing, Product and Operations should review every major page together. The site may simplify complexity; it may not invent capability, hide conditions or drift from canonical language.
Definition of ready
- Page brief names audience, job, owner, primary action and evidence.
- Copy and canonical terminology are reviewed against Brand and Glossary.
- Every feature claim matches the current Product record and release state.
- Desktop, tablet, mobile, keyboard and screen-reader paths are verified.
- Metadata, social preview, analytics events and consent behavior are complete.
- Forms create or update the intended record and confirmation path.
- Links, empty states, failures and unpublished content have been tested.
- Owner and next review date are recorded before release.