01 / THE STARTING POINT
Start with the work.
A website has a job to do. It may help a listener find an interview, give an artist a clear submission process, or bring a creator’s videos and community into one place. I start with those people and tasks, then connect the design, content, and engineering around them.
My work spans public websites and the tools behind them: responsive interfaces, databases, APIs, publishing workflows, and administration. The aim is a site you can use and maintain, with a clear path from the first visit to the next useful action.
Who this can help: Creators, broadcasters, independent organizations, and teams who need a useful public website or a connected application.
02 / SCOPE & DELIVERABLES
What we can work on.
Every engagement is scoped around the current situation. Depending on that scope, the work can include:
- A clear map of audiences, content, page structure, and the actions the site needs to support.
- Responsive pages and interaction patterns that work across desktop and mobile screens.
- Application workflows, data connections, APIs, and administration shaped around actual operating needs.
- Publication and access rules, validation checks, and a practical handoff for ongoing updates.
03 / THE PROCESS
Make the path clear.
Understand the work
We identify the people using the site, the information they need, and the parts of the current workflow that cause friction.
Design the path
We shape the content, navigation, and key interactions before committing to implementation details.
Build and verify
The interface and connected systems are developed together, with checks of public pages and the workflows behind them.
Prepare for everyday use
We work through how content is updated, how access is managed, and what needs to be understood after launch.
04 / PUBLISHED EXAMPLES
See the work in context.
Chart identity, public music discovery, and participant workflows in a connected platform.
A creator website that connects video, collection stories, partners, and community contributions.
A public archive that keeps interviews, station people, and stories accessible.
05 / COMMON QUESTIONS
A little more context.
Can you work with an existing website?
Yes. The first step is to understand the current code, content, and publishing process so that useful work can be preserved and the changes can be scoped sensibly.
Does every project need a custom application?
No. The right scope follows the job the website needs to do. A focused content site and a tool with accounts, data, or integrations have different needs.
EXPLORE THE PRACTICE