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.

Sign up for GitHub

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

Update naming things page #959

Merged
merged 1 commit into from
Nov 7, 2024
Merged

Update naming things page #959

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/standards/naming-software-products.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: How to name software products
last_reviewed_on: 2024-05-03
last_reviewed_on: 2024-11-07
review_in: 6 months
---

Expand All @@ -12,11 +12,11 @@ Read this guide when you need to name components for your software product, for

Avoid using puns or branding for names as this makes it difficult for others to understand what it does.

Make sure you use the same name consistently whenever you're referring to the same product. For example the name of the Signon application’s GitHub repository is [alphagov/signon](https://github.com/alphagov/signon).
Make sure you use the same name consistently whenever you're referring to the same product. For example the name of this website's GitHub repository is [alphagov/gds-way](https://github.com/alphagov/gds-way).

These GDS product names clearly communicate their purpose:

- [Signon](https://github.com/alphagov/signon)
- [Travel Advice Publisher](https://github.com/alphagov/travel-advice-publisher)
- [Manuals Publisher](https://github.com/alphagov/manuals-publisher)
- [Smart Answers](https://github.com/alphagov/smart-answers)

Expand Down