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

[Spike] Should we open the KB articles to more types of content allowed? #20066

Open
2 tasks
srancour opened this issue Dec 9, 2024 · 0 comments
Open
2 tasks
Labels
CMS Team CMS Product team that manages both editor exp and devops

Comments

@srancour
Copy link
Contributor

srancour commented Dec 9, 2024

User Story or Problem Statement

As an editor of the KB I want to build the most robust articles for editors to be able to get the information they need.

As an editor I want high quality KB articles for me to learn from.

Description or Additional Context

This came up when working on bringing the PDFs out of the KB and making them actual html in the KB. Some of the limitations have made it so there are single elements in a list with images between instead of being able to put a full ordered list together with images in context that make sense to screen reader users. Visually it can be done, but to a screen reader user it will read as single item separate lists, which makes it more confusing like when there are 3 steps to the process, but they hear that there's only one item in the list they're on.

An example page where this can be seen is the Find your environment section on the How to access and manage demo environments page.

Steps for Implementation

Discover what content types are turned off in the KB and come up with a list of recommendations for content types that would be useful to turn on to make the KB the best source of information we can for editors.

Acceptance Criteria

  • Discover list of content types that are turned off for the KB
  • Create a list of recommended content types that should be turned on for the KB
@srancour srancour added CMS Team CMS Product team that manages both editor exp and devops Needs refining Issue status labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMS Team CMS Product team that manages both editor exp and devops
Projects
None yet
Development

No branches or pull requests

2 participants