good-gym / yoti-dbs Goto Github PK

• It would be great to have a back link on some of the pages, in particular when the user might be going back and forth between areas/times
• Can we have the address for the Mission Summary page? e.g. for Islington it would be:
  Highbury Pool, Highbury Crescent, London, N5 1RR
• On the "Select a time page" can we change the copy from Next available mission slots at our Islington meeting point: to Next available mission slots in Islington:
• It would also be great to have a link at the bottom in case the user can't make the time, such as Can't make these? Schedule a time to meet us (edited)
• Also it would be great to have a Add to Calendar link/button on the mission confirmed page - it doesn't have to do anything

Allows you to style placeholder text in input fields

Please thumb up this to indicate you understand. Raise questions in this issue if you run into any problems or come find me.

1. Create an issue for the task you are working on:

• user-story: "as a... I want... so that..."
• list the technical tasks involved in completing it, either within the issue itself, or as separate issues that refer to the main issue and are given a 'technical' label.

2. Estimate how long it will take you to finish the issue and add the appropriate time label (t1h = 1 hour, t1d = 1 day, etc). If a user-story will take you longer than a day then its too big. Break it down into smaller issues.
3. Give the issue a priority label.
4. Assign yourself to the issue you're working on and add the 'in-progress' label.
5. When you make commits give appropriate descriptions of the technical task it completes and refer to the issue number in the commit message. (e.g. 'related #7'). Aim for small commits that complete a single task.
6. When the PR is ready for review:

• Assign to your team-mates to review first (if you aren't pair programming)
• Assign the PR to me and change the issue label to 'awaiting-review'. Give the PR an appropriate description listing the technical tasks it completes.

7. When the PR is closed, and once you're satisfied an issue is complete and on the live version of the project, change the label to 'please-test' and assign it to your product owner. This is to indicate to the product owner that they should check if they are satisfied the work is done.

• If they are not satisfied, they should detail in the issue what needs to change. Un-assign them, remove the please-test label, and return to step 2.
• If they are satisfied, they can close the issue.

Not the main focus: e.g. a summary and a link to more details are enough.

Do you have everything you need for a background check?
You need to show us three documents including valid photo ID and proof of address.

The easiest combination is:

Valid Passport
Valid Driving Licence photocard
Proof of current address, e.g.
bank statement (dated within last 3 months)
utility bill (dated within last 3 months)
council tax bill (dated within last 12 months)
There are lots of other documents you can show us if you don't have these. 
Have a look on the DBS website for the full list of document combinations. 
Get in touch if you need help.

We must see the original documents - we can't accept copies. 
Find out what to do if your bills and accounts are paperless.```

So that I can seamlessly share my availability to check documents.