kb01/zmk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(docs): Work around docusaurus bug causing broken links

Browse source 
Some links ended up broken after docusaurus 3 upgrade,
especially if they are the second on the same line and have anchors.
Likely due to https://github.com/facebook/docusaurus/issues/9518
This commit is contained in:
Cem Aksoylar 2024-01-12 21:59:17 -08:00
parent 1b326ff856
commit 5cbffd6625
3 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/docs/features/conditional-layers.md
View file

@ -49,8 +49,8 @@ condition in another configuration, possibly repeatedly.
:::warning :::warning
When configured as a `then-layer`, a layer's activation status is entirely controlled by the When configured as a `then-layer`, a layer's activation status is entirely controlled by the
conditional layers feature. Even if the layer is activated for another reason (such as a [momentary conditional layers feature. Even if the layer is activated for another reason (such as a
layer](../behaviors/layers.md#momentary-layer) behavior), it will be immediately deactivated if the [momentary layer](../behaviors/layers.md#momentary-layer) behavior), it will be immediately
associated `then-layers` configuration is not met. As such, we recommend avoiding using regular deactivated if the associated `then-layers` configuration is not met. As such, we recommend
layer behaviors for `then-layer` targets. avoiding using regular layer behaviors for `then-layer` targets.
::: :::

3
docs/docs/hardware.mdx
View file

@ -41,7 +41,8 @@ export const toc = [
]; ];
With the solid technical foundation of Zephyr™ RTOS, ZMK can support a wide diversity of hardware targets. With the solid technical foundation of Zephyr™ RTOS, ZMK can support a wide diversity of hardware targets.
That being said, there are specific [boards](faq.md#what-is-a-board)/[shields](faq.md#what-is-a-shield) that have been implemented and tested by the ZMK contributors, listed below. That being said, there are specific [boards](faq.md#what-is-a-board) /
[shields](faq.md#what-is-a-shield) that have been implemented and tested by the ZMK contributors, listed below.
<HardwareList items={Metadata} /> <HardwareList items={Metadata} />

4
docs/docs/user-setup.mdx
View file

@ -105,7 +105,9 @@ Pick an keyboard:
:::note[For a keyboard not in the included list:] :::note[For a keyboard not in the included list:]
If you are building firmware for a new keyboard that is not included in the built-in If you are building firmware for a new keyboard that is not included in the built-in
list of keyboards, you can choose any keyboard from the list that is similar to yours (e.g. in terms of unibody/split and [onboard controller](hardware.mdx#onboard)/[composite](hardware.mdx#composite)) to generate the repository, list of keyboards, you can choose any keyboard from the list that is similar to yours
(e.g. in terms of unibody/split and [onboard controller](hardware.mdx#onboard) /
[composite](hardware.mdx#composite)) to generate the repository,
and edit / add necessary files. You can follow the [new shield guide](development/new-shield.mdx) if you are adding support for a composite keyboard. and edit / add necessary files. You can follow the [new shield guide](development/new-shield.mdx) if you are adding support for a composite keyboard.
::: :::