-
Notifications
You must be signed in to change notification settings - Fork 14.8k
Add title case style guideline #35990
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
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
Assigning a SIG Docs Chair since this is trying to change the style guidelines. |
@shannonxtreme Heya Shannon! 👋 Our style guide takes a lot of inspiration from the Google developer documentation style guide, which recommends sentence case for titles and headings. I'm wondering what the motivation is to take a different approach? If there's a conversation that yourself and Tim have had, my apologies in advance for not being aware of the context. |
Ah @natalisucks I was trying to codify what I was seeing here: #35908 (comment) I wasn't trying to change the guideline -- was trying to put the current convention in writing in our SG |
@shannonxtreme Gotcha! It might not surprise you to hear that I don't agree with the suggested change in that comment 😂 Looking at the docs homepage for example, the all capitals convention isn't followed (at least mostly), and I would personally prefer consistency across the docs. However, I also see that capitalization is used across other areas of the docs very specifically (such as in our Concepts area, but not specifically in the Contribute section), so I'm now wondering what we decide on and try and ensure consistency from there. TL;DR – We don't have a unified "current convention", but it is certainly a good idea to decide on one and stick with it. Would be happy to hear your take @sftim if you feel strongly about this 😸 |
Fwiw I use the dev docs style guide a lot and agree with sentence case as well 😁 I think it's def helpful to have a place in our domain to point to in reviews if needed |
Let's discuss what option we want to document in the async Slack (and thank you @bradtopol for tagging Natali!) /hold |
{{< table caption = "Do and Don't - Use title case for page titles" >}} | ||
Do | Don't | ||
:--| :----- | ||
Kubernetes API Server Bypass Risks | Kubernetes API server bypass risks | ||
Configure a Security Context for a Pod or Container | Configure a security context for a Pod or container | ||
{{< /table >}} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we clarify that this is just for the title in the front matter, and not for headings within the page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this convention apply to all titles, page and heading? I dont think that we have a guideline for headings (i couldn't see it in the style guide, please point it out to me if its there already) but it seems to be the general convention that we use in headings as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The guidance on page titles could link to the advice on headings, maybe also vice versa?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be a good idea to merge the titles section into the heading section, call it "Headings and titles" maybe, and clarify what works where.
And I'd still like us to discuss changing the guidance for titles to use sentence case as well, but perhaps as a separate issue. The 5 votes that got in Slack arent many though
@natalisucks to me this isn't a change; it's codifying the existing convention (which is not that well followed or as well known). I learned that convention from approvers / reviewers telling me about it. |
I'd kind of like to merge this PR so it becomes part of the style guide history, even if we then decide we want to change from that convention. That'll help someone looking for a answer to a question like “Hmm, when did we adopt the previous convention and what was our thinking when we did”. |
I agree that we should document that title case is used for the front matter title
|
The title of the ConfigMaps page is, unfortunately, both sentence case and title case (due to our guidelines about how to capitalize API kinds). Maybe a different example? |
80a1946
to
9c777bf
Compare
@sftim and @reylejano I merged this into the headings section which I renamed to Headings and titles (added an anchor to not break links). I prepended the example with |
/unhold |
Use sentence case for headings in the page body. For example, **Extend kubectl | ||
with plugins** | Use title case for headings in the page body. For example, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bold tags appearing as text in preview.
|
Yeah I will open a new issue that we can use to implement that as official guidance for both headings and titles! |
Thanks for following up with this, @shannonxtreme! Given the feedback throughout the PR, I'm happy to sign-off on this being added to make our style guide clearer. |
LGTM label has been added. Git tree hash: a117a41516e6fdb01d46b67252a2d8b4812e8567
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small wording suggestion.
9c777bf
to
8a7f4b6
Compare
8a7f4b6
to
e688bb8
Compare
This is ready for review :) |
/lgtm |
LGTM label has been added. Git tree hash: 57285ccdda0ec85c281b8c7123a942e1168636be
|
/approve We can track a new(?) issue to change this guidance |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Update the style guide to add guidance for title case in page titles
/sig docs
/language en
/cc @sftim