[updating bug title to reflect request]

Hey dglazkov@, thanks for the feedback!  That site is still a WIP, and I'd 100% agree more explanation re: terminology is necessary.  I'll be iterating with sshruthi@ on the look and feel of the page in the near future, and I'll be sure to revisit this bug and get your input on final design once available.  This may be in a little while, as we're focusing on removing the @google.com restriction first and foremost, but rest assured this is on our radar.

"That site is still a WIP" should really be "that specific page."

dglazkov@, sshruthi@, can you PTAL @ our staging instance (https://chromiumdash-staging.googleplex.com/) and head to the "Components" view and let me know what you think of what you see there?  Note, the view takes ~1 minute to load initially - we'll be fixing that with caching ASAP.  Also note the data will look wrong, it's because we're fetching data for staging instance from Monorail staging, will look right when we swap over to prod.

To address this, I've made the "SLO Violations" graph now only show Pri-0,1 violations and triage violations, both of which are Blink standards; I've also made this match the data displayed in the tabular view.  The tabular view column headers now link to the web platform SLO documents so that it's easy to find the exact definition.

I think this makes this understandable, so I'm going to mark this bug as fixed.  Please reopen if you need more details or any more data, though, or really if you have any feedback on the page.  Thanks for the feedback!