From 1ff2d697d79bca9a381fbb4c8b565e4d7baa08ed Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Sep 16 2020 12:22:38 +0000 Subject: review of team directory mechanics --- diff --git a/council/modules/ROOT/pages/procedures/team_directory.adoc b/council/modules/ROOT/pages/procedures/team_directory.adoc index 1da3571..6fcf5a6 100644 --- a/council/modules/ROOT/pages/procedures/team_directory.adoc +++ b/council/modules/ROOT/pages/procedures/team_directory.adoc @@ -46,9 +46,6 @@ Checks can be done at any time, but should be done around the branch date for ea == Mechanism -WARNING: This section has been written by bcotton based on his understanding of how the mechanism works. -Treat it with caution until asamalik verifies it and removes this warning. - === Team information files The directory requires a file that contains the information about the team. @@ -61,4 +58,7 @@ See the https://pagure.io/Fedora-Council/council-docs/blob/master/f/engineering/ Teams will appear in the directory if the team info file is included in the `{engineering,mindshare}/modules/ROOT/pages/index.adoc` directory of the https://pagure.io/Fedora-Council/council-docs/[council-docs repo]. After `include`-ing the info file, the index page must include the `team_render.adoc` file that defines the rendering. +=== Reusing the data on team pages + +Teams can include their `NAME_team_info.adoc` file on their page(s), and then use `{team_name}`, `{team_summary}` etc. anywhere on the page.