Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve use of 'tags' #24

Open
CallumWalley opened this issue Nov 25, 2023 · 2 comments
Open

Improve use of 'tags' #24

CallumWalley opened this issue Nov 25, 2023 · 2 comments
Labels
feature request Request for new feature maintainability Reduce effort required to keep documentation up to standard.

Comments

@CallumWalley
Copy link
Member

Currently tags on the supported apps page are pulled from a file in an external repository.

This could be replaced with a 'domain whitelist' file somewhere in this repo, then any matching tags in an article meta are used in the supported apps page.

@CallumWalley CallumWalley added the maintainability Reduce effort required to keep documentation up to standard. label Nov 25, 2023
@CallumWalley CallumWalley added the feature request Request for new feature label Dec 3, 2023
@CallumWalley
Copy link
Member Author

#117 Adds page tags to supported app badges (in addition to the regular ones).

Currently any badges without CSS rules are hidden, so spammy tags are hidden.

Improvements to be made.

  • de-duplicate 'machine' tags. e.g. 'mahuika'. Also, decide if this is a tag we want app pages to have.
  • Remove spam tags (might be good to have an 'approved tags' list).
  • Filter out unshown tags.
  • Propigate tags other way? E.g from module_list.json

@CallumWalley
Copy link
Member Author

Done-ish.

See 'improvements to be made'

@CallumWalley CallumWalley changed the title Integrate article 'tags' with supported app tags. Improve use of 'tags' Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for new feature maintainability Reduce effort required to keep documentation up to standard.
Projects
None yet
Development

No branches or pull requests

1 participant