In the previous episode, we outlined our roadmap using Project Management tools. Now it's time to get our hands dirty and set up the physical and visual foundations of our Project Zero.
When deciding to start a blog or portfolio, the standard approach (often suggested by marketers) is to buy a shared hosting package, install WordPress, and start downloading plugins. From a Sysadmin's perspective, this is a recipe for disaster: recurring costs, databases to maintain, constant security patches to apply, and often mediocre performance.
Let's see how to flip this paradigm.
1. The Infrastructure: Serverless Hosting and Domain
To slash costs and maintenance overhead, the ideal solution is to rely on serverless or fully managed platforms. Options like GitHub Pages or Blogger (Google's platform) are excellent. In my case, I chose Blogger.
Why? Because it provides us with an enterprise-grade infrastructure at zero cost. We get unlimited bandwidth, a pre-configured free SSL certificate, Google's global CDN, and most importantly, zero server-side maintenance. There are no SQL databases to optimize or PHP versions to update. The system is secured by design.
The only real cost you have to bear (about €10-15 per year) is purchasing a custom Top-Level Domain (e.g., yourname.com or .dev). This step is crucial for two reasons:
- Authority and SEO: A custom domain conveys professionalism and is indexed much better than a free subdomain (like .blogspot.com).
- DNS Control: Owning the domain allows you to manage the DNS zone. You can create MX records to have a professional email (e.g., info@yourname.com) and configure SPF, DKIM, and DMARC records for email security.
2. The Frontend: Choosing (or creating) the Theme
Once the server is sorted, you need the "bodywork". Here you have three paths:
- Free Themes: Ready to use, but often years old, not mobile-optimized, or full of hidden spam links. One good source of free themes is BTemplates
- Premium Themes (Paid): Costing around €30 to €60. They look good, but to please everyone, they include tons of useless JavaScript and CSS files, which kill loading times. A good source for paid themes could be ThemeForest. Usually with a paid theme the developer offers you 6 months of free technical support.
- The Custom Theme (The SysAdmin Approach): This is the path I chose for this site by developing the DualBoot 2.0 framework from scratch.
Writing a theme from the ground up in pure HTML, CSS, and a pinch of Vanilla JavaScript offers absolute control. No heavy external libraries (like jQuery) and no vulnerable plugins. The result? A page that weighs just a few kilobytes, loads instantly, and responds smoothly on both desktop and smartphones. From an SEO perspective, Google loves fast and lightweight websites.
In summary: delegate the heavy infrastructure to those who know how to manage it (Google/Blogger) and maintain total, surgical control over the frontend code.
In the next episode, we will dive into the world of telemetry: we will set up Google Analytics 4 and the Search Console to start monitoring our traffic logs professionally.