Repository: trueberryless-org/blog
Pull request #57: feat: add story and guide for topics composition
Author: login: trueberryless
Labels: name: 📦 package
description: Updates in package structure or package.json
name: 🌏 i18n
description: Updates to internationalized docs, excluding English
Created: 2025-05-05T17:59:57Z | Merged: 2025-05-15T15:56:42Z



<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **New Features**
  - Added two new blog posts: "A short history of Starlight Sidebar Topics plugins" and "Starlight Topics Dropdown and List together," offering insights and practical guidance on sidebar topic navigation.
- **Documentation**
  - Added concise description metadata to several blog posts, improving discoverability and providing quick summaries for readers.
- **Chores**
  - Updated the starlight-blog dependency to the latest version for improved stability and features.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->


Diff:
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index e764f5f6..6e77a501 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -57,8 +57,8 @@ importers:
         specifier: ^0.32.6
         version: 0.32.6
       starlight-blog:
-        specifier: ^0.21.0
-        version: 0.21.0(@astrojs/starlight@0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)))(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))
+        specifier: ^0.23.2
+        version: 0.23.2(@astrojs/starlight@0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)))(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))
       starlight-image-zoom:
         specifier: ^0.10.1
         version: 0.10.1(@astrojs/starlight@0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)))
@@ -113,6 +113,12 @@ packages:
     peerDependencies:
       astro: ^5.0.0
 
+  '@astrojs/mdx@4.2.6':
+    resolution: {integrity: sha512-0i/GmOm6d0qq1/SCfcUgY/IjDc/bS0i42u7h85TkPFBmlFOcBZfkYhR5iyz6hZLwidvJOEq5yGfzt9B1Azku4w==}
+    engines: {node: ^18.17.1 || ^20.3.0 || >=22.0.0}
+    peerDependencies:
+      astro: ^5.0.0
+
   '@astrojs/prism@3.2.0':
     resolution: {integrity: sha512-GilTHKGCW6HMq7y3BUv9Ac7GMe/MO9gi9GW62GzKtth0SwukCu/qp2wLiGpEujhY+VVhaG9v7kv/5vFzvf4NYw==}
     engines: {node: ^18.17.1 || ^20.3.0 || >=22.0.0}
@@ -1210,6 +1216,9 @@ packages:
   es-module-lexer@1.6.0:
     resolution: {integrity: sha512-qqnD1yMU6tk/jnaMosogGySTZP8YtUgAffA9nMN+E/rjxcfRQ6IEk7IiozUjgxKoFHBGjTLnrHB/YC45r/59EQ==}
 
+  es-module-lexer@1.7.0:
+    resolution: {integrity: sha512-jEQoCwk8hyb2AZziIOLhDqpm5+2ww5uIE6lkO/6jcOCusfk6LhMHpXXfBLXTZ7Ydyt0j4VoUQv6uGNYbdW+kBA==}
+
   esast-util-from-estree@2.0.0:
     resolution: {integrity: sha512-4CyanoAudUSBAn5K13H4JhsMH6L9ZP7XbLVe/dKybkxMO7eDyLsT8UHl9TRNrU2Gr9nz+FovfSIjuXWJ81uVwQ==}
 
@@ -2115,8 +2124,8 @@ packages:
   space-separated-tokens@2.0.2:
     resolution: {integrity: sha512-PEGlAwrG8yXGXRjW32fGbg66JAlOAwbObuqVoJpv/mRgoWDQfgH1wDPvtzWyUSNAXBGSk8h755YDbbcEy3SH2Q==}
 
-  starlight-blog@0.21.0:
-    resolution: {integrity: sha512-ZA6y+LTbEr2aH8IOsQ3yIFRcqDNEDJjFG/OVTYbWgDuWuO3DWPGYjovsG4oSarbpxkP1k5OLPtL8Zmhy6DxiNQ==}
+  starlight-blog@0.23.2:
+    resolution: {integrity: sha512-ymyCOsohNb7xomYEL0+S6kV+RWE8uN3FJs6IqgKu2+930nt31zem+NYTCu81BO1wIXx3aF/qPK04RWLZ3wXhIg==}
     engines: {node: '>=18.17.1'}
     peerDependencies:
       '@astrojs/starlight': '>=0.33.0'
@@ -2715,6 +2724,25 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
+  '@astrojs/mdx@4.2.6(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))':
+    dependencies:
+      '@astrojs/markdown-remark': 6.3.1
+      '@mdx-js/mdx': 3.1.0(acorn@8.14.1)
+      acorn: 8.14.1
+      astro: 5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)
+      es-module-lexer: 1.7.0
+      estree-util-visit: 2.0.0
+      hast-util-to-html: 9.0.5
+      kleur: 4.1.5
+      rehype-raw: 7.0.0
+      remark-gfm: 4.0.1
+      remark-smartypants: 3.0.2
+      source-map: 0.7.4
+      unist-util-visit: 5.0.0
+      vfile: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
+
   '@astrojs/prism@3.2.0':
     dependencies:
       prismjs: 1.29.0
@@ -3786,6 +3814,8 @@ snapshots:
 
   es-module-lexer@1.6.0: {}
 
+  es-module-lexer@1.7.0: {}
+
   esast-util-from-estree@2.0.0:
     dependencies:
       '@types/estree-jsx': 1.0.5
@@ -5266,16 +5296,19 @@ snapshots:
 
   space-separated-tokens@2.0.2: {}
 
-  starlight-blog@0.21.0(@astrojs/starlight@0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)))(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)):
+  starlight-blog@0.23.2(@astrojs/starlight@0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)))(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1)):
     dependencies:
-      '@astrojs/mdx': 4.2.5(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))
+      '@astrojs/markdown-remark': 6.3.1
+      '@astrojs/mdx': 4.2.6(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))
       '@astrojs/rss': 4.0.11
       '@astrojs/starlight': 0.34.1(astro@5.7.5(rollup@4.40.1)(typescript@5.7.3)(yaml@2.7.1))
       astro-remote: 0.3.4
       github-slugger: 2.0.0
       marked: 15.0.11
       marked-plaintify: 1.1.1(marked@15.0.11)
+      mdast-util-mdx-expression: 2.0.1
       ultrahtml: 1.6.0
+      unist-util-visit: 5.0.0
     transitivePeerDependencies:
       - astro
       - supports-color
diff --git a/starlight/package.json b/starlight/package.json
index 6e4d9323..0c98326c 100644
--- a/starlight/package.json
+++ b/starlight/package.json
@@ -22,7 +22,7 @@
     "@fontsource/tauri": "^5.0.20",
     "astro": "^5.7.5",
     "sharp": "^0.32.6",
-    "starlight-blog": "^0.21.0",
+    "starlight-blog": "^0.23.2",
     "starlight-image-zoom": "^0.10.1",
     "starlight-links-validator": "^0.14.2",
     "starlight-theme-rapide": "^0.4.0",
diff --git a/starlight/src/assets/covers/dropdownandlist.png b/starlight/src/assets/covers/dropdownandlist.png
new file mode 100644
index 00000000..4601fa47
Binary files /dev/null and b/starlight/src/assets/covers/dropdownandlist.png differ
diff --git a/starlight/src/assets/covers/historytime.png b/starlight/src/assets/covers/historytime.png
new file mode 100644
index 00000000..357dc97d
Binary files /dev/null and b/starlight/src/assets/covers/historytime.png differ
diff --git a/starlight/src/assets/dropdown-or-list.png b/starlight/src/assets/dropdown-or-list.png
new file mode 100644
index 00000000..13892aff
Binary files /dev/null and b/starlight/src/assets/dropdown-or-list.png differ
diff --git a/starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md b/starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md
index 9fc6747b..98385d2e 100644
--- a/starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md
+++ b/starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md
@@ -1,5 +1,6 @@
 ---
 title: Setting up Argo CD in a k3s cluster
+description: Today we'll take a look at how to set up Argo CD in a k3s cluster.
 date: 2024-07-27
 lastUpdated: 2024-07-28
 tags:
diff --git a/starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md b/starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md
index 8051c3b0..73e683a6 100644
--- a/starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md
+++ b/starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md
@@ -1,5 +1,6 @@
 ---
 title: Setting up Continuous deployment in a GitHub repository
+description: Today we'll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD.
 date: 2024-07-28
 tags:
     - CI/CD
diff --git a/starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md b/starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md
index 945875d0..882340b5 100644
--- a/starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md
+++ b/starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md
@@ -1,5 +1,6 @@
 ---
 title: Setting up Kubernetes with Cilium and Cloudflare
+description: Today we'll take a look at how to set up a Kubernetes cluster with K3s and Cilium.
 date: 2024-06-11
 lastUpdated: 2024-10-01
 tags:
