updated docs

src/docs/design-tokens.md

@@ -5,7 +5,8 @@ title: Design tokens
 Edit all your preferences (colors, fluid text sizes etc.) in `src/_data/designTokens/*.json`.
 
 Additional colors, variants and gradients for custom properties are automatically created in `src/assets/css/global/variables.css` based on the colors set in `colors.json`. If you change names you should edit `variables.css` as well and check if the names are used elsewhere in the template.
+Admittedly, I went a little bit crazy there with the new CSS color syntax stuff.
 
 In the [style guide](/styleguide/) you can see how everything turns out.
 
-Please note that adjustments in `viewports.json` only affect your utility classes and custom properties, but do not change the dimensions of your page. You can control this using the custom property `--wrapper-width`.
+Please note that adjustments in `viewports.json` only affect your utility classes and custom properties, but do not change the dimensions of your page. You can control this using the custom property `--wrapper-width`.

src/docs/open-graph.md

@@ -24,7 +24,7 @@ To change the look and behaviour of those images and replace the SVG background
 
 The implementation is based on [Bernard Nijenhuis article.](https://bnijenhuis.nl/notes/automatically-generate-open-graph-images-in-eleventy/)
 
-If you want to be inspired, have a look at [what Lea does here.](If you want to be inspired, have a look at [what Lea is doing here.](https://lea.codes/posts/2023-04-25-pseudorandom-numbers-in-eleventy/)
+If you want to be inspired, have a look at [what Lea is doing here.](https://lea.codes/posts/2023-04-25-pseudorandom-numbers-in-eleventy/)
 
 Previously the images were created at build time, but this leads to not rendering the font - if the system executing the build has not installed it, it will not be generated.
 

src/docs/tags.md

@@ -21,9 +21,10 @@ In several places you will find a code block that looks like this:
 
 {% endraw %}
 
-Here `card.njk` is imported as a component, and some settings are made beforehand. In connection with tags, ` {% set activateTags = true %}` is important, because here you can switch off the display of tags in this card instance.
+`card.njk` is imported as a component, and some settings are made.
+With `set activateTags = true` you can switch the display of tags in this card collection instance.
 
-The tags are in your collection items in the front matter with the syntax
+The tags are placed in the front matter of the posts, using the syntax
 
 {% raw %}
 
@@ -45,6 +46,4 @@ tags: ['markdown', 'feature']
 
 {% endraw %}
 
-are entered.
-
 If you generally do not want any tags to show, it is probably easiest to not create any at all.

src/docs/theme.md

@@ -6,8 +6,10 @@ With version 2.0 I introduced dark and light mode. This is not intended to be a
 
 Dark and light mode respects the user agent or operating system settings using the `prefers-color-scheme` CSS media feature. But there is also a switch in the `<footer>`.
 
-If you want to change something here, for example replace the button with a classic sun/moon icon, make sure to preserve accessibility. The accessible name ("Theme dark" or "Theme light") results from two IDs:
+If you want to change something here, for example replace the button with a sun/moon icon, make sure to preserve accessibility. The accessible name ("Theme dark" or "Theme light") results from two IDs:
 
 `aria-labelledby="theme-switcher-label theme-switcher-value"`
 
-If you remove the text content of the `<button>`, the value for `theme-switcher-value` must therefore be obtained differently.
+If you remove the text content of the `<button>` and you don't use the heading with the ID `theme-switcher-label`, the value for the accessible name must obtained differently.
+
+If you find any accessibility issues, please let me know.