Common Ground

The words. The structure. The parts you see—and the parts you only notice when they stop working.

Common Ground is a self-directed website concept I worked on end to end, bringing together backend development, frontend implementation, visual design and copy.

The aim was to treat the website as one connected experience, rather than a design handed to development with the words squeezed in afterwards.

The challenge: make the whole thing work together

A website can look polished and still leave visitors wondering what it does.

It can also function perfectly while making every page feel like paperwork.

For Common Ground, I wanted to connect the moving parts: what the site said, how it organised information, how it looked and how it worked.

The challenge was coherence. Each layer needed to support the same experience.

What I made

Website concept · Backend and frontend development · Visual design · Website copy

This was a concept project, giving me room to work across the full build rather than contribute to a single stage.

My approach: build the experience, not just the screens

Start with what the website needed to say

I developed the copy alongside the structure and design.

That meant considering the message, headings and next steps as part of the experience—not leaving a collection of empty boxes for “content to follow”.

The words needed to explain the site’s purpose. The layout needed to help people find them.

Neither could rescue the other by working overtime.

Give the content a structure

I worked on how information was organised across the site, considering what belonged together and what visitors would need to understand first.

The aim was to give each page a role and each section a reason to exist.

A website is allowed to have several pages. It shouldn’t feel like several unrelated conversations.

Shape the visual design

I developed the visual presentation around the content and its hierarchy.

The design work focused on bringing the pages into a consistent whole, balancing character with clear communication.

The question wasn’t simply, “Does this look good?” It was, “Does this help the page do its job?”

Connect frontend and backend

I worked on both the visible interface and the underlying implementation.

That connected the presentation with the structure supporting it, allowing me to consider how design decisions translated into a functioning website.

The frontend introduced the experience. The backend had to hold up its end of the conversation.

Refine across disciplines

Working across design, development and copy meant I could revisit decisions across the build.

If a section needed too much explanation, the answer might be better wording—or a clearer structure. If the content didn’t sit comfortably in the layout, the layout could change.

The first decision didn’t automatically get the last word.

My contribution

I worked across:

• Backend development and site implementation.
• Frontend development.
• Visual design and page layouts.
• Content organisation.
• Website copy.

Common Ground brought these responsibilities into one project, giving me a practical way to explore how editorial and technical decisions affect each other.

What this project demonstrates

This project demonstrates my approach to a website as a connected communication system.

The copy establishes meaning. The design creates hierarchy. The frontend presents the experience. The backend supports its operation.

As a concept project, Common Ground does not carry claims about client results, traffic, conversions or measured usability improvements. Its value lies in the end-to-end work and the decisions connecting those layers.

The takeaway

I didn’t stop at how the website looked.

I worked on what it said, how it was built and how the pieces came together.

Because a good-looking frontend shouldn’t be doing all the heavy lifting.