diff --git a/starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx b/starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx
new file mode 100644
index 00000000..63fbb301
--- /dev/null
+++ b/starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx
@@ -0,0 +1,117 @@
+---
+title: Starlight Topics Dropdown and List together
+description: Learn how to combine a desktop list and mobile dropdown for your Starlight sidebar topics.
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to show a list of topics on desktop and a dropdown menu in the mobile sidebar.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownandlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Install the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
+
+## Modify the Sidebar component
+
+In the setup guide from the dropdown component, you have created a sidebar component, which only renders the dropdown menu. Now, you need to modify this component to also render the default sidebar if the user is on desktop.
+
+```astro
+---
+// src/components/Sidebar.astro
+import Default from '@astrojs/starlight/components/Sidebar.astro';
+import Topics from 'starlight-sidebar-topics/components/Sidebar.astro';
+import TopicsDropdown from 'starlight-sidebar-topics-dropdown/TopicsDropdown.astro';
+---
+
+<div class="topics">
+  <Topics/>
+</div>
+<div class="topics-dropdown">
+  <TopicsDropdown/>
+</div>
+<Default><slot /></Default>
+
+<style>
+  /* Hide topics by default and show them on medium screens and larger */
+  .topics {
+    display: none;
+  }
+
+  @media (min-width: 800px) {
+    .topics {
+      display: block;
+    }
+  }
+
+  /* Show topics dropdown on small screens and hide it on medium screens and larger */
+  .topics-dropdown {
+    display: block;
+  }
+
+  @media (min-width: 800px) {
+    .topics-dropdown {
+      display: none;
+    }
+  }
+</style>
+```
+
+## Result
+
+If you follow these steps, your sidebar will look like this:
+
+![Final result with desktop view on the left and mobile view on the right](../../../assets/dropdown-or-list.png)
+
+You can find the complete source code of this guide in this [StackBlitz example](https://stackblitz.com/edit/withastro-starlight-qgraahmp?file=astro.config.mjs).
+
+## Endless possibilities
+
+You could also do it the other way around (list on mobile, dropdown on desktop) by swapping the `display: block` and `display: none` properties in the CSS.
+
+Moreover, you could also create your own display component, which uses the route data from the Starlight Sidebar Topics plugin and renders the topics in a custom way. This is a bit more advanced, but you can find more information about this in the ["Custom Topics List" documentation](https://starlight-sidebar-topics.netlify.app/docs/guides/custom-topic-list/).
diff --git a/starlight/src/content/docs/blog/starlight-sidebar-whitespace.md b/starlight/src/content/docs/blog/starlight-sidebar-whitespace.md
index b9e1241e..8ecaad44 100644
--- a/starlight/src/content/docs/blog/starlight-sidebar-whitespace.md
+++ b/starlight/src/content/docs/blog/starlight-sidebar-whitespace.md
@@ -1,5 +1,6 @@
 ---
 title: How to make your Starlight sidebar items look better
+description: In this blog post, we'll take a look at how small changes can make a big difference when it comes to whitespaces, font sizes, weights, and colors in your Starlight sidebar.
 date: 2025-04-27
 tags:
     - Starlight
diff --git a/starlight/src/content/docs/blog/starlight-topics-history-story.md b/starlight/src/content/docs/blog/starlight-topics-history-story.md
new file mode 100644
index 00000000..b2b9de08
--- /dev/null
+++ b/starlight/src/content/docs/blog/starlight-topics-history-story.md
@@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugins
+description: In this blog post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin.
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism, but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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/).
+
+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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day when HiDeoo contacts me to tell me that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~~plugin~~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
+Now you might wonder how such mature plugins could still improve over time. To be honest, I myself was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
+
+> "One could have something like the default built-in list on a desktop view, and on mobile use your component, or something like that 🧠" — HiDeoo, 21/03/2025 09:54
+
+Profound. Timeless. Golden.
+
+And that single, beautiful spark of an idea? It’s precisely what I’ll guide you through in [the post "Starlight Topics Dropdown and List together"](/blog/starlight-dropdown-and-list-together/).
diff --git a/starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx b/starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx
index 4a5ee8a9..972e0785 100644
--- a/starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx
+++ b/starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx
@@ -1,5 +1,6 @@
 ---
 title: How I Built a GitHub Profile README That Shouldn’t Exist (But It Does)
+description: A deep dive into the technical challenges and solutions behind my GitHub profile README, featuring SVG manipulation, automation, and a dynamic Bento Grid.
 date: 2025-02-05
 tags:
     - GitHub


Reviews:
user: login: coderabbitai[bot]
body: **Actionable comments posted: 5**

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between aec1d80a1a966a82b6fbc46556738c3ac57fad33 and da0b3a429689caffdc3250feace8440d4dea738e.

</details>

<details>
<summary>⛔ Files ignored due to path filters (2)</summary>

* `starlight/src/assets/covers/historytime.png` is excluded by `!**/*.png`
* `starlight/src/assets/covers/starlighttopics.png` is excluded by `!**/*.png`

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[uncategorized] ~22-~22: Did you mean “its” (the possessive pronoun)?
Context: ...hat the plugins functionalities are [in it's documentation](https://starlight-sideba...

(ITS_PREMIUM)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics get displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[formatting] ~30-~30: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ... might think that this story is now over, because everyone could just use the variant the...

(COMMA_BEFORE_BECAUSE)

---

[uncategorized] ~30-~30: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rg/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight wit...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[grammar] ~30-~30: Did you mean the possessive pronoun “its”?
Context: ...rs and pushed this new functionality to it's limits. It took them just two days to [...

(IT_S_ITS)

---

[style] ~30-~30: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ... the code to make even more use of this awesome feature.  And so comes the day, where s...

(AWESOME)

---

[typographical] ~32-~32: Consider adding a comma after this introductory expression.
Context: ...ses Starlight's new route data feature. At first I didn't quite understand what benefits...

(AT_FIRST_COMMA)

---

[style] ~36-~36: Consider a shorter alternative to avoid wordiness.
Context: ...I noticed, how little code it now took, in order to turn the `Topics.astro` list into a dro...

(IN_ORDER_TO_PREMIUM)

---

[uncategorized] ~37-~37: Possible missing comma found.
Context: ...ight-sidebar-topics-dropdown%400.5.0).  Now you might wonder how such matured plugi...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

---

[style] ~44-~44: Consider an alternative for the overused word “exactly”.
Context: ...ingle, beautiful spark of an idea? It’s exactly what I’ll guide you through in the next...

(EXACTLY_PRECISELY)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (1)</summary>

`15-15`: **Ensure draft flag is updated before publishing**  
The frontmatter has `draft: true`, which will prevent this post from appearing on the live site. Remember to change it to `false` when you’re ready to publish.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:01:36Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 8**

<details>
<summary>♻️ Duplicate comments (2)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (2)</summary><blockquote>

`18-18`: **Reduce repetitive sentence openings**  
Lines start with “It's” three times in succession; consider merging or rephrasing to improve flow and avoid monotony.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

</details>

</details>

---

`26-26`: **Remove informal apology**  
The parenthetical “sorry for the self-praise” feels conversational. Consider removing it or rephrasing more formally (e.g., “I’m proud of this implementation”).

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between da0b3a429689caffdc3250feace8440d4dea738e and 60a5665001309396cc59192040ebc9342845c673.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~24-~24: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...y days of the plugin was the way topics are displayed in the sidebar. Because it do...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

---

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[uncategorized] ~30-~30: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rg/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight wit...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[typographical] ~32-~32: Consider adding a comma after this introductory expression.
Context: ...ses Starlight's new route data feature. At first I didn't quite understand what benefits...

(AT_FIRST_COMMA)

---

[style] ~36-~36: Consider a shorter alternative to avoid wordiness.
Context: ...I noticed, how little code it now took, in order to turn the `Topics.astro` list into a dro...

(IN_ORDER_TO_PREMIUM)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

---

[style] ~44-~44: Consider an alternative for the overused word “exactly”.
Context: ...ingle, beautiful spark of an idea? It’s exactly what I’ll guide you through in the next...

(EXACTLY_PRECISELY)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (1)</summary>

`1-16`: **Verify frontmatter draft status before publishing**  
The frontmatter includes `draft: true`, which prevents the post from being published. If this post is intended to go live, please set `draft: false` or remove the `draft` field.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:06:44Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 9**

<details>
<summary>♻️ Duplicate comments (1)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (1)</summary><blockquote>

`26-26`: **Remove informal apology**  
The parenthetical “sorry for the self-praise” reads as too casual for a technical blog post. Consider removing or rephrasing to maintain a professional tone.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 60a5665001309396cc59192040ebc9342845c673 and 2d77b19c0c606fda14f53a859911fd7044d81186.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~24-~24: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...y days of the plugin was the way topics are displayed in the sidebar. Because it do...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

---

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[uncategorized] ~37-~37: Possible missing comma found.
Context: ...ight-sidebar-topics-dropdown%400.5.0).  Now you might wonder how such matured plugi...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (1)</summary>

`15-15`: **Verify draft status before publishing**  
The frontmatter flag `draft: true` will prevent this post from appearing in production. Confirm whether this post is still a work in progress or ready for publication.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:13:25Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 7**

<details>
<summary>♻️ Duplicate comments (4)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (4)</summary><blockquote>

`9-9`: **Shorten and focus the excerpt**  
The current excerpt is quite long and reiterates the post content. Consider trimming it to a concise hook, e.g.:  
> “In this post, I trace the evolution of the Starlight Sidebar Topics plugin ecosystem from its origins to today.”

---

`22-22`: _🧹 Nitpick (assertive)_

**Replace informal “imho” and tighten phrasing**  
The shorthand “imho” is too casual, and “most and best” is redundant. Consider:  
```diff
- the most and imho best plugins you can find for Starlight
+ some of the best plugins available for Starlight
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

---

`30-31`: _🧹 Nitpick (assertive)_

**Remove redundant “myself”**  
In “which I myself never saw coming,” the word “myself” is redundant. Simplify to:  
```diff
- which I myself never saw coming
+ which I never saw coming
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`36-36`: _🧹 Nitpick (assertive)_

**Rephrase “refactor” usage for professional tone**  
Consider using “refactoring” (and removing “casually”) for clarity and formality:  
```diff
- this refactor casually eliminated exactly 1210 lines of code...
+ this refactoring eliminated exactly 1,210 lines of code...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~36-~36: The verb ‘refactor’ is plural. Did you mean: “refactors”? Did you use a verb instead of a noun?
Context: ...actor my plugin into a component - this refactor casually eliminated exactly [1210 lines...

(PLURAL_VERB_AFTER_THIS)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 2d77b19c0c606fda14f53a859911fd7044d81186 and 555dfa7a4c02a097a5d960e5994620d355d11360.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[grammar] ~36-~36: The verb ‘refactor’ is plural. Did you mean: “refactors”? Did you use a verb instead of a noun?
Context: ...actor my plugin into a component - this refactor casually eliminated exactly [1210 lines...

(PLURAL_VERB_AFTER_THIS)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (1)</summary>

* GitHub Check: autofix

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (1)</summary>

`44-45`: **Verify that a practical guide accompanies this history**  
The PR title mentions adding a “guide for topics composition,” but the post currently reads as a historical narrative without actionable instructions or code examples. Should we include a section with concrete guidance on composing topics?

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:20:16Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 1**

<details>
<summary>♻️ Duplicate comments (8)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (8)</summary><blockquote>

`30-30`: **Eliminate redundant “I myself”**  
Remove “myself” for a smoother read:  
```diff
-  ... opened up so many possibilities, which I myself never saw coming.
+  ... opened up so many possibilities, which I never saw coming.
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`38-38`: **Remove redundant “myself” again**  
Simplify phrasing by dropping “myself”:  
```diff
- To be honest, I myself was very surprised when HiDeoo casually dropped a bomb...
+ To be honest, I was very surprised when HiDeoo casually dropped a bomb...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

---

`2-2`: _🧹 Nitpick (assertive)_

**Avoid parentheses in title for clarity**  
Using “plugin(s)” can be confusing—simplify to the plural form.  
```diff
-title: A short history of Starlight Sidebar Topics plugin(s)
+title: A short history of Starlight Sidebar Topics plugins
```

---

`9-9`: _🧹 Nitpick (assertive)_

**Shorten and focus the excerpt**  
The current excerpt is lengthy and generic. Consider trimming it to a single, compelling sentence that hooks the reader. For example:  
```diff
-excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+excerpt: In this post, I trace the evolution of the Starlight Sidebar Topics plugins from a simple list to a dynamic dropdown—and beyond.
```

---

`22-23`: _🧹 Nitpick (assertive)_

**Replace informal shorthand and tighten phrasing**  
The phrase “the most and imho best plugins” is both informal and awkward. Consider a more professional, concise alternative:  
```diff
- ... author of the most and imho best plugins you can find for Starlight.
+ ... author of some of the best plugins available for Starlight.
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

---

`15-15`: _🧹 Nitpick (assertive)_

**Remember to update the `draft` status before publishing**  
The frontmatter is set to `draft: true`. Don’t forget to switch this to `false` (or remove it) when the post is ready to go live.  
```diff
-draft: true
+draft: false
```

---

`24-24`: _🧹 Nitpick (assertive)_

