aboutsummaryrefslogtreecommitdiff
path: root/docs/support_deprecation_policy.md
diff options
context:
space:
mode:
authorNick Brassel <[email protected]>2024-05-30 12:00:41 +1000
committerGitHub <[email protected]>2024-05-30 12:00:41 +1000
commit6ef97172889ccd5db376b2a9f8825489e24fdac4 (patch)
tree334e3bf41c8554d4bee73a140822f95f60eb64e9 /docs/support_deprecation_policy.md
parent395766657ff98a4b1fd0dcba5917557f8acbb9e4 (diff)
downloadqmk_firmware-6ef97172889ccd5db376b2a9f8825489e24fdac4.tar.gz
qmk_firmware-6ef97172889ccd5db376b2a9f8825489e24fdac4.zip
Vitepress conversion of docs. (#23795)
Diffstat (limited to 'docs/support_deprecation_policy.md')
-rw-r--r--docs/support_deprecation_policy.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/support_deprecation_policy.md b/docs/support_deprecation_policy.md
index f7107dfc89..450a578e2e 100644
--- a/docs/support_deprecation_policy.md
+++ b/docs/support_deprecation_policy.md
@@ -6,7 +6,9 @@ In general, feature development is encouraged to support as many hardware config
The most frequently-hit constraint is the amount of code that can be flashed onto an ATmega32U4 -- users almost always need to pick and choose included functionality due to the size constraints.
-!> [Squeezing AVR](https://docs.qmk.fm/#/squeezing_avr) has some steps that users can take in order to minimise the overall firmware size, which in some cases enables the ability for users to include other desired features.
+::: warning
+[Squeezing AVR](squeezing_avr) has some steps that users can take in order to minimise the overall firmware size, which in some cases enables the ability for users to include other desired features.
+:::
## Deprecation & Removal Policy
@@ -27,7 +29,9 @@ There may be several motivations behind the deprecation or removal of functional
When a feature is selected for deprecation, future changes to that area will cease to be developed by the QMK team, and Pull Requests submitted against those areas will be declined.
-?> As QMK does not gather metrics from its users, the only way the QMK team can gauge the level of usage is to refer to the main QMK Firmware repository -- searching through forks is not practical due to the sheer number of them.
+::: tip
+As QMK does not gather metrics from its users, the only way the QMK team can gauge the level of usage is to refer to the main QMK Firmware repository -- searching through forks is not practical due to the sheer number of them.
+:::
### How much advance notice will be given?