TAIWO ATLAS
taiwoatlas.dev@gmail.com +234 901 106 5513
Editorial & Author Platform

Adebayo Akindele

A complete publishing ecosystem for a nonfiction author — book microsite, chapter reader, press room, appearance archive and launch-event RSVP — rather than a single-purpose author bio page.

Adebayo Akindele cover
Role
Front-End Developer
Project Type
Author Ecosystem
Sector
Publishing
Year
2026
Status
Reference build — studied for information architecture and content strategy

Context

Adebayo Akindele's site is the online home of his nonfiction book, The Weight of Becoming — studied here as a reference case study for what a personal-brand site looks like when it has to support a real publishing cycle: a launch, a press run and an ongoing readership, not just a bio and a contact form.

The Challenge

A conventional author page is a static, single-purpose artifact: book cover, blurb, buy link. This site instead has to work as a publishing operation — a book microsite, a press room, an events calendar with RSVP capture, a recurring newsletter, and a first-chapter reader — all under one identity, launching and updating on a real calendar.

Objective

Extract the pattern for building a 'complete editorial ecosystem' — the phrase used elsewhere in this brief — rather than a single homepage, and understand how that pattern generalises to other content-heavy portfolio subjects such as journals, research platforms and community sites.

Approach

Rather than one navigation tier, the site runs two: a persistent global nav (About, Topics, Watch, Book, Appearances, Insights, Media Kit) alongside book-specific and event-specific sub-flows (a chapter reader, a launch RSVP form, a media room with press quotes). Each sub-system is scoped to its own task instead of being flattened into the main site.

Design Direction

Editorial pacing — long-form pull quotes, generous whitespace around the book's central thesis — is used deliberately to slow a visitor down before the commercial 'buy the book' moments, which appear only after the ideas have been introduced.

Technical Implementation

The RSVP and chapter-reader flows are implemented as scoped, self-contained interactions rather than a general-purpose CMS, which keeps each piece simple to reason about even as the overall site surface area grows.

HTML5 CSS3 JavaScript Chapter Reader Event RSVP Flow

Outcome

The transferable lesson for this portfolio was architectural: a subject with genuinely broad content (case studies, a journal, a growing archive) is better served by several well-scoped sub-systems than by one page trying to hold everything, which directly shaped the decision to give this site its own dedicated /journal and /work systems rather than a single flat page.

Lesson

A content-rich identity needs several small, well-scoped systems more than it needs one comprehensive page.

Related Work

Adjacent projects.