**Combine sentences to avoid fragment**  
Starting a sentence with “Because” creates a fragment. Merge it with the previous sentence for clarity:  
```diff
- The one thing that bothered me ... in the sidebar. Because it doesn't use a dropdown menu...
+ The one thing that bothered me ... in the sidebar because it doesn't use a dropdown menu...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

</details>

</details>

---

`26-26`: _🧹 Nitpick (assertive)_

**Refine informal apology**  
“(sorry for the self-praise, I'm just proud of myself)” feels overly casual. Consider:  
```diff
-(sorry for the self-praise, I'm just proud of myself)
+(apologies for the self-praise; I'm proud of the result)
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 555dfa7a4c02a097a5d960e5994620d355d11360 and 74776460e986aa2cc15c2f049da27bf3bb03c39b.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[grammar] ~36-~36: The verb ‘refactor’ is plural. Did you mean: “refactors”? Did you use a verb instead of a noun?
Context: ...actor my plugin into a component - this refactor casually eliminated exactly [1210 lines...

(PLURAL_VERB_AFTER_THIS)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:31:38Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 2**

<details>
<summary>♻️ Duplicate comments (7)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (7)</summary><blockquote>

`2-2`: _🧹 Nitpick (assertive)_

**Simplify title by removing parentheses**  
Parentheses around “plugin(s)” can be distracting. Consider using the plural “plugins” for readability:  
```diff
- title: A short history of Starlight Sidebar Topics plugin(s)
+ title: A short history of Starlight Sidebar Topics plugins
```

---

`9-9`: _🧹 Nitpick (assertive)_

**Shorten and focus the excerpt**  
The current excerpt is lengthy and generic. Try trimming it to a concise hook, for example:  
> “A journey through the evolution of the Starlight Sidebar Topics plugin ecosystem.”

---

`25-26`: _🧹 Nitpick (assertive)_

**Rephrase apology and tighten parentheses**  
The parenthetical apology feels informal. Consider a more concise phrasing and proper comma placement:  
```diff
- (sorry for the self-praise, I'm just proud of myself)
+ (apologies for the digression; I’m proud of the result)
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

---

`29-29`: _🧹 Nitpick (assertive)_

**Split long sentence for readability**  
This sentence merges independent clauses. Break it up or reword:  
```diff
- You might think this story is over—everyone can choose the variant they want and be happy.
+ You might think this story is over. After all, everyone can choose the variant they prefer.
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`37-37`: _🧹 Nitpick (assertive)_

**Eliminate redundant “myself”**  
Simplify “I myself was very surprised” to “I was very surprised.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~37-~37: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

---

`23-24`: _🧹 Nitpick (assertive)_

**Merge the “Because” clause to avoid a fragment**  
Starting a sentence with “Because” leads to a fragment. Also, use em dashes for parentheticals. For example:  
```diff
- Because it doesn't—like I imagined a solution could look like—use some kind of dropdown menu …
+ It doesn't—contrary to my expectation—use a dropdown menu …
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~23-~23: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~23-~23: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...y days of the plugin was the way topics are displayed in the sidebar. Because it do...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

</details>

</details>

---

`21-22`: _🧹 Nitpick (assertive)_

**Clarify plugin endorsement and fix informal shorthand**  
Replace “imho” with “in my opinion” (or “IMO”) and simplify the phrasing, e.g.:  
```diff
- author of the most and imho best plugins
+ author of some of the best plugins
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 74776460e986aa2cc15c2f049da27bf3bb03c39b and b22e2570a03d358b85ffcdc768568c86edd0ae17.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~23-~23: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~23-~23: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...y days of the plugin was the way topics are displayed in the sidebar. Because it do...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

---

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[style] ~37-~37: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (2)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md (2)</summary>

`1-15`: **Frontmatter Validated**  
The YAML frontmatter (title, date, tags, authors, cover) is well-formed and uses consistent indentation.

---

`43-44`: **Engaging closing**  
The final lines are strong and engaging, effectively setting up the next post—no changes needed here.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:35:39Z
user: login: coderabbitai[bot]
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-05T18:36:31Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 7**

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between b22e2570a03d358b85ffcdc768568c86edd0ae17 and 660a9a4123b28e3e561029af0d5a650118e44dba.

</details>

<details>
<summary>⛔ Files ignored due to path filters (1)</summary>

* `starlight/src/assets/covers/dropdownorlist.png` is excluded by `!**/*.png`

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx` (1 hunks)
* `starlight/src/content/docs/blog/starlight-topics-history-story.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx</summary>

[locale-violation] ~56-~56: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...pics-dropdown ```  </TabItem>  </Tabs>  Afterwards, follow the setup guides from [Starligh...

(AFTERWARDS_US)

</details>
<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~23-~23: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[style] ~37-~37: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (3)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md (1)</summary>

`1-15`: **Frontmatter looks solid**  
YAML keys (title, date, tags, authors, cover) are correctly formatted and semantically meaningful.

</details>
<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx (2)</summary>

`1-15`: **Frontmatter is well-formed**  
Metadata (title, date, tags, authors, cover) aligns with project conventions for blog posts.

---

`17-18`: **Import usage is correct**  
You import `Tabs` and `TabItem` but only `TabItem` is used inside `<Tabs>`. If `Tabs` has wrappers or props you plan to use, keep it; otherwise, you could remove the unused import.  

Please confirm whether `Tabs` is needed here or if it can be removed to clean up the imports.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-12T06:33:47Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 5**

<details>
<summary>♻️ Duplicate comments (5)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md (5)</summary><blockquote>

`2-2`: **Simplify title by removing parentheses**  
The parentheses around “plugin(s)” feel informal. Consider using “plugins” or “plugin” to keep the title concise and formal.

---

`21-21`: **Clarify and streamline the opinion sentence**  
This sentence is wordy and unclear. You could rewrite to something like:  
> This sentiment is widely shared by the community.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

---

`25-25`: **Tone down apology language**  
The parenthetical “sorry for the self-praise” is overly casual. Consider a more formal tone or removing the apology.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

---

`29-29`: **Remove redundant “myself”**  
Redundant phrasing: you can simplify “which I myself never saw coming” to “which I never saw coming.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`37-37`: **Remove redundant “myself”**  
Redundant phrasing: simplify “I myself was very surprised” to “I was very surprised.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~37-~37: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 660a9a4123b28e3e561029af0d5a650118e44dba and 7ea53295d464e8ce25995ef6fb71beddffdd09c7.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `starlight/src/content/docs/blog/starlight-topics-history-story.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md</summary>

[uncategorized] ~17-~17: Possible missing comma found.
Context: ... Its features: Simplicity and minimalism but everything you need. Its performance: [...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~23-~23: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[uncategorized] ~36-~36: Possible missing comma found.
Context: ...ight-sidebar-topics-dropdown%400.5.0).  Now you might wonder how such mature plugin...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~37-~37: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-12T06:43:20Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 3**

<details>
<summary>♻️ Duplicate comments (2)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx (2)</summary><blockquote>

`57-57`: **Use American English variant “Afterward”**  
In the sentence “Afterwards, follow the setup guides…”, prefer “Afterward” to align with the style guide.

---

`71-77`: **Enhance semantic accessibility by using `<nav>`**  
Replace the bare `<div>` wrappers with `<nav aria-label="Topics">` to improve semantics and screen-reader support. For example:  
```astro
<nav aria-label="Topics" class="topics">
  <Topics/>
</nav>
```  
And similarly for the `.topics-dropdown` container.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 7ea53295d464e8ce25995ef6fb71beddffdd09c7 and 3382714d7e769e2608dfac0f096e4c671be46beb.

</details>

<details>
<summary>⛔ Files ignored due to path filters (2)</summary>

* `pnpm-lock.yaml` is excluded by `!**/pnpm-lock.yaml`
* `starlight/src/assets/dropdown-or-list.png` is excluded by `!**/*.png`

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `starlight/package.json` (1 hunks)
* `starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx</summary>

[locale-violation] ~56-~56: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...pics-dropdown ```  </TabItem>  </Tabs>  Afterwards, follow the setup guides from [Starligh...

(AFTERWARDS_US)

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (4)</summary>

* GitHub Check: Redirect rules - trueberryless-blog
* GitHub Check: Header rules - trueberryless-blog
* GitHub Check: autofix
* GitHub Check: Pages changed - trueberryless-blog

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>starlight/package.json (1)</summary>

`25-25`: **Verify compatibility of the `starlight-blog` dependency bump**  
The version has been updated from `^0.21.0` to `^0.23.2`. Please confirm there are no breaking changes in the new `starlight-blog` release that could affect rendering of the newly added posts or other parts of the site.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-14T19:04:59Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 5**

<details>
<summary>♻️ Duplicate comments (5)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md (4)</summary><blockquote>

`22-22`: **Streamline and clarify community sentiment**  
The phrase “And I'm not alone with this subjectively general accepted opinion” is wordy and somewhat unclear. Consider rewriting to something like:  
> “This sentiment is widely shared by the community.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

---

`26-26`: **Tone down apology language**  
The parenthetical “(sorry for the self-praise, I'm just proud of myself)” is overly casual. You could replace it with a more formal phrasing or remove the apology:  
```diff
- …pure HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myself)
+ …pure HTML + CSS but also clean to look at — pardon the self-praise.
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

---

`30-30`: **Remove redundant “myself”**  
In “which I myself never saw coming,” the word “myself” is unnecessary. Consider:  
> “which I never saw coming.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`38-38`: **Remove redundant “myself”**  
Similarly, “I myself was very surprised” can be simplified to:  
> “I was very surprised.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</blockquote></details>
<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx (1)</summary><blockquote>

`58-58`: **Use American English “Afterward”**  
Line begins with “Afterwards, follow the setup guides…”. In American English, prefer “Afterward, follow the setup guides…”.

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 3382714d7e769e2608dfac0f096e4c671be46beb and d67f2950e6010ce4ea7877d20f07f631622a5e8d.

</details>

<details>
<summary>📒 Files selected for processing (7)</summary>

* `starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md` (1 hunks)
* `starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md` (1 hunks)
* `starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md` (1 hunks)
* `starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx` (1 hunks)
* `starlight/src/content/docs/blog/starlight-sidebar-whitespace.md` (1 hunks)
* `starlight/src/content/docs/blog/starlight-topics-history-story.md` (1 hunks)
* `starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics were displayed in the si...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>
<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx</summary>

[locale-violation] ~57-~57: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...pics-dropdown ```  </TabItem>  </Tabs>  Afterwards, follow the setup guides from [Starligh...

(AFTERWARDS_US)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (4)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md (1)</summary>

`1-16`: **Frontmatter schema and metadata look good**  
All required fields (title, description, date, tags, excerpt, authors, cover) are present and correctly formatted.

</details>
<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx (3)</summary>

`1-16`: **Frontmatter metadata is well-structured**  
The title, description, date, tags, excerpt, authors, and cover fields are present and valid.

---

`72-78`: **Improve accessibility semantics**  
Replace the bare `<div>` wrappers with a `<nav aria-label="Topics">` to convey semantics, and add `aria-hidden="true"` to hidden containers so screen readers skip them:  
```diff
-<div class="topics">
+<nav class="topics" aria-label="Topics">
   <Topics/>
-</div>
+</nav>
```  
[ suggest_optional_refactor]

---

`86-102`: **Extract magic number into a CSS variable**  
Define the `800px` breakpoint as a custom property for maintainability and consistency:  
```css
:root {
  --sidebar-breakpoint: 800px;
}
@media (min-width: var(--sidebar-breakpoint)) {
  /* … */
}
```  
[ suggest_optional_refactor]

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-15T15:43:57Z
user: login: coderabbitai[bot]
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-15T15:48:51Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 2**

<details>
<summary>♻️ Duplicate comments (4)</summary><blockquote>

<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md (4)</summary><blockquote>

`26-26`: **Tone down apology language**  
The parenthetical “sorry for the self-praise” may feel overly casual. You could replace with a more formal alternative such as “pardon the self-praise” or remove it altogether to maintain a neutral tone.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

---

`30-30`: **Remove redundant “I myself”**  
For conciseness, consider simplifying to “I never saw coming.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

---

`38-38`: **Remove redundant “I myself”**  
The phrase “I myself was very surprised” can be streamlined to “I was very surprised.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

---

`24-24`: _🧹 Nitpick (assertive)_

**Maintain past-tense consistency**  
The narrative is set in the past, so adjust “are displayed” to “were displayed.”  
```diff
- topics are displayed in the sidebar
+ topics were displayed in the sidebar
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics were displayed in the si...

(SUBJECTVERBAGREEMENT_2)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: ASSERTIVE**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between b37b671883594805fbfab1e9be9bd997d6a8efc8 and fa986c9acd5012646100fce413becd96aba675e9.

</details>

<details>
<summary>⛔ Files ignored due to path filters (1)</summary>

* `starlight/src/assets/covers/dropdownandlist.png` is excluded by `!**/*.png`

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx` (1 hunks)
* `starlight/src/content/docs/blog/starlight-topics-history-story.md` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx</summary>

[locale-violation] ~57-~57: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...pics-dropdown ```  </TabItem>  </Tabs>  Afterwards, follow the setup guides from [Starligh...

(AFTERWARDS_US)

</details>
<details>
<summary>starlight/src/content/docs/blog/starlight-topics-history-story.md</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics were displayed in the si...

(SUBJECTVERBAGREEMENT_2)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: CHANGES_REQUESTED
author_association: CONTRIBUTOR
submitted_at: 2025-05-15T15:54:15Z
user: login: coderabbitai[bot]
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-15T15:56:26Z

Review comments:
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in it's documentation](https://starlight-sidebar-topics.netlify.app/).
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Fix possessive pronoun in link text**  
Change “in it's documentation” to “in its documentation” to use the correct possessive pronoun.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

---

[uncategorized] ~22-~22: Did you mean “its” (the possessive pronoun)?
Context: ...hat the plugins functionalities are [in it's documentation](https://starlight-sideba...

(ITS_PREMIUM)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 60a5665
created_at: 2025-05-05T18:01:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in it's documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics get 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.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Correct verb agreement**  
Replace “the way topics get displayed in the sidebar” with “the way topics are displayed in the sidebar” for proper subject–verb agreement.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics get displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 60a5665
created_at: 2025-05-05T18:01:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in it's documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics get 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over, because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to it's limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this awesome feature.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Tighten phrasing and fix typos**  
1. Remove the comma before “because” if the clause is essential.  
2. Change “to it's limits” to “to its limits” (correct possessive).  
3. Consider replacing “awesome” with a more descriptive adjective (e.g., “powerful” or “valuable”).

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[formatting] ~30-~30: If the ‘because’ clause is essential to the meaning, do not use a comma before the clause.
Context: ... might think that this story is now over, because everyone could just use the variant the...

(COMMA_BEFORE_BECAUSE)

---

[uncategorized] ~30-~30: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rg/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight wit...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

---

[grammar] ~30-~30: Did you mean the possessive pronoun “its”?
Context: ...rs and pushed this new functionality to it's limits. It took them just two days to [...

(IT_S_ITS)

---

[style] ~30-~30: Consider using a more formal and expressive alternative to ‘awesome’.
Context: ... the code to make even more use of this awesome feature.  And so comes the day, where s...

(AWESOME)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 60a5665
created_at: 2025-05-05T18:01:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Eliminate redundant “I myself”**  
Simplify “which I myself never saw coming” to “which I never saw coming” for conciseness.

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:06:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - which casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took, in order to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
+Now you might wonder how such matured plugins could still improve over time. To be honest, I myself was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
+
+> "One could have something like the default built-in list on a desktop view, and on mobile use your component, or something like that 🧠" — HiDeoo, 21/03/2025 09:54
+
+Profound. Timeless. Golden.
+
+And that single, beautiful spark of an idea? It’s exactly what I’ll guide you through in the next post — coming soon. Stay tuned!
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Replace overused “exactly”**  
Consider using a more precise alternative (e.g., “precisely” or “truly”) to strengthen the language.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~44-~44: Consider an alternative for the overused word “exactly”.
Context: ...ingle, beautiful spark of an idea? It’s exactly what I’ll guide you through in the next...

(EXACTLY_PRECISELY)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 2d77b19
created_at: 2025-05-05T18:06:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - which casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took, in order to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Simplify wording and punctuation**  
Remove the comma before “in order to” and consider replacing “in order to” with “to” for brevity. For example:  
“…noticed how little code it now took to turn the `Topics.astro` list into a dropdown…”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~36-~36: Consider a shorter alternative to avoid wordiness.
Context: ...I noticed, how little code it now took, in order to turn the `Topics.astro` list into a dro...

(IN_ORDER_TO_PREMIUM)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 2d77b19
created_at: 2025-05-05T18:06:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add comma after introductory phrase**  
Insert a comma after “At first” (i.e., “At first, I didn’t quite understand…”) to follow conventional punctuation.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[typographical] ~32-~32: Consider adding a comma after this introductory expression.
Context: ...ses Starlight's new route data feature. At first I didn't quite understand what benefits...

(AT_FIRST_COMMA)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 2d77b19
created_at: 2025-05-05T18:06:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Hyphenate compound adjective “long-awaited”**  
Use “long-awaited addition” instead of “long awaited addition” to follow standard hyphenation rules.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~30-~30: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...rg/work/20th-birthday/) for me, was the long awaited addition of route data in Starlight wit...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 2d77b19
created_at: 2025-05-05T18:06:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use “Adaptation” instead of “Adaption”**  
The heading “The Adaption” would be more conventional as “The Adaptation”.

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 555dfa7
created_at: 2025-05-05T18:13:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Replace informal shorthand and tighten phrasing**  
Change “imho” to “in my opinion” (or “IMO”) and simplify “the most and in my opinion best plugins” to something like “some of the best plugins” for clarity and professional tone.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Shorten and focus the excerpt**  
The current excerpt is very long and generic. Consider trimming it to a single concise sentence that hooks the reader, e.g.:  
“In this post, I trace the evolution of the Starlight Sidebar Topics plugin ecosystem from its origins to today.”

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add comma after introductory phrase**  
Insert a comma after “At first” in “At first I didn’t quite understand…” to follow conventional punctuation.

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - which casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
+Now you might wonder how such matured plugins could still improve over time. To be honest, I myself was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Replace “matured plugins” with “mature plugins”**  
The term “matured plugins” is uncommon; “mature plugins” reads more naturally.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 555dfa7
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaption
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - which casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Refine phrasing around code removal**  
“It casually eliminated exactly 1210 lines” is vague—consider specifying the action clearly, e.g., “this refactor eliminated 1,210 lines of code”. Removing “casually” sharpens the statement.

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Fix sentence fragment and dash usage**  
Avoid starting a sentence with “Because”. Also consider using em dashes elegantly:  
- Merge the “Because it doesn’t …” clause into the previous sentence.  
- Replace hyphens (`-`) with em dashes (`—`) for parenthetical emphasis.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~24-~24: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

---

[uncategorized] ~24-~24: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...y days of the plugin was the way topics are displayed in the sidebar. Because it do...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:13:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Remember to update `draft` status before publishing**  
Frontmatter is set to `draft: true`. Don’t forget to switch this to `false` (or remove it) once the post is ready to go live.

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit b22e257
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Avoid parentheses in title for clarity**  
The title “A short history of Starlight Sidebar Topics plugin(s)” uses parentheses around the plural “plugin(s)”. Consider simplifying to “plugins” to improve readability—for example:  
```markdown
title: A short history of Starlight Sidebar Topics plugins
```

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactor casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
+Now you might wonder how such mature plugins could still improve over time. To be honest, I myself was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Remove redundant “myself”**  
In “I myself was very surprised,” remove “myself” to improve flow:  
```diff
- To be honest, I myself was very surprised...
+ To be honest, I was very surprised...
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
Now you might wonder how such mature plugins could still improve over time. To be honest, I was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~38-~38: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... still improve over time. To be honest, I myself was very surprised when HiDeoo casually...

(I_MYSELF)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Clean up comma usage around “that”**  
The comma before “that” is unnecessary, and “where” after “day” can be smoothed out. For example:  
```diff
- And so comes the day, where suddenly HiDeoo contacts me to tell me, that the Starlight...
+ And so comes the day when HiDeoo contacts me to tell me that the Starlight...
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
And so comes the day when HiDeoo contacts me to tell me that the Starlight...
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->

✅ Addressed in commit 7477646
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add comma before nonrestrictive clause & rephrase apology**  
A comma is needed before “which” in a nonrestrictive clause, and the parenthetical apology feels informal. For clarity and tone:  
```diff
- adapt the `Topics.astro` component which includes the HTML for rendering the topics...
+ adapt the `Topics.astro` component, which includes the HTML for rendering the topics...
- (sorry for the self-praise, I'm just proud of myself)
+ (apologies for the self-praise; I’m proud of the result)
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
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 (apologies for the self-praise; I’m proud of the result), 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.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~26-~26: Possible missing comma found.
Context: ...nd just had to adapt the `Topics.astro` component which includes the HTML for rendering t...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~26-~26: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use correct possessive and vary sentence openings**  
Sentences starting with “It’s features”, “It’s performance”, and “It’s accessibility” should use the possessive “Its” and avoid repeating “It’s” at the start of each clause. For example:  
```diff
- It's features: Simplicity and minimalism but everything you need.
+ Its features combine simplicity and minimalism with everything you need.
- It's performance: Faster than 98% of other websites out there.
+ Its performance outstrips 98% of other websites.
- It's accessibility: Not even a question!
+ Its accessibility is top-tier.
```  



> Committable suggestion skipped: line range outside the PR's diff.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~18-~18: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...tarlight-astro-build-getting-started/). It's accessibility: Not even a question!  ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. It's features: Simplicity and minimalism but everything you need. It's performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). It's accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Split long sentence and clarify structure**  
This sentence merges multiple independent clauses. Consider breaking it up or using an em dash for clarity:  
```diff
- You might think that this story is now over because everyone could just use the variant they want, everyone is happy.
+ You might think this story is over—everyone can choose the variant they want and be happy.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
You might think this story is over—everyone can choose the variant they want and be happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~30-~30: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:20:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+draft: true
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day when HiDeoo contacts me to tell me that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactor casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use “refactoring” instead of “refactor”**  
Change the noun for grammatical correctness and add comma separation for large numbers:  
```diff
-  ...this refactor casually eliminated exactly [1210 lines of code and added 68 lines of changelog]...
+  ...this refactoring casually eliminated exactly 1,210 lines of code and added 68 lines of changelog...
```  



> Committable suggestion skipped: line range outside the PR's diff.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~36-~36: The verb ‘refactor’ is plural. Did you mean: “refactors”? Did you use a verb instead of a noun?
Context: ...actor my plugin into a component - this refactor casually eliminated exactly [1210 lines...

(PLURAL_VERB_AFTER_THIS)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:31:37Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Refine introductory praise for formality**  
Phrases like “cool documentation framework” and contractions (“I’m”) can be softened for a more professional tone. Consider:  
```diff
- Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly.
+ You may already be familiar with this documentation framework. I discuss it frequently and rely on it in my projects.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
You may already be familiar with this documentation framework. I discuss it frequently and rely on it in my projects. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:35:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day when HiDeoo contacts me to tell me that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
path: starlight/src/content/docs/blog/starlight-sidebar-topics-composition.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Remove unnecessary comma after “noticed”**  
The comma in “and I noticed, how little code…” is unnecessary. Use:  
```diff
- and I noticed, how little code it now took
+ and I noticed how little code it now took
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-05T18:35:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Tone down apology language**  
The parenthetical “sorry for the self-praise” is overly casual. You could replace with a more formal tone such as “pardon the self-praise” or remove the apology altogether.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~25-~25: “Sorry” is a very overused expression. Consider replacing it with a more formal alternative.
Context: ...e HTML + CSS but also clean to look at (sorry for the self-praise, I'm just proud of myse...

(APOLOGIZE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Clarify and streamline the second sentence**  
The phrase “And I'm not alone with this subjectively general accepted opinion” is wordy and a bit unclear. Consider rewriting to something like:  
- “This sentiment is widely shared by the community.”

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Consider removing parentheses around “plugin(s)”**  
The title `A short history of Starlight Sidebar Topics plugin(s)` is clear, but the `(s)` may feel informal. You could title it `A short history of Starlight Sidebar Topics plugins` or `plugin` depending on focus.

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Remove redundant “I myself”**  
Phrases like “which I myself never saw coming” and “I myself was very surprised” can be simplified to “which I never saw coming” and “I was very surprised.”  



Also applies to: 37-37

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~29-~29: This phrase is often redundant. Consider writing “I” unless you want to emphasize that you and not someone else will do something.
Context: ... opened up so many possibilities, which I myself never saw coming. HiDeoo once again was...

(I_MYSELF)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,110 @@
+---
+title: Dropdown on mobile, List on desktop
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to create different displays on mobile and desktop.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownorlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Add the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
+
+## Modify the Sidebar component
+
+In the setup guide from the dropdown component, you have created a sidebar component, which only renders the dropdown menu. Now, you need to modify this component to also render the default sidebar if the user is on desktop.
+
+```astro
+---
+// src/components/Sidebar.astro
+import Default from '@astrojs/starlight/components/Sidebar.astro';
+import Topics from 'starlight-sidebar-topics/components/Sidebar.astro';
+import TopicsDropdown from 'starlight-sidebar-topics-dropdown/TopicsDropdown.astro';
+---
+
+<div class="topics">
+  <Topics/>
+</div>
+<div class="topics-dropdown">
+  <TopicsDropdown/>
+</div>
+<Default><slot /></Default>
+
+<style>
+  /* Hide topics by default and show them on medium screens and larger */
+  .topics {
+    display: none;
+  }
+
+  @media (min-width: 800px) {
+    .topics {
+      display: block;
+    }
+  }
+
+  /* Show topics dropdown on small screens and hide it on medium screens and larger */
+  .topics-dropdown {
+    display: block;
+  }
+
+  @media (min-width: 800px) {
+    .topics-dropdown {
+      display: none;
+    }
+  }
+</style>
+```
path: starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Enhance accessibility and maintainability of the Sidebar snippet**  
- Wrap topic lists in a `<nav aria-label="Topics">` instead of a bare `<div>` to improve semantics.  
- When hiding elements via `display: none`, add `aria-hidden` on the hidden container so screen readers skip it.  
- Consider extracting the `800px` breakpoint into a CSS variable or theme token to avoid “magic numbers.”

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,110 @@
+---
+title: Dropdown on mobile, List on desktop
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to create different displays on mobile and desktop.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownorlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Add the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
path: starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use American English variant “Afterward”**  
Line 57 reads “Afterwards, follow the setup guides…”. In American English, prefer “Afterward, follow the setup guides…”.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[locale-violation] ~56-~56: In American English, ‘afterward’ is the preferred variant. ‘Afterwards’ is more commonly used in British English and other dialects.
Context: ...pics-dropdown ```  </TabItem>  </Tabs>  Afterwards, follow the setup guides from [Starligh...

(AFTERWARDS_US)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:33:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day when HiDeoo contacts me to tell me that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
+
+Now you might wonder how such mature plugins could still improve over time. To be honest, I myself was very surprised when HiDeoo casually dropped a bomb in my Discord DMs. His idea was and still is ingenious. Otherwise, I wouldn't even think about this _topic_ anymore. But here I am, writing a whopping 800 words just to prepare you for what's to come. Drum roll please! Fasten your seatbelt! This statement from HiDeoo is going to blow your mind:
+
+> "One could have something like the default built-in list on a desktop view, and on mobile use your component, or something like that 🧠" — HiDeoo, 21/03/2025 09:54
+
+Profound. Timeless. Golden.
+
+And that single, beautiful spark of an idea? It’s precisely what I’ll guide you through in [the post "Dropdown on mobile, List on desktop"](/blog/starlight-topics-history-story/).
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _⚠️ Potential issue_

**Fix link to the “Dropdown on mobile, List on desktop” post**  
The current link points to this same post. It should reference the guide post `starlight-dropdown-or-list`. For example:  
```diff
-And that single, beautiful spark of an idea? It’s precisely what I’ll guide you through in [the post "Dropdown on mobile, List on desktop"](/blog/starlight-topics-history-story/).
+And that single, beautiful spark of an idea? It’s precisely what I’ll guide you through in [the post "Dropdown on mobile, List on desktop"](/blog/starlight-dropdown-or-list/).
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
And that single, beautiful spark of an idea? It’s precisely what I’ll guide you through in [the post "Dropdown on mobile, List on desktop"](/blog/starlight-dropdown-or-list/).
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:43:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
+
+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.
+
+## The Adaptation
+
+You might think that this story is now over because everyone could just use the variant they want, everyone is happy. But Starlight kept and keeps improving and around three months later, on the 15th of February, coming almost as a [birthday present](https://trueberryless.org/work/20th-birthday/) for me, was the long-awaited addition of route data in Starlight with the release of [v0.32](https://github.com/withastro/starlight/releases/tag/@astrojs/starlight@0.32.0). This seemingly small addition opened up so many possibilities, which I myself never saw coming. HiDeoo once again was the leading inspiration for plugin authors and pushed this new functionality to its limits. It took them just two days to [adapt over 11 plugins to the latest Starlight version back then](https://bsky.app/profile/hideoo.dev/post/3liffpudc5c2b) and they later improved and refactored much of the code to make even more use of this powerful feature.
+
+And so comes the day when HiDeoo contacts me to tell me that the Starlight Sidebar Topics plugin now uses Starlight's new route data feature. At first, I didn't quite understand what benefits these implementation changes would have, but then HiDeoo took the time to explain to me that I could now turn the Starlight Sidebar Topics Dropdown plugin into a simple component which uses the route data from his plugin. Intuitively, I was opposed to this smart idea because it felt like my only plugin that made some popularity was turned into some useless component. I couldn't have been further from the truth.
+
+## The Union
+
+Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~plugin~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Correct Markdown strikethrough syntax**  
Use double tildes for strikethrough instead of single:  
```diff
-... right direction for the ~plugin~ component.
+... right direction for the ~~plugin~~ component.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
Eventually, I decided to refactor my plugin into a component - this refactoring casually eliminated exactly [1210 lines of code and added 68 lines of changelog](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/pull/40) - and I noticed, how little code it now took to turn the `Topics.astro` list into a dropdown from a user's perspective. I was confident that this really was the right direction for the ~~plugin~~ component. And so I updated the whole documentation - more like: deleted more than 200 lines of text (feels good) - and released the new [version 0.5](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown/releases/tag/starlight-sidebar-topics-dropdown%400.5.0).
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:43:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Fix possessive form for “plugin’s functionalities”**  
Correct the possessive form to improve grammar:  
```diff
-Read more about what the plugins functionalities are [in its documentation]
+Read more about the plugin’s functionalities in [its documentation]
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
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://hideoo.dev) 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/).
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~21-~21: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:43:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add missing comma for clarity**  
Consider adding a comma after “minimalism” to improve readability:  
```diff
-Its features: Simplicity and minimalism but everything you need.
+Its features: Simplicity and minimalism, but everything you need.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism, but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~17-~17: Possible missing comma found.
Context: ... Its features: Simplicity and minimalism but everything you need. Its performance: [...

(AI_HYDRA_LEO_MISSING_COMMA)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:43:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,43 @@
+---
+title: A short history of Starlight Sidebar Topics plugin(s)
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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 what the plugins functionalities are [in its documentation](https://starlight-sidebar-topics.netlify.app/).
+
+The one thing that bothered me personally in the early days of the plugin was the way topics are 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.
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Consistent past tense for “topics were displayed”**  
Use past tense to match “bothered me personally in the early days”:  
```diff
-The one thing that bothered me personally in the early days of the plugin was the way topics are displayed in the sidebar.
+The one thing that bothered me personally in the early days of the plugin was the way topics were displayed in the sidebar.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
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.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~23-~23: Did you mean “were”?
Context: ...sonally in the early days of the plugin was the way topics are displayed in the sid...

(SUBJECTVERBAGREEMENT_2)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-12T06:43:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,116 @@
+---
+title: Starlight Topics Dropdown and List together
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to show a list of topics on desktop and a dropdown menu in the mobile sidebar.
path: starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Consider adding a `description` field for SEO and social previews**  
While `excerpt` is used for listing pages, a dedicated `description` in the frontmatter helps search engines and link unfurls. For example:  
```yaml
description: "Learn how to combine a desktop list and mobile dropdown for your Starlight sidebar topics."
```

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-14T19:04:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,116 @@
+---
+title: Starlight Topics Dropdown and List together
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to show a list of topics on desktop and a dropdown menu in the mobile sidebar.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownorlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Add the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
+
+## Modify the Sidebar component
+
+In the setup guide from the dropdown component, you have created a sidebar component, which only renders the dropdown menu. Now, you need to modify this component to also render the default sidebar if the user is on desktop.
+
+```astro
+---
+// src/components/Sidebar.astro
+import Default from '@astrojs/starlight/components/Sidebar.astro';
+import Topics from 'starlight-sidebar-topics/components/Sidebar.astro';
+import TopicsDropdown from 'starlight-sidebar-topics-dropdown/TopicsDropdown.astro';
+---
+
+<div class="topics">
+  <Topics/>
+</div>
+<div class="topics-dropdown">
+  <TopicsDropdown/>
+</div>
+<Default><slot /></Default>
+
+<style>
+  /* Hide topics by default and show them on medium screens and larger */
+  .topics {
+    display: none;
+  }
+
+  @media (min-width: 800px) {
+    .topics {
+      display: block;
+    }
+  }
+
+  /* Show topics dropdown on small screens and hide it on medium screens and larger */
+  .topics-dropdown {
+    display: block;
+  }
+
+  @media (min-width: 800px) {
+    .topics-dropdown {
+      display: none;
+    }
+  }
+</style>
path: starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Extract the hardcoded `800px` breakpoint into a CSS variable**  
Defining a custom property (e.g. `--sidebar-breakpoint`) increases maintainability and consistency:  
```css
:root {
  --sidebar-breakpoint: 800px;
}
@media (min-width: var(--sidebar-breakpoint)) {
  /* … */
}
```

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-14T19:04:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,116 @@
+---
+title: Starlight Topics Dropdown and List together
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to show a list of topics on desktop and a dropdown menu in the mobile sidebar.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownorlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Add the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
+
+## Modify the Sidebar component
+
+In the setup guide from the dropdown component, you have created a sidebar component, which only renders the dropdown menu. Now, you need to modify this component to also render the default sidebar if the user is on desktop.
+
+```astro
+---
+// src/components/Sidebar.astro
path: starlight/src/content/docs/blog/starlight-dropdown-or-list.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use YAML comments in Astro frontmatter**  
Inside the `---` frontmatter block, comments should follow YAML syntax (`#`) instead of JavaScript (`//`).  
```diff
- ---
- // src/components/Sidebar.astro
+ ---
+ # src/components/Sidebar.astro
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
---
# src/components/Sidebar.astro
```

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-14T19:04:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,5 +1,6 @@
 ---
 title: Setting up Continuous deployment in a GitHub repository
+descrption: Today we'll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD.
path: starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Fix typo in frontmatter key**  
The frontmatter field `descrption` is misspelled and should be `description` to align with other posts and ensure the metadata is correctly parsed.  


```diff
- descrption: Today we'll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD.
+ description: Today we'll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD.
```


<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
description: Today we'll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD.
```

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In
starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md
at line 3, correct the typo in the frontmatter key by changing `descrption` to
`description` to ensure consistent metadata parsing across posts.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:43:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,5 +1,6 @@
 ---
 title: Setting up Kubernetes with Cilium and Cloudflare
+description: Today we'll take a look at how to set up a kubernetes cluster with k3s and cilium.
path: starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Capitalize proper nouns in the description**  
The frontmatter description should mirror the title’s casing for consistency and correct branding. For example:
```diff
- description: Today we'll take a look at how to set up a kubernetes cluster with k3s and cilium.
+ description: Today we'll take a look at how to set up a Kubernetes cluster with K3s and Cilium.
```




<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
description: Today we'll take a look at how to set up a Kubernetes cluster with K3s and Cilium.
```

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In
starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md
at line 3, the description in the frontmatter uses lowercase for proper nouns
like "kubernetes," "k3s," and "cilium." Update the description to capitalize
these proper nouns to match the title casing and maintain consistency and
correct branding.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:43:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,5 +1,6 @@
 ---
 title: Setting up Argo CD in a k3s cluster
+description: Today we'll take a look at how to set up Argo CD in a k3s cluster.
path: starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Quote the description to prevent YAML parsing issues.**

The unquoted `description:` value contains an apostrophe (`'`) which can lead to YAML parsing errors in some tooling. Wrap the description in double quotes to ensure it's treated as a single scalar and to align with the frontmatter style of other posts. 

Proposed diff:
```diff
- description: Today we'll take a look at how to set up Argo CD in a k3s cluster.
+ description: "Today we'll take a look at how to set up Argo CD in a k3s cluster."
```


<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
description: "Today we'll take a look at how to set up Argo CD in a k3s cluster."
```

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md at line 3, the
description field contains an unquoted string with an apostrophe, which can
cause YAML parsing errors. Fix this by wrapping the entire description value in
double quotes to ensure proper parsing and consistency with other frontmatter
entries.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:43:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,5 +1,6 @@
 ---
 title: How to make your Starlight sidebar items look better
+description: In this blog post, we'll take a look at how small changes can make a big difference when it comes to whitespaces, font sizes, weights and colors in your Starlight sidebar.
path: starlight/src/content/docs/blog/starlight-sidebar-whitespace.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add and refine metadata description**  
The new `description` frontmatter enhances SEO and discoverability. As a nitpick, consider adding an Oxford comma (“weights, and colors”) to match style conventions used in other posts:

```diff
-description: In this blog post, we'll take a look at how small changes can make a big difference when it comes to whitespaces, font sizes, weights and colors in your Starlight sidebar.
+description: In this blog post, we'll take a look at how small changes can make a big difference when it comes to whitespaces, font sizes, weights, and colors in your Starlight sidebar.
```

Also, verify that the `excerpt` field remains complementary and accurately reflects the full scope of this post’s customizations.  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
description: In this blog post, we'll take a look at how small changes can make a big difference when it comes to whitespaces, font sizes, weights, and colors in your Starlight sidebar.
```

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In starlight/src/content/docs/blog/starlight-sidebar-whitespace.md at line 3,
update the description frontmatter by adding an Oxford comma after "weights" so
it reads "weights, and colors" to maintain consistency with style conventions.
Additionally, review the excerpt field to ensure it complements the updated
description and accurately summarizes the post's content.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:43:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -1,5 +1,6 @@
 ---
 title: How I Built a GitHub Profile README That Shouldn’t Exist (But It Does)
+description: A deep dive into the technical challenges and solutions behind my GitHub profile README, featuring SVG manipulation, automation, and a dynamic Bento Grid.
path: starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Add concise metadata for SEO and maintain consistent frontmatter style**

The new `description` field provides a clear summary for search engines and social previews, matching the pattern applied across other posts in this PR. To ensure uniformity, verify that all blog entries follow the same frontmatter key order (e.g., `title`, `description`, `date`, `tags`, `excerpt`, etc.) and stay within recommended character limits (≈150–160 chars).

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In
starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx
at line 3, add a concise description field in the frontmatter that summarizes
the post for SEO and social previews. Ensure the frontmatter keys follow the
consistent order used in other blog posts, such as title, description, date,
tags, excerpt, and keep the description length within 150-160 characters for
optimal SEO.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:43:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,44 @@
+---
+title: A short history of Starlight Sidebar Topics plugins
+description: In this blog post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin.
+date: 2025-05-05
+tags:
+    - Starlight
+    - Evolution
+    - Topics
+    - Plugins
+excerpt: In this post, I'll show you the evolution of Starlight plugins with a case study of the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin. Be prepared to find out some impressive facts about people and code around Starlight.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "History Time"
+  image: ../../../assets/covers/historytime.png
+---
+
+Maybe you have heard about this cool documentation framework before. I talk about it quite often and use it regularly. Not only because I'm an active contributor, but also because [Starlight](https://starlight.astro.build) just grew to my heart. Its features: Simplicity and minimalism, but everything you need. Its performance: [Faster than 98% of other websites out there](https://www.websitecarbon.com/website/starlight-astro-build-getting-started/). Its accessibility: Not even a question!
+
+## The Creation
+
+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://hideoo.dev) 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/).
+
path: starlight/src/content/docs/blog/starlight-topics-history-story.md
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Clarify “imho” phrase for formal tone**  
The abbreviation “imho” is informal and the article usage is unclear. Consider rephrasing for clarity and tone.  
```diff
- author of the most and imho best plugins
+ author of some of the best plugins (in my opinion)
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
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://hideoo.dev) is not only one of the most active maintainers of the project, but also the author of some of the best plugins (in my opinion) 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/).
```

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[grammar] ~22-~22: A determiner may be missing.
Context: ...ct, but also the author of the most and imho best plugins you can find for Starlight. And...

(THE_SUPERLATIVE)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In starlight/src/content/docs/blog/starlight-topics-history-story.md around
lines 22 to 23, replace the informal abbreviation "imho" with a clear and formal
phrase such as "in my opinion" or "arguably" to improve tone and clarity. Also,
ensure the article usage before the phrase is grammatically correct and
consistent with the new wording.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:54:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,117 @@
+---
+title: Starlight Topics Dropdown and List together
+description: Learn how to combine a desktop list and mobile dropdown for your Starlight sidebar topics.
+date: 2025-05-13
+tags:
+    - Starlight
+    - Composition
+    - Topics
+    - Plugins
+excerpt: Combine two Starlight Sidebar Topics plugins to show a list of topics on desktop and a dropdown menu in the mobile sidebar.
+authors:
+    - trueberryless
+cover:
+  alt: A beautiful cover image with the text "Dropdown or List?"
+  image: ../../../assets/covers/dropdownandlist.png
+---
+
+import { Tabs, TabItem } from "@astrojs/starlight/components";
+
+Using the [Starlight Sidebar Topics](https://github.com/hideoo/starlight-sidebar-topics) plugin together with the [Starlight Sidebar Topics Dropdown](https://github.com/trueberryless-org/starlight-sidebar-topics-dropdown) component, you can create a website that has a list of topics on desktop and a dropdown menu on mobile.
+
+## Prerequisites
+
+You will need to have an existing Starlight website.
+
+## Install the packages
+
+First, install the `starlight-sidebar-topics` plugin and also the `starlight-sidebar-topics-dropdown` component:
+
+<Tabs syncKey="pkg">
+
+<TabItem label="npm">
+
+```sh
+npm install starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="pnpm">
+
+```sh
+pnpm add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+<TabItem label="Yarn">
+
+```sh
+yarn add starlight-sidebar-topics starlight-sidebar-topics-dropdown
+```
+
+</TabItem>
+
+</Tabs>
+
+Afterwards, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
path: starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx
user: login: coderabbitai[bot]
body: _🧹 Nitpick (assertive)_

**Use American English spelling**  
Consider replacing “Afterwards” with the preferred American variant “Afterward” for consistency.  
```diff
- Afterwards, follow the setup guides from [...]
+ Afterward, follow the setup guides from [...]
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

```suggestion
Afterward, follow the setup guides from [Starlight Sidebar Topics](https://starlight-sidebar-topics.netlify.app/docs/getting-started/#installation) and [Starlight Sidebar Topics Dropdown](https://starlight-sidebar-topics-dropdown.trueberryless.org/docs/getting-started/#installation).
```

</details>

<!-- suggestion_end -->

<details>
<summary>🤖 Prompt for AI Agents</summary>

```
In starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx at
line 58, replace the word "Afterwards" with the American English spelling
"Afterward" to maintain consistent language style throughout the document.
```

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-05-15T15:54:15Z
author_association: CONTRIBUTOR

PR comments:
user: login: changeset-bot[bot]
created_at: 2025-05-05T18:00:00Z
body: ###  ⚠️  No Changeset found

Latest commit: fa986c9acd5012646100fce413becd96aba675e9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. **If these changes should result in a version bump, you need to add a changeset.**



[Click here to learn what changesets are, and how to add one](https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md).

[Click here if you're a maintainer who wants to add a changeset to this PR](https://github.com/trueberryless-org/blog/new/topics-double?filename=.changeset/gold-bees-rush.md&value=---%0A%22%40fake-scope%2Ffake-pkg%22%3A%20patch%0A---%0A%0Afeat%3A%20add%20story%20and%20guide%20for%20topics%20composition%0A)


author_association: NONE
user: login: coderabbitai[bot]
created_at: 2025-05-05T18:00:03Z
body: <!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- walkthrough_start -->

## Walkthrough

Two new blog posts were added: one detailing the history of Starlight Sidebar Topics plugins and another explaining how to combine the list and dropdown sidebar plugins for responsive navigation. Several existing blog posts received a new `description` metadata field. The `starlight-blog` dependency was updated in the project’s `package.json`.

## Changes

| Files/Paths                                                                                         | Change Summary                                                                                                    |
|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
| starlight/src/content/docs/blog/starlight-topics-history-story.md                                   | Added a new blog post covering the evolution of Starlight Sidebar Topics plugins.                                 |
| starlight/src/content/docs/blog/starlight-dropdown-and-list-together.mdx                            | Added a new blog post describing how to combine list and dropdown sidebar plugins for responsive navigation.      |
| starlight/src/content/docs/blog/setup-argocd-for-kubernetes.md<br>starlight/src/content/docs/blog/setup-continuous-integration-github-repository.md<br>starlight/src/content/docs/blog/setup-kubernetes-with-cilium-and-cloudflare.md<br>starlight/src/content/docs/blog/starlight-sidebar-whitespace.md<br>starlight/src/content/docs/blog/technically-impressive-github-profile-readme.mdx | Added a `description` metadata field to the frontmatter of each blog post.                                       |
| starlight/package.json                                                                              | Updated the `starlight-blog` dependency version from `^0.21.0` to `^0.23.2`.                                     |

## Sequence Diagram(s)

```mermaid
sequenceDiagram
    participant User
    participant Blog
    participant SidebarPluginList
    participant SidebarPluginDropdown

    User->>Blog: Loads documentation site
    Blog->>SidebarPluginList: Render topics list (desktop)
    Blog->>SidebarPluginDropdown: Render topics dropdown (mobile)
    SidebarPluginList-->>User: Displays sidebar topics (list)
    SidebarPluginDropdown-->>User: Displays sidebar topics (dropdown)
```

## Suggested labels

`📝 changeset`, `✒️ documentation`

## Poem

> In Starlight’s warren, new posts appear,  
> Sidebar tales and dropdowns clear,  
> Descriptions bloom with metadata bright,  
> Plugins combine for screens day and night.  
> A hop, a skip, dependencies grow—  
> Rabbits rejoice as the docs overflow!  
> 🐇✨

<!-- walkthrough_end -->

<!-- announcements_start -->

> [!NOTE]
> <details>
> <summary>⚡️ AI Code Reviews for VS Code, Cursor, Windsurf</summary>
> 
> CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
> Learn more [here](http://coderabbit.ai/ide).
> 
> </details>

---

> [!NOTE]
> <details>
> <summary>⚡️ Faster reviews with caching</summary>
> 
> CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure `Review - Disable Cache` at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the `Data Retention` setting under your Organization Settings.
> Enjoy the performance boost—your workflow just got faster.
> 
> </details>

<!-- announcements_end -->
<!-- internal state start -->


<!-- DwQgtGAEAqAWCWBnSTIEMB26CuAXA9mAOYCmGJATmriQCaQDG+Ats2bgFyQAOFk+AIwBWJBrngA3EsgEBPRvlqU0AgfFwA6NPEgQAfACgjoCEYDEZyAAUASpETZWaCrKNwSPbABsvkCiQBHbGlcSHFcLzpIACIAMxJqLjRaekQCF3QMeiJseCVIWPw+Am54BmQmZm58RHV4fAxoyAB3NGQHAWZ1Gno5MNgPbERKMIpggUoXSMRkNus7DEcJvgBWAHYNGAH5lAxcCkVsBml0SHJm+3T5TGzc/MKGIaiG/o9K6trxF/xYsPxS8qbABy+HQKTqDTQviUiAYFHg3C+WFayF4+AkeSiE1kDXouG24UiGnMlgAwiw2Ht2o5mM5XAZ3PwMF55JVKaEXviPLYWnNafk+lycPiigAaUbjSayaaITbueSIWDOKJoHj4EjiBhnfA0SAkAAevGktQwRHQ3CNDHg1HqWEKxW2TD27HFzQQDFgkDYuDQ3FgRTKUJZkBhcPgE2QuGaoLSAekXAaHhU+Dw9kxAmcyGa6k9tAO3Fo+GaGFmWT80mqJckHni1Gw/kQ4pumR1Az4ydTQpIEnwXjwtv4v24faI8BLu1OTpo+tC/niFH8eNBc2iAGUfRQvPAiLBNE1GWz2JAEDutzvcJHHf4bVJMniBrTNXrIuzkP4vNQogRXvMAOTU4RRFCR8aD4ARU0LE4MB1XYGD7fIaA9DBA18eI6AzBgAGt+D4fwghCZB7UYJVTWkYkDAsSAAFF9SQcRTX4QCxGraknAyb8JkgbAC0/WgjAZdRIi4WtODBVIrjvSAckxAoij+AEKhYD4ISwSADCBJZKC4dZIDUgBVYYKC4fZJQXaVjSMfRjHAKAyHoH5hUIUhyCoHoFFYdguF4RiRGYqQZFZRRlFUdQtB0KyTCgOBUFQTBHOIMhlDcw89i4KgLgcNj5D6JglCoELNG0XQwEMazTAMNJnDPXcAHpEAoBgaqndgasLcoaoELx8CIOqN2q3AwBKMpEDABBYxcMBxtkDRmFoDgDGiRaKMsABBABJBKXN4+waTpQdiMwUhECMFazhIC5Ou6tU0jCQSomiU7FSKUIxokhz1yq7dd0gVd02cGB/mGngRzHRAmhRMS6HFJQfXgLcGK7Hs+yRfahQ+zcvtCX6lAzPhoEB8pgewUcsFEGpZDSEhmDlbYPlCMd9kOY5Lw8dH+pDfBHnZG0XliKg2GjChMPFE9YH6sczXUdp4CqLcrVwWRxW4Sh7VpDBjibMs0AYZnajULcFc2Nb6aUPZ4FieATlVLoZglgoElwesSCSKSqEWD8+FaeRv2GbhnE/SABAOZJ5KBscOa59geYwV13U9SJ6AACXgAAREh8HwJtIEwkh5FpBntBc8VvzhB2PCFAMSahH6+sxn6/rxgnURBrBw4AeTEQQRgAJgABm7gAWGnUGHYnw9oJBhzQCn0B8UPCdqZhvB9cgU0QYNw6FWocf+1y236OKhjtvN/kLYsvTIIYs6ULdlgDmFtywD18DKDwHAtZ6sXkA00Flk4txzj+FaaQDgR1lG4bYaA8D+j4KGeEEYQxIEQDaRAsRtYo2zPiH8lcxzV1HiTQAmATID0mtSS/oLhcnkPaHO9B1B/EYNeXUqpzhExJpACQzhrR7HtnWeEDFVQnwLEWLAlJsCyWKE3cUGBf5RDZnXbGJBcYAwUpAFO+Yz4YBph4aRC4bxvAaPRYIWYcw/nfAkYY+05HnnYb3DQABmbuE4ABiiixh7T7t3FYscyiegZgcWgRwogHDwB4Wg1A0DijICoeGZpmBFA8NUZoKtvCsPDgwX0Kg4Z1DIpAZOacM6QCCGUTCwZki+jcmreQ+DQb0MiFIKgpB+ioBEk7ciTjexdWzAjMaxdIHQLkhDMgTB6xoFIL0eQeT06gm/HOdBckuTwFgeo4RqTW57GXGmP+fB3iJm4fiagXFhgsz8CmXUYSfQFAOMwbB8Iq6+GqZorYqBZmdyWW0TUQZ5CLkCfQXKb94AAC8kxlkXsOc2lt7yDEMnqQ0lBLbqxIOKR4XgujSPopLLAQozFtA8A5eptQXi2JWC0ExICEjMHhlENqjgo5InIoyOmCh1bwROH0RUnD+HsKQLaPamJVR8xYLk1OUz0ACFOe5NQyFumhJIGg5eIZpCYRKJALcN0MTnRJVgoUgiNHuUrEeF4cT9aIuPAzO2BzYh4CdigKoBwpCvkkmiG25rZI+CLGAbi11QjfgNMOeJTTFIIsRAUesXIKDkRJJAFaXhQLR0jNM7YSg4L+yRMgByvrP72T4NwbAnUyh6jNuIaQllIAggOqReNMLqgUDcnJHNeatTsGyYgAA3AGlAswzrNFKSkKItIha6sumaRlFtIiav9KmP5Crk2uVtOAxa0RLLlUqhjc8NU/ZYVGSQDQQhEANHmgu5aUaNrOSSlETK/b5AOQ9IdYtDJtj4oHA5IUAADFd/UwBDpfQq5WWQhnyE3tsF9G7MJbp3XujA37R0eAhtxc5UQBXXJfQAPVsd3AAjBoXu37vwobQ3YjQ3cX3AlBK2EYN6K30KUL+02VppDilhPCREjYcJMotjkWdLwkn+C9Mkbd/Ej3Rtjam+h2rRAezjftDNNbnjZtzXLAt4RLbHXUomYkh6DAQDAEYd9mM6oNSagYlqbVEAdS6j1YYjtuBgGcEQTmtAwD2jAJhXNlByA0FlLNA9S1KLrU2me1Iu0MjXpIkdE6aZTRju9GUi5FsSBeHoC+uBCIkTfohskJQS4fwCr2CBEYz7thDq9bxgdKzoNaK7QqxjKWBxogxDCU4QdLa/AvXSLg0R8ZhPkEk38c8fSANVF1fA2EDnkPoZZri3Ao0UDs5AUkKcJyqkwnYiofZKbhqaGWsj2yjPcLkuZ/NFGjotEoB4fk/H+K+ZjUlOdonE3iZTbd9NhpM2sfrQpptRaVNQBWr2+gOXcB5b4HFhLkAkvSDDIiW0XBOvTxO713w/WkwqoziNl6RZxsakm9N2b83FvZxW4wNboENDfsA2d5wmFdXQbB7ptd9VGrNT2K1Tmpmh11Q1NxGzM37OOaKM51zFB3NkVmi+haS1NPLtrvTgzTPcAs/auzyzXOpxjmwGvMADMSBEE4xgYgOZc1gH8MpK4M05ri8Xb5k9iVXLnqC1e34R272nRYQDoHBRLag/B9VqHDQ0tzAy1+BNFPSvn2g/+C+PpzmqkwZ6IUHC+weA64oOHPW+toAGyj4b6B0cUJjFjz1qoADi6hE65vLCboo3W44krnpxajXVZBB9OMt1bQxQJctVCtHnc2U4aH3GNMSKkdoWhfOwY5Bo6J22i9HwOEF1TIGgqEKEHfMBUOwOrJE1c5esYO1qWP5OI40r2BGwT13deVrEzOyTz3q21rkw2xTzaS2/cy5cgx7uQeJeS77jAXAQESw4bB4lZU4rLUrsiR4xaqjhxvrS61QM6GbOjM4mZmbdQc5WZgCq6LAa5a467Rz674iG7G41DqBV5m5i4aZaY6ZwHy4IFy4K5s7mboFc4ubLDC4jSx6YFZKOA2ZZCYFdTYC0CxAezbpeYW6CbW5bRuStbBaO6hbO4RZEBjqUq8izB/Z3YeBFaMoz7hIuze6Q6pYe7xb0Cx4/jTihDJ5dbw7p6Z5DZo7HgY4+wF5TaqgADSgu7BRO7eIwphrhhOzYpI3B1Mm2pGYaTKNAe2fAe+5ax23GFOSgp+V2wmt234V+EmImt+r2da8m+an2ymL+6hbu1AHeX+YOP+SI/++wQBP4WhNQwEGoUBE4sBn0MujOu28uKBSunO1mrBbmGo0gYAnBVoW4PBNw/BKYQhIh5B4hku2mFUNB+mbRSBHRrOqBFmNBk0DcgxCAHmG6oh5uh6Vu/mtugWWU+0TuKmj0EsUWDRs+pR+hTGhh6W6hqRhW5mxWRRuAJOTyyA5RA4MhgKJwQoRWcuIsX04s3SBydCTA+KDhGUtIc8FxE4bo6gFY2sJqhQ3CtQQKLGSSmMLGzYTAXUFAFQcUMsdW5ckCFoCQbsxwqM2wVi3028iizgJG/AYRO++23Uh28hWYp2vGCRAmSRN2DQl+921+GRvw0m9+ngj+eRd6II5A6mEuVB8xLR8Bsu7RDBaxNUiEsAyE6SPgsgmutqxo1YBBsAhuaI0GRuCQtAbAZu+o3mluq0khAWO0ZxIWt6KmB48hYknaLCDxNWfukBdxnuWWwJ7xI6BwuWxRlAw8vxEOjxtWdqmInaToVoFiMhDuP4dMRC4RLopqp4mMdsQoepBp2+SoPgZAx2zYe6yMt2Y4SMUgtCWA4EcME80qkAJeuAZeAgPABwNONgVEK0KcAAslROKGOHBIIXbKuAAGpF68bIQ5ofhIhNh4AsDRyaz0ACKyDSJdBagABC7AoIRe8ItAbJ22BZkRKOo4WoSJcRApF2kaQmIp44rxMqEpT2UpL2MmWaspH2ha+RmmUa6hQZv+UG4ZGhgcUZdR7+sZXxIwOhFyMBdOGpSxERKxiuTB5ZKELIJpRotsUgFpVpg5cMJAtpyQDps0+oL680ukL6TFsgv8XgBgukfx+6UaCqJAU2E8t4DMwBeFhpB01ZlGdZvY/YopgcJACAZYzA8gPZfZA5PwFFkAw5o5E54oLSfCZoC5S5asCI3g25jkj4toO5pwtA+5v8+aJ56y3ZF5xIjFTFMxqp6FtBmpyx2pSuGxOqwivBDmqqA0BApAYajpzpEhxx202Z5xvJ4WLCtRN0hI90jJoQ+MKiaip8KyzYAAMnRH8KFW2E0EqDICQGQJDJeVsAkvBb6h+DUmNiXCwJKuXNGDXOqVjA3MokDA8ogIACgEAiiqyqQVkk1sggalflxYvVJcjCyODYlYtQt4zJSiQ0hM0iGIRA0cRs9MzKghJwRoeEuQnw9GuwlUPg0cJ1JkzE0lREYqWCPVhydsGA3AzASsT1L1kkAAms4DHJJHOKdgimKSQIsuWIgMrH5G/N0VJHcDkgyvBXVmmZOEFDCr/MODWHJHEhPLELIKWdsEtf9DsuQHsqCE6BPFvkaeWH+g6OXE3CqvlS8DCEqv8PYKXGQKWJCiGMsufIamNWOoxmVeOEfAxKSKuKuBfBPKqPhPCDDdsMLaLSFUoScBiHrFkgrIHDivZFgKqEHAkJhNUAzDnpAAABy9y9zcD6jM3+DlXZi0D4gVaMpQh7qwQsqdp82s3+gci/BCgWzSK+ANjyrNiDZjjYTfiqjvCRC6g/x/xMhtVYRHkGwAqbBOK4JGlTmhAOBEBHQXizygRorVhsbbgjIibNh61Uj0LJAcIIq/Lt4sCArnX/AiYYiqgVyxAWxWjVzgG0q2iJGrTn6SafnTrpE/lVpZEP5AVKZ3pQCKkeAAAUQoTu/ppwLC/aoB58iVoQNOph0Ew9/5b2ORD5SN8piAAAlMqYupLqVJFAWvZL8FAgQFFclBSJ5H4GgBlPboHIFHlCoGoIVOFCVAYJfWyOoAAPp5CIBAP+DqpJK0BAMrqhBWT/02QhhoC9wCB2JoADzdwACcAAbIbZg+ki3bQAwA4isL3LWMcIbQPAPL3LQAPEoGgGsHYobR4BFIg9g73GgCsNg9g6Q73OhnYr3Jg3YjgzrCsJg+hpg33NQ4ogwEIxg5QysAwNg4w8VIYJfd3LQGsGsAIBIwwL3Eo73Ng7EGEuhgPLECsGg4bWI+I+hsY2sL3FQ7QIbehuhobdg6owgxAJACsD40IQw+g3o93Mg5g2sJw7QDg73CQNYwPNg33LQHYr4y43Yuwx45fWsAPFo9gzE5E5g242gGgN3DrOhoo93LEA45g2Et3No7EHYqoL3HYsQ5g/2aw14wIN3N3CQJ4vY8g3YvEysIbQIFYy3QwEQ2sLg1w4bQwG43QLQBwyQOhmsKk2w+w2gJg+g+ht3LU93Mw3YlE9g+hv3Gs2U7QCsGgDw3w64yQI4xmEs142sAkBY1gysLQ1kyQJM509YysLKkYwIGsOhhMCkIQ7M/g4sy01AHYkw1U6Y5oyQGM5g50+w4bX43o2Uzg1c0o38xMDExMM03/ZfbQMo7EE85E+wwc8cAPAkGsIbVo7QH3GU2sLENg3YuhrE0E180i7c1AKg9o8o644bQk5gwPMbSsLEAIGgjoyQE05KwIOEyEwS2gMw7EFM5ywUKs247I9rCc3w93Fk/sybUq1c/wxMCMzgyoGc2sF85gx4541AIA7gCA7QGAxA5bFA0A3ZKo0AA=== -->

<!-- internal state end -->
<!-- tips_start -->

---



<details>
<summary>🪧 Tips</summary>

### Chat

There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=trueberryless-org/blog&utm_content=57):

- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  - `I pushed a fix in commit <commit_id>, please review it.`
  - `Explain this complex logic.`
  - `Open a follow-up GitHub issue for this discussion.`
- Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples:
  - `@coderabbitai explain this code block.`
  -	`@coderabbitai modularize this function.`
- PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.`
  - `@coderabbitai read src/utils.ts and explain its main purpose.`
  - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.`
  - `@coderabbitai help me debug CodeRabbit configuration file.`

### Support

Need help? Create a ticket on our [support page](https://www.coderabbit.ai/contact-us/support) for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

### CodeRabbit Commands (Invoked using PR comments)

- `@coderabbitai pause` to pause the reviews on a PR.
- `@coderabbitai resume` to resume the paused reviews.
- `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
- `@coderabbitai full review` to do a full review from scratch and review all the files again.
- `@coderabbitai summary` to regenerate the summary of the PR.
- `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR.
- `@coderabbitai generate sequence diagram` to generate a sequence diagram of the changes in this PR.
- `@coderabbitai resolve` resolve all the CodeRabbit review comments.
- `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository.
- `@coderabbitai help` to get help.

### Other keywords and placeholders

- Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed.
- Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description.
- Add `@coderabbitai` anywhere in the PR title to generate the title automatically.

### CodeRabbit Configuration File (`.coderabbit.yaml`)

- You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository.
- Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json`

### Documentation and Community

- Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit.
- Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback.
- Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

</details>

<!-- tips_end -->
author_association: CONTRIBUTOR
user: login: netlify[bot]
created_at: 2025-05-05T18:00:14Z
body: ### <span aria-hidden="true">✅</span> Deploy Preview for *trueberryless-blog* ready!


|  Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | fa986c9acd5012646100fce413becd96aba675e9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/projects/trueberryless-blog/deploys/68260d7774716b000871e820 |
|<span aria-hidden="true">😎</span> Deploy Preview | [https://deploy-preview-57--trueberryless-blog.netlify.app](https://deploy-preview-57--trueberryless-blog.netlify.app) |
|<span aria-hidden="true">📱</span> Preview on mobile | <details><summary> Toggle QR Code... </summary><br /><br />![QR Code](https://app.netlify.com/qr-code/eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cmwiOiJodHRwczovL2RlcGxveS1wcmV2aWV3LTU3LS10cnVlYmVycnlsZXNzLWJsb2cubmV0bGlmeS5hcHAifQ.przfeoBpiw5XfIIY8tYhX_nRA57Nz-PmYvcQsPyIT-M)<br /><br />_Use your smartphone camera to open QR code link._</details> |
---
<!-- [trueberryless-blog Preview](https://deploy-preview-57--trueberryless-blog.netlify.app) -->
_To edit notification comments on pull requests, go to your [Netlify project configuration](https://app.netlify.com/projects/trueberryless-blog/configuration/notifications#deploy-notifications)._
author_association: NONE
user: login: trueberryless
created_at: 2025-05-15T05:10:02Z
body: I like this:

In burrows deep, two stories sprout,
Of sidebars clever, and plugins throughout!
One tells of dropdowns, lists that appear,
Responsive magic—sidebar cheer!
The other recalls a journey so bright,
Of plugins evolving in Starlight’s light.
author_association: MEMBER