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

Highlight *S*upported items #62

Open
gundalow opened this issue Apr 12, 2022 · 4 comments
Open

Highlight *S*upported items #62

gundalow opened this issue Apr 12, 2022 · 4 comments

Comments

@gundalow
Copy link
Contributor

gundalow commented Apr 12, 2022

Some items on the list are Supported by Red Hat, should we highlight that?

Other projects are Maintained by Red Hat, should they be highlighted?

I've not looked at enough other lists to see what they do.

@gundalow
Copy link
Contributor Author

@KeyboardInterrupt what do you think? I don't want to abuse what you've built over the years.

Maybe something like:

Ansible Lint - Checks Playbooks for best practices and behavior that could potentially be improved. (Supported by Red Hat)
ARA - ARA Records Ansible playbooks and makes them easier to understand and troubleshoot with a reporting API, UI and CLI. (Maintained by Ansible Community)

@KeyboardInterrupt
Copy link
Member

KeyboardInterrupt commented Apr 13, 2022

I think distinguishing, or rather highlighting, Items, in a way is a good Idea. I have seen other lists do similar things by utilizing Emojis i.E. adding a 🐋 when something runs on docker or 💎 when something is "especially awesome".

But I guess adding Text is more clean, inclusive and easily implemented.

A compromise would be to have labels like this:

  • Ansible Community Project
  • Officially supported by RedHat
  • Whatever

With good Alt text for the Images, this approach would also be pretty and somewhat inclusive for People with screenreaders.

@rndmh3ro
Copy link
Contributor

I prefer plain text (maybe bold or italics) instead of emojis or labels. Plain text does not interrupt the text flow and is more accessible.

@KeyboardInterrupt
Copy link
Member

Hey, I want to revisit this. After some more pondering, I believe we shouldn't introduce a special label; instead, we could leverage the description text, like so:

This item is already distinctly identified as a resource provided by Red Hat through its description.

I think explicitly stating the source in the description might suffice without the need for bold, italic, or any other formatting.

If there's no strong objection to this approach, I'd like to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants