Changed categories and tags, added warning.

content/blog/01-blog.md

@@ -4,12 +4,16 @@ draft: false
 title: "Let's start a blog!"
 author: "Jirka"
 tags: ["hugo", "idea", "guide", "tutorial"]
-categories: ["documentation", "idea"]
+categories: ["blog", "idea"]
 description: "Behind the scenes of the idea and setup."
 ---
 
 This blog has been created as one of my personal projects, first one released on this page. (Actually, this article, about creating this blog, is being written before creation of the blog and this page).
 
+> [!WARNING]
+> If you decide to follow my steps, please, be careful and use your head. I do not guarantee they will work for you and do so at your own risk.
+
+
 ## How it started
 
 The original idea was simple: **I would like to share my projects and knowledge with others.** But how?
@@ -36,7 +40,7 @@ This article is just about how to set up the Hugo for my purpose and how the con
 
 ## Hugo setup
 
-Work with hugo is super simple, I've start with their official [guide](https://gohugo.io/getting-started/quick-start/), but I will cover basic steps here.
+Work with Hugo is super simple, I've start with their official [guide](https://gohugo.io/getting-started/quick-start/), but I will cover basic steps here.
 
 To create empty Hugo project (after installing Hugo), start with:
 ```bash
@@ -142,3 +146,6 @@ So I've created `layouts/_default/_markup/render-link.html` will follow content:
 ```
 
 It creates correct links just from file links and will warn me if anything will go wrong.
+
+---
+This article is one from series about this blog and self-hosting. All connected articles can found [here](categories/blog).

content/blog/02-hosting-blog.md

@@ -1,16 +1,19 @@
 ---
 date: '2026-03-24T10:17:21+01:00'
 draft: false
-title: 'Hosting Blog'
+title: 'How to self-host a blog'
 author: "Jirka"
-tags: ["caddy", "vps", "wireguard", "docker", "guide", "tutorial"]
+tags: ["caddy", "docker", "wireguard", "vps", "guide", "tutorial", "self-hosted"]
-categories: ["blog", "self-hosting"]
+categories: ["blog"]
-description: "How this blog came online."
+description: "How this blog came online without public IP."
 ---
 
 In last post [Let's start a blog!](./01-blog.md) I've introduced idea and how-to guide how I will write this blog, but left it offline.
 That is going to change in this post.
 
+> [!WARNING]
+> If you decide to follow my steps, please, be careful and use your head. I do not guarantee they will work for you and do so at your own risk.
+
 ## Requirements
 
 This whole blog/website project is about self-hosting. That said, I will host this page my on server/PC at home. For that, you usually have public IP address.
@@ -261,3 +264,6 @@ docker compose up -d
 ```
 
 And your web should be online.
+
+---
+This article is one from series about this blog and self-hosting. All connected articles can found [here](categories/blog).

content/blog/03-gitea.md

@@ -4,7 +4,7 @@ draft: false
 title: 'Time for version control'
 author: "Jirka"
 tags: ["gitea", "self-hosted", "docker", "guide", "tutorial"]
-categories: ["self-host", "documentation"]
+categories: ["blog"]
 description: "Let's look at how to self host gitea on our infrastructure."
 ---
 
@@ -12,6 +12,9 @@ How would I share my projects with you, if I do not have any git hosting server?
 
 That is a reason, why we need to set up one! You can choose from more variant, but I decided for [Gitea](https://about.gitea.com/).
 
+> [!WARNING]
+> If you decide to follow my steps, please, be careful and use your head. I do not guarantee they will work for you and do so at your own risk.
+
 ## Self-hosting Gitea
 
 Thanks to our earlier setup, next step is pretty simple.
@@ -154,3 +157,6 @@ git.jirkabuilds.dev {
 If you have set up DNS correctly, after shutting the stack down and up the Gitea should be online.
 
 And that's it!
+
+---
+This article is one from series about this blog and self-hosting. All connected articles can found [here](categories/blog).

content/blog/04-automatic-release.md

@@ -3,8 +3,8 @@ date: '2026-03-24T20:36:26+01:00'
 draft: false
 title: 'Automatic web update release'
 author: "Jirka"
-tags: ["self-host", "gitea", "automation"]
+tags: ["self-hosted", "gitea", "automation", "docker"]
-categories: ["self-host", "documentation", "automation"]
+categories: ["blog"]
 description: "Last step, how to relase changes to web automatically"
 ---
 
@@ -14,6 +14,9 @@ The idea is simple, push changes to `master` branch of repo holding this web and
 
 We will split this problem into two: Building web with Hugo and second, updating files with webhook. Let's start.
 
+> [!WARNING]
+> If you decide to follow my steps, please, be careful and use your head. I do not guarantee they will work for you and do so at your own risk.
+
 ## Set up Gitea runner
 
 Gitea does support actions like GitHub, but you have to provide it runner to execute you tasks. We are going to use the most secured way, runner in docker, which will start another docker container in another docker.
@@ -278,3 +281,6 @@ Final last step is to replace #TODO in our workflow with following:
 ```
 
 And that is it. On next push, web should update itself automatically.
+
+---
+This article is one from series about this blog and self-hosting. All connected articles can found [here](categories/blog).