Predefined tag lists

[Josh-Cena]

Discussed in #5911

^{Originally posted by mambax November 9, 2021}

Use Case

To our docs contribute now more than 40 people. They all love tags in docs and blogs. The issue arising is that we have the same tag multiple times, like

infra-as-code
infra as code
infrastructure as code
infrastructure-as-code

You can figure.

Proposed idea

Allow a tags.yml to be assigned to each plugin/preset.

tags:
  - infrastructure-as-code
  - kubernetes

• If then users add tags to docs/blog that are not present in the list, the build fails (optionally, warns).
• If the file is not specified, the current approach would apply
• This would be similar to the global authors approach where you have only 1 author file

Is something like that already present and I am just too blind to find it?
If not could you rate its complexity and if it would fit your feature set? I would like to contribute something but only if I can try by myself without asking for guidance every 2h 😊

[Josh-Cena]

@mambax I think this is a feature worth adding, and it would be easier to track if we add it to the issue queue. Are you willing to self-service?

[mambax]

Certainly, will do! 🤝
Okay edit: I am over-asked. What means self-service? I see you created an issue already 😦

[mambax]

Did you mean like #5913?