Feature requests breakout session

Notes from the feature requests breakout session.

Best practices

1. Submit a ServiceNow request so we can look at the page more directly and give you one on one assistance with what you are trying to accomplish on your page. Some things can be worked around using the content types we have and some things we don't have the capability to do right now. However, it is extremely beneficial to us to know exactly what you want. As of right now, we have a list of things we assume you all would want. But if you file a ServiceNow request along with putting things on the feature request board, we can see what you want and prioritize requests accordingly.

2. It's really hard to make an accessible pdf. It's A LOT easier to make accessible HTML content.

Questions and answers

What are the best practices for linking documents? What is the right way for linking documents?

Check out our resources for linking to documents.

Why are the URLs for documents different depending on where they live on a page? For example, it will say media/number or /doc.

Media/number is not very informative, so in 2017 we made all document URLs /doc/ to be more friendly and helpful. They are the same thing, but the /doc is just a newer document, alias, or nickname, for the document, whose real underlying link remains /media/###.

When I find a bug in Drupal and report it through ServiceNow, I'm told to make a feature request. And I feel like the feature requests go into a hole and never get addressed. I feel like I make my feature request and I am forgotten. I also think bugs and features are different and need to be handled differently.

We handle and prioritize bugs and features together. We look at what people are reporting, and resolve the high priority bugs and features. We have limited resources and we try to tackle everything using priorities to attack the ones that will help the most people.

Curated lists have boxes in boxes and it is difficult to see what you have when you have large lists. They’re difficult to maintain and edit.

For shorter lists, use the crosshairs on the left side to drag and reorder the content. On longer pages, click the show row weights link and order each section numerically in the order you'd like them to appear on the page. But, If it is super long then try to break up the page

I use tables a lot and I am having issues with them. For example, one of my pages is just a table, two columns, and when you enter the information in one column it doesn’t line up with the second. There is no rhyme or reason to line it up, you can’t tell if it is going to look good. Is there something coming out that will make the tables easier to use?

Submit a ServiceNow request the next time this happens. Submitting a ServiceNow request when you are really frustrated with something allows us to look more deeply into something and help more because we are more focused on it directly.

Generally, tables shouldn't be used for any content other than data sets.

Will the Information Detail's table of contents be able to have a double column like Guide pages?

For mobile phones and accessibility purposes, the single column is preferable. So, that is why we haven't switched the Info Details table of contents to a double column like the Guide page. This also means that eventually, for accessibility purposes, we will make the Guide table of contents into a single column as well.

I have about 2,000 documents in the CMS for my agency and, as of right now, I have to go in one by one to edit any of the document’s names. How can I go through document names and make mass edits? Is there something that will come out so I can make this an easier process?

For something like this, it's best to submit a Feature Request with this specific use case as an example for the problem this feature would solve.

Was this article helpful?