From e9b38d8a9a0558afb5e23d834fdeb594e38a8a56 Mon Sep 17 00:00:00 2001
From: Simon Lecoq <22963968+lowlighter@users.noreply.github.com>
Date: Sun, 13 Feb 2022 20:56:42 -0500
Subject: [PATCH] docs(plugins/core): add note about `config_order`

---
 source/plugins/core/README.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/source/plugins/core/README.md b/source/plugins/core/README.md
index 3731b5e0..86f1b82b 100644
--- a/source/plugins/core/README.md
+++ b/source/plugins/core/README.md
@@ -53,6 +53,9 @@ Content can be manually ordered using `config_order` option.
 
 > 💡 Omitted sections will be appended at the end using default order
 
+> ℹ️ The handles to use for each plugin and sections is based on the [`partials/_.json`](/source/templates/classic/partials/_.json) of the template.
+> It may not necessarly be the plugin id (e.g. `base.header`, `base.activity+community`, `base.repositories`, etc.).
+
 ## 🪛 Using presets
 
 It is possible to reuse the same configuration across different repositories and workflows using configuration presets.
@@ -970,4 +973,4 @@ This option has no effects on forks (images will always be rebuilt from Dockerfi
 <b>default:</b> no<br></td>
   </tr>
 </table>
-<!--/options-->
\ No newline at end of file
+<!--/options-->