-
Notifications
You must be signed in to change notification settings - Fork 9
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
PP-12251: Adds some signposting to some API-only features #956
Conversation
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.
Looks great. Just a few suggestions.
Co-authored-by: asimms41 <[email protected]>
Co-authored-by: asimms41 <[email protected]>
@@ -9,6 +9,8 @@ weight: 2100 | |||
|
|||
This section tells you how to take a payment using the GOV.UK Pay API. | |||
|
|||
If you want to take payments using a no-code solution instead, you can use [payment links](https://www.payments.service.gov.uk/govuk-payment-pages/). |
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.
what is the purpose of "instead" here? I am wondering if it works the same just with "If you want to take payments using a no-code solution, you can use..."
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.
Good point. Services can use both - I'll adjust.
@@ -19,6 +21,8 @@ Your service has [additional responsibilities when taking recurring payments](/r | |||
* telling users when you’re going to take or change payments | |||
* letting users amend their recurring payments | |||
|
|||
It would be helpful to familiarise yourself [the standard GOV.UK Pay payment flow](/payment_flow) before reading about recurring payments. | |||
|
|||
This section outlines the recurring payment flow, your responsibilities, and how to set up and use agreements to take recurring payments. |
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.
"This section explains"? I think "outlines" is a bit of a policy word, dangerously close to "sets out" :)
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.
'explains' is clearer English - good spot!
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.
All serving suggestions from me, but please check that typo on recurring_payments line 24
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.
Looks good
Context
A lot of the pages in the tech docs have pre-requisites that we don’t really spell out. For example, ‘Take recurring payments’ makes more sense if readers have an understanding of how standard payments work. Similarly, ‘Take a payment’ requires users to have some technical knowledge to understand how APIs work.
Changes proposed in this pull request
This PR:
Guidance to review