How I set up this website


In this very first post, I’ll cover how I set up my own personal website and blog. I started by claiming a free student domain name through Combell using Academic Software, which gave me a good starting point to host my own platform.

Before actually building the site, I researched different CMS and static site options. I looked into tools such as WordPress and Jekyll, but neither of them really matched what I wanted. WordPress felt too heavy and bloated for a simple personal website, while Jekyll did not feel very intuitive to work with for me personally.

Eventually, I decided to use Astro, which turned out to be a much better fit for the kind of website I wanted to build. I started from one of their blog templates and spent quite a bit of time customizing the layout, styling, and structure to make it feel more personal.

Once the initial setup was finished, I deployed an intermediate version of the website containing my CV and an about me page, while the blog section still contained placeholder Lorem Ipsum text. This already allowed me to test the hosting setup and see how the website behaved in a production environment.

After that, I focused on writing and publishing the actual content for the blog, including reflections about events, projects, and activities. Once everything was finalized, I pushed the updated version of the website to the webserver hosting the static files.

Overall, it was a fun project that gave me more insight into static site generation, hosting, and web development workflows. It also felt rewarding to build something lightweight and fully customizable from scratch instead of relying on a traditional CMS.

Adding new articles to the website is straightforward. Astro stores blog posts as Markdown files, so whenever I want to publish a new article, I simply create a new file in the blog content directory, add the required metadata such as the title and publication date, and write the content using Markdown. Once the article is finished, Astro automatically includes it in the blog overview during the build process. After reviewing the changes locally, I rebuild the website and upload the updated static files to the webserver, making the new article available online.