-
Notifications
You must be signed in to change notification settings - Fork 11
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
2024 01 17 new features readme layout and content #130
Merged
C-Harry
merged 25 commits into
main
from
2024-01-17-New-features-README-layout-and-content
Jan 17, 2024
Merged
2024 01 17 new features readme layout and content #130
C-Harry
merged 25 commits into
main
from
2024-01-17-New-features-README-layout-and-content
Jan 17, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Includes an overview of why we split our work to start from prototypes testing whole journeys and then moved on to feature focussed work.
Used the “what” from each feature README page as the description. If we want to change these descriptions to make them higher level then we should look at updating in both places
- Added some positive contractions etc. - Split a few sentences up to make them shorter - Added a definition of 'early access'
Made some small tweaks to shorten sentences etc.
…ntent-updates Update README.md - minor tweaks for readability and house style
…ntent-updates-2 Update README.md - small tweaks for readability
C-Harry
approved these changes
Jan 17, 2024
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.
Looking good I think!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
What
README.md
to the/design
directory to add a little explanation of what it is for and how we use it/features/README.md
file to remove mention of not testing them in the prototype (because we have for some), and added links and descriptions for all the features we have documentedprototype-tested.md
file names for the prototype version toREADME.md
so the content displays if the user goes to a version directoryHow to review
Who can review
Anyone in the team can review, especially as most of it is file renames and removals.
But content review of the new
design/README.md
and updated content of thefeatures/README.md
would be welcomed!