The main inspiration of this blog so far is the blog itself. Although I am not the best role model for a non-tech person, I have never made any serious web-pages. I plan to develop this one, starting with a simple resume page. But at this point I can caym that with the arrival of ChatGPT and its peers, the largest problem of a personal page creation is creating the content, not the code. While I can not advise on the hard part, here I start with an easy one: make your own page if you have never did it before

In general, to secure your own nice little corner of the web, you only need to follow three high-level phases:

1. Writing the actual code (Architecting the Source).
2. Moving that code to a platform capable of publishing it (Environment Setup).
3. Pushing the "Go Live" button (Deployment).

ChatGPT can essentially hold your hand through every single step. The only catch is that you need to know a bit of the technical "slang" that the AI understands. Here is some translation from human to machine language to get you started:

1. Concept to Code

   Start by gathering a few sites you admire. Copy the links and describe your "dream site" in your own words. ChatGPT will generate something that’s a bit of an "average of the bunch." Honestly, if you have a hyper-specific aesthetic in mind, this part might upset you and push you to a travel through a rabbit hole. But if not, you can get something quite respectable very quickly. Download the code as a ZIP archive, review the files, and tweak the copy. You could spend forever here, but you don't have to.

2. Version Control & Hosting

   Upload your finished code to a platform where it can be stored and published. I personally use GitLab. It’s useful to maintain two branches of the code: one that is live (production) and one for your own experiments (development). These two would be sufficient for most of the tasks. But no one forbids go get wild here (how do I create a per-feature branches in Git?)

3. Public Access

   There are two paths here:
   • The "Default" Route: Keep the slightly messy address that a platform like GitLab assigns you.
   • The "Pro" Route: Purchase a custom domain for about €10 a year. This won’t affect the look or performance of your site at all; it’s just the paint on the front door. Just ask the AI for step-by-step instructions on how to point your domain to your hosting. I skipped this for now.

And here it is: is my first and shallowdescription of this project. There are no trackers or "probes" there (at least at the time of the publishing), so you don't even have to deal with those annoying cookie policy pop-ups.