You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pymdownx introduced a new Blocks API as experimental in v9.10 (2023-03-05) and moved it out of beta in 10.12 (2024-10-28) , while marking some of the older API's extensions (Details, Tabbed) as "legacy". There are a handful of advantages to the new API, but the chief benefits are that 1) it is more extendable, and 2) whitespace indentation is no longer necessary when writing them, especially helpful for nested blocks.
The first step would be to modify mkdocs.yml, i.e.
Mentioned in #601 (comment)
pymdownx
introduced a new Blocks API as experimental in v9.10 (2023-03-05) and moved it out of beta in 10.12 (2024-10-28), while marking some of the older API's extensions (Details, Tabbed) as "legacy". There are a handful of advantages to the new API, but the chief benefits are that 1) it is more extendable, and 2) whitespace indentation is no longer necessary when writing them, especially helpful for nested blocks.
The first step would be to modify
mkdocs.yml
, i.e.user-guides/mkdocs.yml
Lines 322 to 351 in 03b4d6c
would be changed to
mkdown.yml
extensions as above!!!
Admonitions and???
Details fence syntax with///
pymdownx
API remains fully compatible withmkdocs-material
The text was updated successfully, but these errors were encountered: