There is no universal formula for a great personal website.
A writer, a designer, and an independent developer might all need an online presence, but their core goals, the content they need to showcase, and what their visitors hope to find are completely different. Apply the same template to all three, and you'll end up with something that feels adequate for everyone but compelling for no one.
This article breaks down the structural challenges each group faces most often, and offers practical advice on how to build a personal site that actually serves your specific goals.
Whether you're trying to attract readers, land clients, or grow a side project, the structure of your site should be a deliberate choice—not an afterthought.
And if you're looking for a head start, Otimififi's personal website templates are organized by profession so you don't have to force-fit a generic layout onto a specific purpose.
The Writer's Personal Website
What It Needs to Accomplish
A writer's website has a distinct and multifaceted job:
- Communicate what topics and perspectives you cover
- Surface your best work so new visitors can quickly assess your voice and quality
- Build a long-term relationship with readers through subscriptions or follow options
- In some cases, demonstrate credibility for freelance commissions, book deals, or editorial partnerships
Common Structural Mistakes Writers Make
Dumping every article on the homepage
This is the most frequent error. The homepage becomes a chronological firehose of every post you've ever published. For a new visitor, this feels like walking into a library with no signage. They don't know where to start, what your best work is, or whether your recent output is representative of your overall quality.
A better approach: feature three to five selected pieces on the homepage, organized around a clear introduction that explains who you are and what you write about. Move the full archive to a dedicated "All Writing" or "Archive" page.
No author presence at all
Some writers' sites are nothing but content—no photo, no bio, no context. For existing fans, this is fine. For first-time visitors, it's a barrier. They don't know if you're an expert, a hobbyist, or a bot.
Your homepage needs at least one clear sentence: what you write about, why you write it, and who it's for. That context is what transforms a random click into a intentional follow.
Turning the About page into a resume
A writer's About page should not be a CV reformat. It should answer the question: "Should I keep reading this person's work?"
More useful than your employment history: the topics you obsess over, the perspective you bring, the consistency readers can expect, and what you stand for as a writer. Make it personal, not professional in the bureaucratic sense.
Recommended Structure for Writers
- Homepage: A concise identity statement (who you are, what you write about, who it's for) + three to five featured articles + a visible subscription or follow prompt
- Archive page: Complete article list, optionally filterable by topic or date
- About page: Your story, your obsessions, your writing philosophy, and what readers gain by following you
- Contact: Email or social links, accessible for editors, collaborators, or readers who want to reach out
If you're early in your writing journey and don't have much published yet, a single-page site with an intro, a few representative posts, and a contact link is perfectly sufficient. Don't wait for a massive archive to launch. A small, clear site beats a nonexistent one every time.
The Designer's Personal Website
What It Needs to Accomplish
A designer's site has a different set of imperatives:
- Help potential clients or employers quickly assess whether your style and capabilities match their needs
- Showcase representative projects, including process and rationale—not just polished final images
- Build enough trust that visitors feel comfortable initiating contact
Common Structural Mistakes Designers Make
Visuals without explanation
A portfolio of gorgeous final images, with no written context, tells a visitor almost nothing about your actual skills. They can see the output, but they can't see the thinking: What was the problem? What constraints did you face? Why did you make the decisions you made?
For most people evaluating a designer—clients, recruiters, creative directors—your process and judgment matter more than your visual polish. Beautiful work with no explanation looks like decoration. Beautiful work with clear reasoning looks like expertise.
Too many projects, too little depth
Fifteen projects, each with two images and a one-line caption, is a classic portfolio trap. It suggests breadth but reveals no depth.
Five carefully chosen projects, each with context, process, and outcome, is infinitely more persuasive. Curation is hard because it requires you to exclude work you might be proud of. But it's one of the most important skills a designer can demonstrate—and your portfolio is the first place you get to show it.
A homepage that doesn't specify your design direction
"Designer" is a massive umbrella. Brand design, UI design, product design, interaction design, motion design, spatial design, illustration—each is a distinct discipline with distinct client needs.
If your homepage simply says "Designer," visitors have to dig through your projects to figure out what you actually do. That's unnecessary friction. State your specialization explicitly and immediately.
Recommended Structure for Designers
- Homepage: A sharp professional positioning statement (what type of design you do, for whom) + three to five featured projects with substantial descriptions + a clear contact CTA
- Project detail pages: Background → Your specific role → Process and key decisions → Result or impact. This is where most designer portfolios are weakest, and where the most improvement is possible
- About page: Your trajectory, your design philosophy, what you're currently exploring, and what kinds of opportunities you're seeking
- Contact: Visible on both homepage and About page, with multiple options (email, form, calendar link)
If your work is inherently visual—photography, illustration, motion—give the images the space they deserve. But even then, pair each project with at least a short paragraph about the brief, your role, and the outcome.
The Indie Developer's Personal Website
What It Needs to Accomplish
An independent developer's personal website often serves multiple goals simultaneously:
- Showcase products and projects you've built
- Establish your personal brand within the developer or founder community
- Drive adoption for tools or products you're currently shipping
- Attract contract work, consulting engagements, or full-time opportunities
Common Structural Mistakes Developers Make
Using a GitHub profile as a stand-in for a personal site
GitHub is a powerful credential. It shows code quality, contribution history, and technical range. But it is not a personal website.
A GitHub profile cannot natively explain who you are in natural language, what problems you're passionate about solving, why your projects matter, or what a visitor should do next. Your personal site and your GitHub profile should complement each other, not compete or substitute.
Listing every project without hierarchy
Many developers populate their sites with every public repo they have: experiments, tutorials, abandoned side projects, forks of other people's work. For a visitor, this creates noise. They can't tell which projects represent your real capabilities and which are casual sketches.
A better approach: feature your two to four most significant projects prominently. For each, explain what it is, what problem it solves, what you built, and what the result was. Link to GitHub or live demos for visitors who want to dig deeper. Everything else can live in a secondary "More on GitHub" link.
Replacing capability descriptions with tech stack lists
"Python · TypeScript · PostgreSQL · Docker · AWS"
This tells a technical visitor what tools you've touched. It does not tell a non-technical client what you've built, what results you achieved, or why your approach was effective. Tech stack lists are convenient shorthand, but they are poor substitutes for project narratives.
Whenever possible, describe your capabilities through outcomes: "Built a real-time collaboration tool used by 500+ teams" is more persuasive than any list of frameworks.
Failing to clarify your current priorities
Many developer personal sites try to do everything at once: show side projects, attract consulting clients, recruit users for a product, and build a personal brand. Without clarity about which goal is primary, visitors don't know what action to take.
Your homepage should have one dominant purpose. Other goals can exist as secondary paths, but don't make visitors guess why they're on your site.
Recommended Structure for Indie Developers
- Homepage: A clear identity statement (who you are, what you build, what you're currently focused on) + two to four featured projects with meaningful descriptions + one primary CTA (contact, view product, or view work)
- Project write-ups: For each featured project, cover the background, your specific contributions, key technical decisions and their rationale, and the outcome or current status
- About page: Your path into development, your working style, what you're building now, and what kinds of collaborations or opportunities you're open to
- GitHub / demo links: Positioned adjacent to each project for visitors who want technical depth
- Contact: Direct email plus one or two relevant social links, visible without hunting
Principles That Apply to Everyone
Despite their different contexts, writers, designers, and indie developers all benefit from a few shared structural principles:
State your identity immediately
Every personal website homepage should answer "Who is this person and what do they do?" within five seconds. Never assume visitors will piece this together from your work samples.
Curate ruthlessly
Everyone wants to show their best side. But your best side is not your entire side. Three to five carefully selected, well-explained pieces of work outperform twenty thin listings every time.
Make the next step obvious
Whether it's subscribing, contacting you, viewing a project, or signing up for a tool, the desired action should be visible and unambiguous. Don't let visitors finish your site wondering what they're supposed to do next.
Ship first, iterate second
The most common trap across all three groups is waiting for the "perfect" personal website. A simple, launched site that clearly explains who you are, links to a few good examples of your work, and provides a way to reach you is infinitely more valuable than a hypothetical masterpiece that's still in Figma or your local dev environment.
Launch something clean and honest. Improve it based on real feedback and real usage. That's how good personal websites get built.
No matter which category you fall into, Otimififi's personal website templates give you a professionally structured starting point that you can adapt to your specific voice and goals—without wrestling with layout decisions from scratch.