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.

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

Findings from Sara installing prototype kit #157

Open
LauraJD opened this issue Dec 2, 2024 · 1 comment
Open

Findings from Sara installing prototype kit #157

LauraJD opened this issue Dec 2, 2024 · 1 comment

Comments

@LauraJD
Copy link

LauraJD commented Dec 2, 2024

Sara tested installing and having an initial go at using the prototype kit.
Here are the main issues experienced:

  • 20 minutes seems like a long time to download - surprised it's this long
  • Not clear initially where to find terminal on a mac - need to look in the utilities file but this was not clear from the screen shot initially
  • Unsure what is meant by 'you will use a new copy of the kit for each new prototype'
  • Why is it called find-a-pharmacy? Is this just an example? A different example is used later on - should examples be aligned?
  • Step 5 - looks different to the screenshots for this - see Sara's screenshots
  • Was not expecting to download developer tools python as it does not say anything about this
  • What to do if there are errors? Mentioned in step 6
  • Should vulnerabilities in the code be addressed? What is the impact of this?
  • npm run watch - could be clearer what is going to happen at this stage - opens in the browser
  • 'You must install the prototype kit' - confusing as already been through steps to install it
  • Config js to change service name - does not work as expected. Service name is NHS UK prototype in Config js and this does not change the name on the prototype.
  • Can change prototype H1 by editing the code but not sure how to change title across all.

Sara's reflections:

  • I had some familiarity with Terminal and VS Code previously so recognised some of the screenshots/steps. I was OK with typing things in but don't always understand what I'm doing and why.
  • I can imagine some content designers struggling with this, without handholding - or perhaps video to refer to?
  • If I wasn't familiar with Terminal, I think I'd have been scared by all the code that shows when you type npm install - a long wall of code I don't understand.
  • I got a bit confused by the changes in language: "code editor", "HTML text editor", "VS Code". I think if we're encouraging people to use VS Code, perhaps just refer to that?

With the 3rd to last bullet point, we could be clearer that "You must install the prototype kit" is on the Before you start page in the Build a basic prototype tutorial. If you've just come from the Download and install guide, it's asking you to do something you've just done.

Once reviewed these issues may turn into a number of tickets to action.

@LauraJD LauraJD converted this from a draft issue Dec 2, 2024
@LauraJD LauraJD changed the title Findings from Sara installing and using prototype kit Findings from Sara installing prototype kit Dec 2, 2024
@vickytnz
Copy link
Contributor

vickytnz commented Dec 9, 2024

on reviewing the govuk versions, I think that the NHS version is very very behind. The GOV.UK version that is in parallel with ours had a couple of pages that explained instructions (and has been retained in the latest version)

How to install the kit
How to run the kit

Generally the approach in the govuk versions are entirely different fewer setup setps but more about explaining terminal.

I think that the entire install sections need a review to justify why they are so far away from the govuk version that is supposedly the same version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants