Please describe the feature you feel like this repository should have.
Add tags to questions as a building block to tag-related functionality.
The heart of this issue should address the following:
- Would this suggestion be of significant benefit to users (see Potential Benefits section)
- How should tags be implemented in "Actions question files", i.e.
questions/**/actions/*.md files (see Proposed Structure) section
Potential Benefits
As for what tags would be used for, that's a larger discussion but it would be cool to do things like:
- Filter questions based on the type of tag, so users could then test themselves on a certain topic.
- After a practice exam, the post-mortem could break down what kinds of questions the user got wrong (ex. some sort of graphical display and/or statements like "You got 5 questions wrong that were related to ." Obviously, a textual approach would be more straightforward to implement.)
- If a tag has its own page, gather relevant links from questions for a kind of "library" regarding that tag (ex. The "runner" tag could link to Github-hosted runner documentation, self-hosted runner documentation, other documentation concerning runners (This one has the most overhead)
Proposed Structure
Perhaps something like the following would work to define a tag
question: What is the benefit of using self-hosted runners vs. Github-hosted runners?
documentation: "Some-documentation-here.com"
tags: [runners]
A question should have at least one tag, with the potential for multiple tags if applicable.
I don't know a TON about how keys like question and documentation get worked into the UI of a question, but the top section seems to be the most-appropriate place for a tags key.
I'd be down to help code this out, but would need some time to get familiar with the codebase and my bandwidth has been sporadic recently. Just let me know what you think
Additional context
Please describe the feature you feel like this repository should have.
Add tags to questions as a building block to tag-related functionality.
The heart of this issue should address the following:
questions/**/actions/*.mdfiles (see Proposed Structure) sectionPotential Benefits
As for what tags would be used for, that's a larger discussion but it would be cool to do things like:
Proposed Structure
Perhaps something like the following would work to define a tag
A question should have at least one tag, with the potential for multiple tags if applicable.
I don't know a TON about how keys like
questionanddocumentationget worked into the UI of a question, but the top section seems to be the most-appropriate place for atagskey.I'd be down to help code this out, but would need some time to get familiar with the codebase and my bandwidth has been sporadic recently. Just let me know what you think
Additional context