Hero: Table's width is too wide and doesn't render entirely on screen

[bradleycamacho]

Tell us what you need

The table in the AWS Integrations Metrics doc is far too wide. Some cells have extremely long contents and make the table extremly hard to navigate. Not sure what the solution is, but we could explore wordwrap or something.

Report:
"Hello @hero not sure if this was reported earlier but this what i am seeing on the Docs page. Not sure if this is how it supposed to look...FYI. Here is the link: https://docs.newrelic.com/docs/integrations/amazon-integrations/get-started/aws-integrations-metrics"

Anything else you'd like to share?

[paperclypse]

I'm also seeing this issue when tables have code blocks in them. For example, here: https://docs.newrelic.com/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/get-started-incident-intelligence/#configure-algorithmia

This is especially messy when those tables are inside collapsers :D

[rhetoric101]

I would like to echo the previous comments and emphasize that this seriously compromises the value of some of our docs. Essentially, users can't read some of these tables, unless they were to do something like view the source.

[bradleycamacho]

This is currently tagged as a content issue, but I'm going to ping @jpvajda and label it as eng since it seems to be a styling issue.

[jpvajda]

@bradleycamacho / @paperclypse given the <table> component is being referenced in the collapser I'm wondering if we just have a bug in the table component.

But I agree, this is a pretty bad bug, so we'll see if we can knock it out in sprint 4