Services
What we bring together
One shared foundation for content, brand and engineering.
Strategy
Align goals, audiences and content around one direction.
Brand and identity
A durable language and visual attitude for digital touchpoints.
Interface design
Clear, accessible interfaces with a distinctive rhythm.
Engineering
Fast, resilient websites that can be delivered statically.
Content systems
Editorial models teams can use confidently every day.
Quality and accessibility
Accessibility, performance and resilience as one shared standard.
Editorial text
A text block with a real editorial purpose
This block tests longer paragraphs, deliberate spacing and the typography shared by Payload and Astro.
It remains semantic content: the local Starwind adapter owns presentation instead of exposing arbitrary layout controls in the CMS.
Image and context
Media explains a decision, not only a mood
Image, heading and body copy form one statement. The block stays responsive without asking editors to manage breakpoints.
Measurable quality goals
- 90+
- Lighthouse targetAcross performance, accessibility, best practices and SEO.
- AA
- WCAG 2.2As the binding quality framework.
- 2
- LanguagesIndependent published DE/EN snapshots.
- 0
- Silent fallbacksIncomplete content should fail visibly.
More structured block types
The section break structures the lab without mixing content and presentation.
Process with multiple stages
A complete path from the first conversation to maintenance.
- 1
Listen
Collect questions and context.
- 2
Focus
Choose a durable direction.
- 3
Build
Bring content and interface together.
- 4
Learn
Launch, observe and improve.
Questions about the studio
How does a project begin?
We start with a structured conversation about goals, audiences, content and the right next step.
Do you work with existing teams?
Yes. We complement internal skills and make decisions transparent enough to carry forward together.
Why static delivery?
Static websites reduce moving parts in public operation and provide a strong basis for speed and resilience.
How does a site stay maintainable?
A bounded content model, clear editorial rules and documented handovers keep daily work understandable.
How is accessibility considered?
Accessibility informs content structure, contrast, keyboard access and testing from the first phase onward.
Can content be published in two languages?
Yes. German and English are maintained as independent published locale snapshots without a silent fallback.
Working material
Existing tenant media shown in a range of views.
A question is a good beginning.
We sort goals, content and possibilities in a first conversation.
All twelve references
A complete manual selection for the renderer test.
01 / Project
Signal Atlas
A digital orientation system for an organisation with many voices.
02 / Project
Field Notes
An editorial platform turning research into accessible stories.
03 / Project
Common Ground
A collaboration platform where different perspectives can stand side by side.
04 / Project
North Star
A strategic website for teams choosing one direction from many possibilities.
05 / Project
Open Studio
A digital look into working methods that usually stay visible only in conversation.
06 / Project
Quiet Commerce
A focused product world for decisions without artificial urgency.
Insights
All twelve insights
Content Is Infrastructure
Why good content is not produced at the end of a project but forms its foundation.
Designing for Maintenance
A good interface helps the editorial team as well as its visitors.
Designing for MaintenanceThe Value of Restraint
Why less interaction often creates more orientation.
The Value of RestraintFrom Workshop to System
How conversations become durable decisions for a digital product.
From Workshop to SystemAccessibility Is Quality
Accessibility is not a final check but a measure of good design.
Accessibility Is Quality
Static by Default
What static delivery means for resilience, speed and responsibility.
Static by DefaultThree perspectives
Cards with image, text and an internal destination.
Contact without invented data
This reference deliberately uses neutral placeholders only.
hello@example.invalid
Availability
Conversations by prior arrangement
Location
Remote and location-independent
Cray Studio
Example partner fields
Four roles, one way of working
Fictional role profiles instead of real personal data.
Direction
Strategy
Connects goals, questions and priorities.
Language
Content design
Makes content clear, accessible and consistent.
Form
Interface design
Develops systems with rhythm and orientation.
Workshop
Engineering
Takes care of resilient technical delivery.
"A good system takes complexity seriously without passing it on."