Expressive websites often become fragile. We use a small set of editorial rules to keep personality and maintainability together.
h2
Notes from Morrow Works on design, publishing and studio practice.
Start with recurring decisions
The useful question is not which homepage looks most exciting in a presentation. It is what the studio will publish repeatedly: projects, notes, announcements, services or experiments. Those recurring decisions should shape the content model and templates before decorative interactions are added.
Give content a reliable minimum
Every project should work with a title, short description, category and one strong image. Richer projects can add galleries, credits and process writing, but the site should not collapse when a smaller piece of work has less material. A dependable minimum makes publishing easier and reduces abandoned drafts.
Use exceptions deliberately
Custom layouts are valuable when they reveal something specific about a project. They become expensive when every entry needs a unique solution. We design a strong default, a small number of meaningful variations and clear rules for when each should be used.
Treat the admin experience as part of the design
A polished front end can still fail if updating it requires remembering hidden conventions. Labels, preview states, image guidance and sensible fallbacks determine whether the site remains alive after launch. The publishing experience deserves the same attention as the public interface.
A working checklist
- Model repeated content first
- Design a useful minimum entry
- Limit layout options to meaningful differences
- Test publishing with someone outside the design team
The best studio website is not the one with the most layouts. It is the one the studio keeps using.
Join the conversation.