Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
@dangbert This doesn't fit within our style guide, however we are moving away from quotes for important items and towards putting them in bold, so this would be acceptable:
If you don't think that's sufficient, I really don't like the placement of that callout. Think of text formatting as a means of directing attention. If you direct attention somewhere with a callout, you're basically taking it away from somewhere else, and that "somewhere else" is usually the area immediately following the place where you've directed the attention. That's fine if there's a bunch of text afterward to remind the reader there's more to read, but when you follow a callout with one line of text and then a heading for a new section, that one line of text is going to get lost. I would rather see the callout at the end of the section if there's nowhere further up the section where it makes sense. But even if the callout gets moved, "Immutable" should still be bolded, because that's what we're doing now. |
Why:
Closes: #43715
What's being changed (if available, include any code snippets, screenshots, or gifs):
Make important text bold so it's harder to overlook.
Check off the following: