Skip to content
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

Style guide #81

Merged
merged 4 commits into from
Nov 5, 2024
Merged

Style guide #81

merged 4 commits into from
Nov 5, 2024

Conversation

vickytnz
Copy link
Contributor

@vickytnz vickytnz commented Nov 4, 2024

starting point for style guide.

Things to check:

  • all the points really
  • anything re formatting. I thought this would be a definition list but the health guide A-Z is headings?

Fixes #62

Style guide

We normally use the NHS content guide for terms. But there are some terms that are only used in the guidance for the kit:

command line

Lower case. Only use for Windows instructions. Nortmally it will be ‘the command line’.

GOV.UK Prototype Kit, GOV.UK Design System and other GOV.UK products

Title case.

NHS, NHS.UK, NHS England

Use ‘NHS.UK’ for products that are for delivery teams and not the public (find out more on the NHS health writing A-Z)This includes the NHS.UK prototype kit, NHS.UK design system, NHS.UK service manual or NHS.UK website.

#### NHS England laptops
Use ‘NHS England Windows laptops’ instructions for people using corporate laptops.

NHS.UK prototype kit

‘NHS.UK’ is in caps and ‘prototype kit’ in lower case (except where the NHS.UK is shown as a logo when it is then presented as ‘NHS Prototype kit’). Write out in full the first time it is used on a page, then call ’the kit’. Do not use ‘prototype kit’ if you can.

terminal

Lower case. Only use for Mac and Linux instructions. Usually it will be ‘the terminal’.

Things I'd like to add:

  • anything about file paths - for example do we always need to spell them out as from the top or is it OK to be a bit more loose about them?
  • more about the terminal and command prompt stuff, maybe I don't have enough yet to complete that

@frankieroberto frankieroberto temporarily deployed to nhs-prototyp-style-guid-enayl7 November 4, 2024 22:34 Inactive
README.md Outdated Show resolved Hide resolved
Co-authored-by: Ed Horsford <[email protected]>
@vickytnz vickytnz temporarily deployed to nhs-prototyp-style-guid-enayl7 November 5, 2024 17:56 Inactive
Copy link
Contributor Author

@vickytnz vickytnz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed

@vickytnz vickytnz dismissed edwardhorsford’s stale review November 5, 2024 18:04

Changed merged into branch

@vickytnz vickytnz merged commit 8724526 into main Nov 5, 2024
4 checks passed
@vickytnz vickytnz deleted the style-guide branch November 5, 2024 18:04
@vickytnz
Copy link
Contributor Author

From Sara - looking to change from NHS.UK to NHS.
This means opening this ticket up again @sarawilcox

@sarawilcox
Copy link
Contributor

Hi @vickytnz , for GOV.UK and NHS we lower case "prototype kit": GOV.UK prototype kit. No need for title case. Ditto GOV.UK design system. (There are some inconsistencies in the service manual but we generally use sentence case for service names.)

We avoid using "NHS.UK" as it confuses people. Some people think we're referring to the NHS.UK programme. Other people think we're talking about the wide nhs.uk domain. So we tend to write: NHS prototype kit, NHS design system, NHS digital service manual and "the NHS website (at www.nhs.uk)". Again there are some inconsistencies, particularly with the frontend and our GitHub repos. Part of the reason we prefer NHS to NHS.UK is that it makes it clear that the design system, prototype kit etc are for the whole NHS, regardless of programme or domain.

I have been using "prototype kit" but could switch to "kit" (after first spelling NHS prototype kit out in full). I was wondering why you say not to use "prototype kit"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Style guide for prototype kit instructions
4 participants