+1 -1

starlight/src/content/docs/blog/accelerating-translations-with-continuous-integration.mdx

reviewed

··· 17 17 18 18 For the last year, I have been working a lot in various Open Source Communities on GitHub in my free time and I have been enjoying these somehow relaxing contributions because they help me gain new knowledge on a daily basis. 19 19 20 20 - After some time contributing I also got to know how kind and welcoming communities behind those projects are. These people have all one thing in common with you: They want to build great stuff in their leisure time. Especially the Astro community is the one and only I have enjoyed being in the most, since it's the most rewarding and friendly at the same time. Not all communities can achieve such a great status among OSS. 20 20 + After some time contributing I also got to know how kind and welcoming communities behind those projects are. These people have all one thing in common with you: They want to build great stuff in their leisure time. Especially the [Astro](https://github.com/withastro) community is the one and only I have enjoyed being in the most, since it's the most rewarding and friendly at the same time. Not all communities can achieve such a great status among OSS. 21 21 22 22 Recently, I discovered another evolving project founded by [pelikhan](https://github.com/pelikhan) which aims to automatically translate all your documentation, blogs or shop sites whenever something changes with the help of AI. Whilst initially sceptical, reading more about the project in its README.md had me hooked. 23 23

+5 -5

starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md

reviewed

··· 14 14 image: ../../../../public/blog/setup-argocd-for-kubernetes.png 15 15 --- 16 16 17 17 - Having read Vegard S. Hagen's article “[Argo CD Kustomize with Helm](https://blog.stonegarden.dev/articles/2023/09/argocd-kustomize-with-helm/)” and decided that their solution was not the way to go for our cluster, we jumped straight into the default Argo CD “[Getting started](https://argo-cd.readthedocs.io/en/stable/getting_started/)” guide. And now we will walk you through the pain of setting up Argo CD on k3s and cilium, continuing from the chapter “[Setup Certificate Manager with Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare#setup-certificate-manager-with-cloudflare)” of our most recent post “[Setting up Kubernetes with Cilium and Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare)”. In this exact recent post we also set up [Keel](https://keel.sh/) at the end, but this step will now be unnecessary because we'll use Argo CD for getting the newest state-of-the-art code from each GitHub repo. Enjoy reading! 17 17 + Having read Vegard S. Hagen's article “[Argo CD Kustomize with Helm](https://blog.stonegarden.dev/articles/2023/09/argocd-kustomize-with-helm/)” and decided that their solution was not the way to go for our cluster, we jumped straight into the default Argo CD “[Getting started](https://argo-cd.readthedocs.io/en/stable/getting_started/)” guide. And now we will walk you through the pain of setting up [Argo CD](https://github.com/argoproj) on [k3s](https://github.com/k3s-io) and [Cilium](https://github.com/cilium), continuing from the chapter “[Setup Certificate Manager with Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare#setup-certificate-manager-with-cloudflare)” of our most recent post “[Setting up Kubernetes with Cilium and Cloudflare](/blog/setup-kubernetes-with-cilium-and-cloudflare)”. In this exact recent post we also set up [Keel](https://github.com/keel-hq) at the end, but this step will now be unnecessary because we'll use Argo CD for getting the newest state-of-the-art code from each GitHub repo. Enjoy reading! 18 18 19 19 :::note 20 20 We assume that you followed [our other blog post](/blog/setup-kubernetes-with-cilium-and-cloudflare). ··· 106 106 107 107 ## Deactivate TSL within Argo CD 108 108 109 109 - With the certificate the connection between the client and server is secured. However, there is still a self-signed certificate within the Argo CD services, which we don't necessarily need. We can therefore deactivate the security of the Argo CD server, by editing the property `server.insecure`. 109 109 + With the certificate the connection between the client and server is secured. However, there is still a self-signed certificate within the [Argo CD](https://github.com/argoproj) services, which we don't necessarily need. We can therefore deactivate the security of the Argo CD server, by editing the property `server.insecure`. 110 110 111 111 In order to do that, we first run this command: 112 112 ··· 165 165 166 166 ## Add manifest to repository 167 167 168 168 - Now in order to create a new application in Argo CD (either UI or CLI — we use UI cause we didn't setup CLI), we need to prepare the Git repository. Because the repository is the single source of truth, this is also the place, where we define all the kubernetes resources which should be created by Argo CD. 168 168 + Now in order to create a new application in [Argo CD](https://github.com/argoproj) (either UI or CLI — we use UI cause we didn't setup CLI), we need to prepare the Git repository. Because the repository is the single source of truth, this is also the place, where we define all the kubernetes resources which should be created by Argo CD. 169 169 170 170 We recommend creating a new folder in the git repository called something like `manifest`. In this folder, we'll create a few files: 171 171 ··· 261 261 262 262 ## Create new application in Argo CD UI 263 263 264 264 - You'll probably see the big `NEW APP` button in the Argo CD UI. Click it and create a new application with adapted properties from below: 264 264 + You'll probably see the big `NEW APP` button in the UI of [Argo CD](https://github.com/argoproj). Click it and create a new application with adapted properties from below: 265 265 266 266 - Application Name: `mutanuq` 267 267 - Project Name: `default` ··· 290 290 291 291 ## Celebrate with a Coffee! 292 292 293 293 - Congratulations, you've successfully set up Argo CD with k3s and Cilium! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you! 293 293 + Congratulations, you've successfully set up [Argo CD](https://github.com/argoproj) on a [k3s](https://github.com/k3s-io) cluster! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you! 294 294 295 295 ## Continuation 296 296

+1 -1

starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md

reviewed

··· 273 273 274 274 ## Celebrate with a Coffee! 275 275 276 276 - Congratulations, you've successfully set up Argo CD with k3s and Cilium! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you! 276 276 + Congratulations, you've successfully set up Argo CD with k3s and [Cilium](https://github.com/cilium)! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you!

+8 -8

starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md

reviewed

··· 14 14 image: ../../../../public/blog/setup-kubernetes-with-cilium-and-cloudflare.png 15 15 --- 16 16 17 17 - Working with Docker Containers can be hard. However, there are tools which enhance the management of containers, like Kubernetes. Actually, Kubernetes is the only tool to my knowledge which acts as a management software for Docker Containers. Kubernetes is well-integrated in almost all cloud providers, like Google Cloud, Azure and AWS. As a result, it has a standardized `yaml`-syntax, which is great for small developers because they can switch between `The Big Three` with low effort. 17 17 + Working with [Docker](https://github.com/docker) Containers can be hard. However, there are tools which enhance the management of containers, like [Kubernetes](https://github.com/kubernetes). Actually, Kubernetes is the only tool to my knowledge which acts as a management software for Docker Containers. Kubernetes is well-integrated in almost all cloud providers, like Google Cloud, Azure and AWS. As a result, it has a standardized `yaml`-syntax, which is great for small developers because they can switch between `The Big Three` with low effort. 18 18 19 19 ## tl;dr 20 20 ··· 98 98 --cluster-init 99 99 ``` 100 100 101 101 - After the installation, there should be some pods running (3). Don't be shocked if the pods are in the `ContainerCreating` or `Pending` state. This is because the pods can't communicate between each other because we disabled the CNI (`--flannel-backend=none`). We will later install Cilium, which will be the replacement of the Flannel CNI. 101 101 + After the installation, there should be some pods running (3). Don't be shocked if the pods are in the `ContainerCreating` or `Pending` state. This is because the pods can't communicate between each other because we disabled the CNI (`--flannel-backend=none`). We will later install [Cilium](https://github.com/cilium), which will be the replacement of the Flannel CNI. 102 102 103 103 ```bash 104 104 kubectl get pods -A ··· 106 106 107 107 ## Install Helm 108 108 109 109 - Helm is the package manager for Kubernetes, so you should either install it directly (follow the [Helm docs](https://helm.sh/docs/intro/install/)) or use parts of Helm which are shipped with Cilium. We chose to install Helm directly, which is easily possible with this command: 109 109 + Helm is the package manager for [Kubernetes](https://github.com/kubernetes), so you should either install it directly (follow the [Helm docs](https://helm.sh/docs/intro/install/)) or use parts of Helm which are shipped with Cilium. We chose to install Helm directly, which is easily possible with this command: 110 110 111 111 ```bash 112 112 curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash ··· 114 114 115 115 ## Install Cilium 116 116 117 117 - Cilium is a networking and security software for Kubernetes. Cilium is very fast, scalable and secure because it's built upon eBPF -- a revolutionary technology that can run sandboxed programs in the Linux kernel without recompiling the kernel or loading kernel modules. 117 117 + [Cilium](https://github.com/cilium) is a networking and security software for Kubernetes. Cilium is very fast, scalable and secure because it's built upon eBPF -- a revolutionary technology that can run sandboxed programs in the Linux kernel without recompiling the kernel or loading kernel modules. 118 118 119 119 We could install Cilium with Helm like shown here: 120 120 ··· 253 253 254 254 ## Setup Certificate Manager with Cloudflare 255 255 256 256 - In order to be able to create certificates for each subdomain, it is important to apply a certificate issuer which handles certificate requests and resolves them at some provider. We chose Cloudflare as our issuer and here is the setup which you need to apply to your kubernetes cluster. For further information you can check out the [cert-manager docs](https://cert-manager.io/docs/configuration/acme/dns01/cloudflare/). 256 256 + In order to be able to create certificates for each subdomain, it is important to apply a certificate issuer which handles certificate requests and resolves them at some provider. We chose [Cloudflare](https://github.com/cloudflare) as our issuer and here is the setup which you need to apply to your Kubernetes cluster. For further information you can check out the [cert-manager docs](https://cert-manager.io/docs/configuration/acme/dns01/cloudflare/). 257 257 258 258 But first, we need to install the cert-manager by running the following command: 259 259 ··· 283 283 key: api-token 284 284 ``` 285 285 286 286 - You can apply a file to the Kubernetes cluster, by running this k8s (also k3s) command: 286 286 + You can apply a file to the [Kubernetes](https://github.com/kubernetes) cluster, by running this k8s (also k3s) command: 287 287 288 288 ```bash 289 289 kubectl apply -f cluster-issuer.yaml ··· 297 297 298 298 As you may have spotted above, we also need a secret for the API token which authenticates that this issuer is allowed to request certificates. Therefore, we create a secret with an unencrypted `API Token` from Cloudflare. 299 299 300 300 - Nowadays we create a token by going to your Cloudflare dashboard, then click on your profile and select the tab `API Tokens`. Here you can generate a specific token for your issuer or use the Global API Key (not recommended any more). The recommended solution is to create a API token with two permissions (custom token): 300 300 + Nowadays we create a token by going to your [Cloudflare](https://github.com/cloudflare) dashboard, then click on your profile and select the tab `API Tokens`. Here you can generate a specific token for your issuer or use the Global API Key (not recommended any more). The recommended solution is to create a API token with two permissions (custom token): 301 301 302 302 - Zone - DNS - Edit 303 303 - Zone - Zone - Read ··· 711 711 712 712 ## Celebrate with a Coffee! 713 713 714 714 - Congratulations, you've successfully set up Kubernetes with Cilium and Cloudflare! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you! 714 714 + Congratulations, you've successfully set up [Kubernetes](https://github.com/kubernetes) with [Cilium](https://github.com/cilium) and [Cloudflare](https://github.com/cloudflare)! You deserve a coffee break. Enjoy a well-earned cup, and if you'd like to share a virtual coffee with me, feel free to support my work on [Ko-fi](https://ko-fi.com/trueberryless). Thank you! 715 715 716 716 ## Troubleshooting 717 717

+1 -1

starlight/src/content/docs/blog/starlight-topics-history-story.md

reviewed

··· 20 20 21 21 However, one thing that's objectively missing in my opinion is a granular way of separating broad topics inside your documentation. And I'm not alone with this subjectively general accepted opinion. [HiDeoo](https://github.com/HiDeoo) is not only one of the most active maintainers of the project, but also the author of the most and imho best plugins you can find for Starlight. And they have also noticed this missing niche functionality about topics. That's why they decided to create the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin early on, back in October 2024, which allows you to make a sidebar with topics. Read more about the plugin's functionalities in [its documentation](https://starlight-sidebar-topics.netlify.app/). 22 22 23 23 - The one thing that bothered me personally in the early days of the plugin was the way topics were displayed in the sidebar. Because it doesn't - like I imagined a solution could look like - use some kind of dropdown menu for switching between topics, but instead always shows all topics. This design choice was, as [HiDeoo clearly points out](https://github.com/HiDeoo/starlight-sidebar-topics/issues/2#issuecomment-2410196392), very intentional and not without any reason: All topics should be visible at once. Proven by the Astro docs themselves ([Chris Swithinbank](https://github.com/delucis) implemented the ["tabbed sidebar"](https://github.com/withastro/docs/pull/9890) for the Astro v5 docs later in the same month), this approach definitely has many benefits over a dropdown menu. Nonetheless, I was still unsatisfied by this design, and so I created my own version. 23 23 + The one thing that bothered me personally in the early days of the plugin was the way topics were displayed in the sidebar. Because it doesn't - like I imagined a solution could look like - use some kind of dropdown menu for switching between topics, but instead always shows all topics. This design choice was, as [HiDeoo clearly points out](https://github.com/HiDeoo/starlight-sidebar-topics/issues/2#issuecomment-2410196392), very intentional and not without any reason: All topics should be visible at once. Proven by the [Astro](https://github.com/withastro) docs themselves ([Chris Swithinbank](https://github.com/delucis) implemented the ["tabbed sidebar"](https://github.com/withastro/docs/pull/9890) for the Astro v5 docs later in the same month), this approach definitely has many benefits over a dropdown menu. Nonetheless, I was still unsatisfied by this design, and so I created my own version. 24 24 25 25 Copying and pasting was my strength when it came to building a new Starlight plugin for the community. And so, I did just that. I took the Starlight Sidebar Topics plugin as a starting point and just had to adapt the `Topics.astro` component, which includes the HTML for rendering the topics in the sidebar. After struggling for some time with the implementation of a satisfying enough dropdown menu, which was pure HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myself), I finally found a solution that I'm very satisfied with and released this new plugin under the name [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) - how original. 26 26

+1 -1

starlight/src/content/docs/blog/writing-blogs-is-hard-and-easy.mdx

reviewed

··· 14 14 tableOfContents: false 15 15 --- 16 16 17 17 - After a very interesting discussion in the [Astro Discord](https://astro.build/chat) - started by none other than core maintainer [Alex](https://github.com/alexanderniebuhr) himself (btw congratulations on this recent achievement 🎉) -, I joked around that someone could write a blog about reasons why it is so difficult for many people to not only write, but also maintain a blog as a whole. 17 17 + After a very interesting discussion in the [Astro](https://github.com/withastro) [Discord](https://astro.build/chat) - started by none other than core maintainer [Alex](https://github.com/alexanderniebuhr) himself (btw congratulations on this recent achievement 🎉) -, I joked around that someone could write a blog about reasons why it is so difficult for many people to not only write, but also maintain a blog as a whole. 18 18 19 19 The man who nominated me as an Astro Support Squad - [Jacob](https://github.com/jdtjenkins) (btw thank you very much for noticing me within this awesome community 😍) - took that quite literally and wrote a blog about it. No joke. Check it out: https://jacobjenkins.codes/posts/why-is-writing-blogs-so-hard/ This is his first every blog btw (and hopefully not his last one, as I really enjoyed reading his style). 20 20