Personal Websites¶
When to build one, what to build it on, and what it actually costs
The Case for a Personal Website¶
A personal website is the only platform in this section that you fully control.
No algorithm determines who sees your content. No platform policy change can remove your work. No company acquisition can alter the terms under which your portfolio is hosted. No feed competes with your case studies for a reader's attention. The URL is yours, the structure is yours, the content is yours.
This platform independence is the primary argument for a personal website — not aesthetic control, not design flexibility, though both are real advantages. The deeper value is that a personal website does not depend on any third party remaining relevant, solvent, or aligned with your interests.
For a student building a professional presence that should outlast their degree, this matters more than it might initially appear.
When a Personal Website Is Worth Building¶
A personal website earns its effort when:
◆ you have enough content to justify the infrastructure — at minimum, two to three documented case studies, a current bio, and links to other professional presences
◇ your discipline does not have a dominant community platform that a personal site would compete with rather than complement — a design student with a strong Behance presence may benefit more from maintaining Behance than from building a parallel personal site
◆ you have the time and inclination to maintain it — a personal site that was last updated eighteen months ago and still shows first-year projects is actively harmful to a professional reputation
◇ you are approaching a professional moment — a job search, a freelance launch, a postgraduate application — where a cohesive, self-controlled presence adds credibility that platform profiles alone cannot provide
A personal website is not the right first step for most first-year students. It is a platform you grow into, not one you start with.
The Honest Cost Conversation¶
Most articles about personal portfolio websites skip the cost question. Itan does not — because the financial reality is different for a student on a tight budget versus a working professional, and the decision should reflect that honestly.
Domain name¶
A domain name (.com, .co.za, .io, or similar) typically costs between R150 and R400 per year depending on the extension and registrar. This is a fixed, recurring cost regardless of which hosting platform you choose.
Your domain is worth owning independently of your hosting — registered directly through a domain registrar (Namecheap, Cloudflare Registrar, and Google Domains are commonly used), not through your hosting platform. This keeps you free to move hosting providers without losing your domain.
Hosting and platform costs¶
The cost of maintaining a personal website ranges from genuinely free to several hundred rand per month, depending on what platform you choose and what features you need. The honest breakdown:
Free or near-free options:
◆ GitHub Pages — free hosting for static sites, directly from a GitHub repository. Supports custom domains. No monthly cost beyond the domain. Ideal for CS and engineering students who are already using GitHub — the technical overhead is low and the platform alignment is strong. A personal portfolio site hosted on GitHub Pages, built with HTML, CSS, and JavaScript, is itself evidence of technical capability.
◇ Netlify (free tier) — free hosting for static sites with a generous free tier that covers most student portfolio needs. Supports custom domains, continuous deployment from GitHub, and HTTPS. An accessible step up from GitHub Pages for students who want simpler deployment without cost.
◆ Notion (free tier as public page) — Notion pages can be made public and serve as a lightweight portfolio presence for students who are not ready to build a full site. Not a replacement for a proper personal site, but a legitimate intermediate step.
Low-cost options (R50–R200 per month):
◇ WordPress.com (personal plan) — the most widely used content management system in the world. The personal plan removes WordPress branding and allows a custom domain. Accessible to non-technical users, with thousands of portfolio-appropriate themes. The hosted version (WordPress.com) is different from the self-hosted version (WordPress.org) — the hosted version trades some flexibility for significantly reduced technical overhead.
◆ Squarespace — polished templates, strong design defaults, and a genuinely good editor for non-technical users. More expensive than WordPress at the entry level, but produces visually credible sites with less effort. The annual billing option reduces the effective monthly cost. Best suited to students in design-adjacent disciplines where visual presentation of the portfolio site itself carries weight.
◇ Wix — accessible and template-driven, with a free tier (though free Wix sites carry Wix branding and a Wix subdomain rather than a custom domain). A paid plan is needed for professional use. Lower ceiling on design quality compared to Squarespace, but lower cost and accessible to complete beginners.
Mid-range options (R200–R600 per month):
◆ Webflow — the most powerful no-code website builder available. Produces genuinely custom websites without writing code, but has a steeper learning curve than Squarespace or Wix. For design students, Webflow proficiency is itself a marketable skill — the tool is widely used in professional design and front-end development contexts. The free tier allows building and publishing to a Webflow subdomain; a paid plan is needed for a custom domain.
◇ Framer — a newer platform that bridges design and development, popular with product designers and developers comfortable with React-adjacent workflows. Produces visually sophisticated sites quickly. Growing in community adoption among designers and front-end developers. Free tier available; custom domain requires a paid plan.
Design-community specific:
◆ Cargo — built specifically for artists, designers, and creative practitioners. Strong visual defaults and a design-community reputation that adds credibility within those fields. Annual billing model; less expensive than Webflow for comparable visual output. Best suited to students in visual arts, design, and creative disciplines.
◇ Format — oriented toward photographers, designers, and visual artists. Strong image presentation, clean templates, and portfolio-specific features (client proofing, print ordering). More relevant for photography and visual arts students than for software or research-led disciplines.
The student recommendation¶
For most students, the cost-benefit analysis points clearly:
If you are a CS, IT, or engineering student: GitHub Pages with a custom domain is the right starting point. Zero hosting cost, maximum technical credibility, and the site itself demonstrates relevant skills. Total annual cost is the domain registration only.
If you are a design student: Webflow or Cargo justify their cost because the tool proficiency is professionally relevant and the visual output is appropriately high. If cost is a constraint, Cargo's annual pricing is more accessible. Squarespace is the most accessible alternative if the learning curve of Webflow is prohibitive.
If you are in a non-technical, non-design discipline: WordPress.com or Squarespace provide the right balance of accessibility, professional appearance, and manageable cost. The free tier of either is not sufficient for professional use — the branded subdomain and platform watermarks undermine the credibility the site is meant to establish.
For every discipline: domain cost is worth paying. A portfolio at yourname.com is a different professional signal from one at yourname.wixsite.com or yourname.github.io. The domain is the smallest recurring cost and one of the highest-return investments in a personal portfolio.
What Your Personal Site Should Contain¶
A personal portfolio site is not a different format from a portfolio — it is the same content, hosted in a space you control.
At minimum, a personal portfolio site should include:
◆ a home or landing page that immediately communicates who you are and what you do — your positioning statement, a brief introduction, and clear navigation to your work
◇ your portfolio entries — case studies documented to the standard from Part Ⅳ
◆ an about page — your full bio, your positioning statement, your professional background
◇ a contact route — an email link, a contact form, or links to your LinkedIn and GitHub
◆ links to your other professional presences — GitHub, LinkedIn, Behance, or whatever platforms are relevant to your discipline
What it does not need:
◆ a blog — unless you are genuinely committed to writing regularly. An empty blog or one last updated two years ago is a negative signal.
◇ a services or hire me page — unless you are actively freelancing
◆ a comprehensive list of every technology you have used
◇ a loading animation, a parallax scrolling effect, or any other design element that delays a reader getting to your content
Platform Independence as a Long-Term Principle¶
The platforms available to you today are not necessarily the platforms that will be most relevant in five years. Platforms rise, consolidate, pivot, and occasionally shut down.
Platform independence — hosting your primary portfolio presence on a domain you own, using a platform you can migrate away from — protects you from these shifts.
The content you build is yours regardless of the platform. A case study written and documented to the standard Itan describes does not become obsolete because a platform changes its pricing model. The habit of owning your domain and maintaining platform-agnostic content is a professional habit worth building early.