The problem
Eniola Yemi Temidayo is a change agent, a human rights activist, a business coach, a mentor, an author and an award-winning corporate manager. Every one of those is true, and listing all six is the fastest way to make a visitor believe none of them.
The audiences do not overlap either. A multinational booking a speaker, an NGO looking for a partner, and an individual looking for mentorship arrive with different questions and leave if the site answers somebody else's.
The constraint
Fragment him and he stops being credible
The obvious fix is to build six sites in a trench coat, a landing page per role, each pitched at its own audience. It routes people correctly and it destroys the thing that makes him worth booking, which is that one person does all of this.
The opposite failure is a single flat biography where every role is given equal weight and no visitor finds their own.
So the structure had to hold a through-line and a set of routes at the same time: one argument at the top that every role is evidence for, and clear paths underneath for people who already know what they came for.
What I built
- 01
Lead with the argument, not the titles
The through-line, that inclusiveness is the route to sustainable societies, and that barriers are the material change makers work with, carries the top of the page.
The six roles then read as evidence for a position rather than as a list of jobs, which is the difference between a CV and a case for hiring someone.
- 02
Roles are routes, not sections
Coaching, activism, entrepreneurship education and corporate work each open into what that engagement actually looks like and who it is for.
A visitor who arrived knowing what they needed can get there in one move; a visitor who did not gets the argument first.
- 03
Credibility lives in the specifics
Award-winning corporate manager, published author, work spanning private citizens through to government agencies. The proof is in the range and the detail, so the copy stays concrete where a personal site usually drifts into adjectives.
- 04
No CMS for a site that changes twice a year
Frontend only, content in the codebase, deploys straight to Vercel. A content system would have added a login, a schema and a subscription to maintain, in exchange for edits that happen roughly as often as a new book comes out.