Skip to content

Commit 36c5896

Browse files
authored
CCM-12397: update README (#32)
* CCM-12397: update README * CCM-12397: update contacts * CCM-12397: resolve comment * CCM-12397: resolve comment
1 parent 19d34c9 commit 36c5896

File tree

3 files changed

+14
-50
lines changed

3 files changed

+14
-50
lines changed

README.md

Lines changed: 13 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,27 @@
11
# NHS Notify Digital Letters
22

3-
[![CI/CD Pull Request](https://github.com/nhs-england-tools/repository-template/actions/workflows/cicd-1-pull-request.yaml/badge.svg)](https://github.com/nhs-england-tools/repository-template/actions/workflows/cicd-1-pull-request.yaml)
4-
[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=repository-template&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=repository-template)
3+
[![CI/CD Pull Request](https://github.com/NHSDigital/nhs-notify-digital-letters/actions/workflows/cicd-1-pull-request.yaml/badge.svg)](https://github.com/NHSDigital/nhs-notify-digital-letters/actions/workflows/cicd-1-pull-request.yaml)
4+
[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=nhs-notify-digital-letters&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=nhs-notify-digital-letters)
5+
6+
This repository contains the infrastructure and code required to deliver letters digitally that would traditionally be printed and posted.
7+
8+
NHS Trusts currently generate a high volume of letters for patients and other care providers, most of which are still sent in printed form. This project enables those letters to be delivered through the NHS App in digital form, with a fallback to printed letter.
59

610
## Table of Contents
711

812
- [NHS Notify Digital Letters](#nhs-notify-digital-letters)
9-
- [Table of Contents](#table-of-contents)
10-
- [Documentation](#documentation)
1113
- [Setup](#setup)
1214
- [Prerequisites](#prerequisites)
1315
- [Configuration](#configuration)
1416
- [Usage](#usage)
1517
- [Testing](#testing)
1618
- [Design](#design)
1719
- [Diagrams](#diagrams)
18-
- [Modularity](#modularity)
19-
- [Contributing](#contributing)
2020
- [Contacts](#contacts)
2121
- [Licence](#licence)
2222

23-
## Documentation
24-
25-
- [Built](/)
26-
- [Source](/docs/README.md)
27-
2823
## Setup
2924

30-
By including preferably a one-liner or if necessary a set of clear CLI instructions we improve user experience. This should be a frictionless installation process that works on various operating systems (macOS, Linux, Windows WSL) and handles all the dependencies.
31-
3225
Clone the repository
3326

3427
```shell
@@ -47,7 +40,7 @@ make debug
4740

4841
The following software packages, or their equivalents, are expected to be installed and configured:
4942

50-
- [Docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [Podman](https://podman.io/),
43+
- [Docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [Podman](https://podman.io/), [Rancher](https://rancherdesktop.io/)
5144
- [asdf](https://asdf-vm.com/) version manager,
5245
- [GNU make](https://www.gnu.org/software/make/) 3.82 or later,
5346

@@ -79,8 +72,6 @@ make config
7972
8073
## Usage
8174

82-
After a successful installation, provide an informative example of how this project can be used. Additional code snippets, screenshots and demos work well in this space. You may also link to the other documentation resources, e.g. the [User Guide](./docs/user-guide.md) to demonstrate more use cases and to show more features.
83-
8475
### Testing
8576

8677
There are `make` tasks for you to configure to run your tests. Run `make test` to see how they work. You should be able to use the same entry points for local development as in your CI pipeline.
@@ -89,44 +80,16 @@ There are `make` tasks for you to configure to run your tests. Run `make test`
8980

9081
### Diagrams
9182

92-
The [C4 model](https://c4model.com/) is a simple and intuitive way to create software architecture diagrams that are clear, consistent, scalable and most importantly collaborative. This should result in documenting all the system interfaces, external dependencies and integration points.
93-
94-
![Repository Template](./docs/diagrams/Repository_Template_GitHub_Generic.png)
95-
96-
The source for diagrams should be in Git for change control and review purposes. Recommendations are [draw.io](https://app.diagrams.net/) (example above in [docs](.docs/diagrams/) folder) and [Mermaids](https://github.com/mermaid-js/mermaid). Here is an example Mermaids sequence diagram:
97-
98-
```mermaid
99-
sequenceDiagram
100-
User->>+Service: GET /users?params=...
101-
Service->>Service: auth request
102-
Service->>Database: get all users
103-
Database-->>Service: list of users
104-
Service->>Service: filter users
105-
Service-->>-User: list[User]
106-
```
107-
108-
### Modularity
109-
110-
Most of the projects are built with customisability and extendability in mind. At a minimum, this can be achieved by implementing service level configuration options and settings. The intention of this section is to show how this can be used. If the system processes data, you could mention here for example how the input is prepared for testing - anonymised, synthetic or live data.
111-
112-
## Contributing
113-
114-
Describe or link templates on how to raise an issue, feature request or make a contribution to the codebase. Reference the other documentation files, like
115-
116-
- Environment setup for contribution, i.e. `CONTRIBUTING.md`
117-
- Coding standards, branching, linting, practices for development and testing
118-
- Release process, versioning, changelog
119-
- Backlog, board, roadmap, ways of working
120-
- High-level requirements, guiding principles, decision records, etc.
83+
![Digital Letters Process](./docs/diagrams/digital-letters-process.png)
12184

12285
## Contacts
12386

124-
Provide a way to contact the owners of this project. It can be a team, an individual or information on the means of getting in touch via active communication channels, e.g. opening a GitHub discussion, raising an issue, etc.
87+
NHS Notify Team
12588

126-
## Licence
89+
Ross Buggins - [[email protected]](mailto:[email protected])
12790

128-
> The [LICENCE.md](./LICENCE.md) file will need to be updated with the correct year and owner
91+
Thomas D'Roza - [[email protected]](mailto:[email protected])
12992

130-
Unless stated otherwise, the codebase is released under the MIT License. This covers both the codebase and any sample code in the documentation.
93+
## Licence
13194

132-
Any HTML or Markdown documentation is [© Crown Copyright](https://www.nationalarchives.gov.uk/information-management/re-using-public-sector-information/uk-government-licensing-framework/crown-copyright/) and available under the terms of the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/).
95+
The source code for the repository's documentation can be found under [/docs](docs) and is deployed by the CD pipeline to [NHS Notify Digital Letters](https://nhsdigital.github.io/nhs-notify-digital-letters).
195 KB
Loading

scripts/config/vale/styles/config/vocabularies/words/accept.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ Cyber
66
Dependabot
77
draw.io
88
drawio
9+
D'Roza
910
endcapture
1011
endfor
1112
endraw

0 commit comments

Comments
 (0)