← Back to Work

Charlie Cobbinah - Academic Website

How we designed and built a personal academic website that gives Charlie Cobbinah a clear home for his research, publications, speaking work, writing, and CV, while keeping editing simple after handoff.

Charlie Cobbinah presenting at an academic event
Academic Website

Charlie Cobbinah is a doctoral researcher whose work sits across decolonial discourse, African higher education, and sustainable African futures. The site needed to do more than introduce him. It had to hold research, publications, speaking engagements, essays, contact details, and a CV in one place without feeling crowded.

The job was not just to make the site look calm. It was to give very different kinds of academic material a shared structure and a publishing flow Charlie could keep using on his own.

11Page templates
6Publication entries
~60sEdit to live

The brief

The brief was clear from the start: build a personal academic website for Charlie’s doctoral research, publications, speaking, writing, about page, CV, and contact. The site had to feel serious enough for academic work, but simple enough for a visitor who might arrive from LinkedIn, search, or a direct recommendation and need to understand the work quickly.

Charlie pointed us to codykommers.com as a reference. That helped settle the visual direction early. The site did not need decoration or a personal-brand performance. It needed to trust the writing, stay readable for long stretches, and make the research feel properly held.

What the site needed to hold

This was not one content type repeated across a few pages. Each section had a different job, and the site only worked if those differences stayed clear.

Research

A place for the doctoral work itself

The research page needed a central question, affiliations, methodology, themes, and intellectual influences without collapsing into a wall of institutional text.

Publishing

Different outputs, handled properly

Publications, speaking, and writing each needed their own logic, from grouped publication types to event listings and an archive for essays and commentary.

Handoff

A system Charlie could keep using

The site had to be editable after launch, which meant structuring the content and CMS around real use rather than around what looked good in a demo.

The research page needed a clear framing of Charlie’s doctoral question, institutional affiliations, methodology, themes, and influences. The publications page needed grouping by type and link logic that respected academic status, so pieces in preparation or under review could be listed without pretending to be publicly available.

The speaking page needed a chronological archive with enough context for each event to stand on its own. The writing section needed both an index and a post template. Around those sat the quieter support pages such as About, Contact, Privacy, Terms, and the 404 page. Altogether, the project ended up with eleven distinct page templates.

We also populated the core material from Charlie’s CV and project notes, which meant correcting assumptions as we went. One early fix was removing an incorrect University of Cape Town reference and replacing it with the real University of Ghana fieldwork context and Charlie’s collaboration with Dr Delali Amuzu.

The direction we chose

Visually, the site was built to feel editorial rather than promotional. We used a warm off-white background, dark ink, one gold accent, serif-led typography, and a persistent two-column reading layout on the main content pages. The homepage carries a full-bleed image of Charlie presenting, which grounds the site in a real academic setting instead of generic professional polish.

The design work was less about adding personality and more about removing noise. The point was to give the writing, the research question, and the publication record enough room to speak without the site becoming plain or lifeless.

How we structured the build

We built every page first as a standalone HTML prototype before moving anything into Astro. That helped settle layout, hierarchy, and page rhythm early. Once the direction was approved, we translated the prototypes into a content-driven site with a lighter stack underneath.

About and Research were treated as single documents, while publications, speaking, and writing were modeled as repeatable content types. That gave Charlie a cleaner editing experience and kept the site structure aligned with the way the content actually behaves.

Under the surface, the site runs on Astro, Tina CMS, GitHub, and Cloudflare Pages, which keeps it fast and simple to maintain. The deeper build notes, delivery fixes, and technical lessons are better told in the separate project note rather than inside the case study itself.

Supporting note

The case study stays with the project. The build note covers the technical and editorial lessons behind it.

Handoff and next steps

By handoff, the site was live on charliecobbinah.com, the core content had been populated from Charlie’s CV, and he could manage routine updates himself without depending on us. Google Search Console and Umami analytics were also set up so visibility and site usage could be tracked more clearly after launch.

The remaining work was deliberately smaller than the structure beneath it. The main follow-up items were a portrait photo, Charlie’s personal narrative for the About page, and replacing homepage placeholders as more writing is published.

Share this case study