X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=docs%2Fdocumentation_best_practices.md;h=059b25bcd3b536dbe0481e84968811f71927f0f5;hb=785474670426c9325fcf82a852618053f3dd1713;hp=f30793181c41afd870c755fed6160c13d77e333b;hpb=9e79bb14915ee39b756eaeb569b14a54fb9916ec;p=qmk_firmware.git

diff --git a/docs/documentation_best_practices.md b/docs/documentation_best_practices.md
index f30793181..059b25bcd 100644
--- a/docs/documentation_best_practices.md
+++ b/docs/documentation_best_practices.md
@@ -75,3 +75,23 @@ You can add some colors. What about a warning message?
 What about an error message?
 **[error [ERROR] This is not the error you are looking for]
 ```
+
+# Documenting Features
+
+If you create a new feature for QMK, create a documentation page for it. It doesn't have to be very long, a few sentances describing your feature and a table listing any relevant keycodes is enough. Here is a basic template:
+
+```markdown
+# My Cool Feature
+
+This page describes my cool feature. You can use my cool feature to make coffee and order cream and sugar to be delivered via drone.
+
+## My Cool Feature Keycodes
+
+|Long Name|Short Name|Description|
+|---------|----------|-----------|
+|KC_COFFEE||Make Coffee|
+|KC_CREAM||Order Cream|
+|KC_SUGAR||Order Sugar|
+```
+
+Place your documentation into `docs/feature_<my_cool_feature>.md`, and add that file to the appropriate place in `docs/_summary.md`. If you have added any keycodes be sure to add them to `docs/keycodes.md` with a link back to your feature page.