Adding information about using GitHub and GitHub Desktop

[vickytnz]

Ported over the GOV.UK Prototype Kit guides:

1. Store your code online with GitHub and GitHub Desktop
2. Store your new prototype in GitHub
3. Download an existing prototype from GitHub4. Collaborate on prototypes using GitHub Desktop

Reformatted the guides page to have a section.

I do wonder if it would be better to reconfigure the install section to just be about Github or somehow pull the downloading someone else's prototype earlier with an easier through-line.

This could also align with @paulmsmith's work on Codespaces.

Pages:

How to (changed to 3 columns) and with some new ideas

Store your code online with GitHub and GitHub Desktop

Store your new prototype in GitHub

Download an existing prototype from GitHub

Collaborate on prototypes using GitHub Desktop

[vickytnz]

I'm also now wondering how much this needs to be "NHSed" to at least note that this should usually be done with official NHS repositories and with our processes. DfE does similar with their guidance for design ops

https://design.education.gov.uk/design-system/github-heroku

[vickytnz]

Version now ready for review

How to page with new section

Store your code online with GitHub and GitHub Desktop

Similar to GOV.UK page but some tweaking and addition of NHS England info and a course correct to start with installing as needed

Using GitHub if you work for NHS England

NEW PAGEThis is trying to have just enough information without duplicating stuff that is in Sharepoint organisations. Main thing is to encourage people to set up Github early rather than go rogue.

Store your new prototype in GitHub

As per the GOV.UK version with extra linking to other sections.

Download an existing prototype from GitHub

As per the GOV.UK version with extra linking to other sections.

Collaborate on prototypes using GitHub Desktop

As per the GOV.UK version. This hasn't been changed.

[vickytnz]

Latest version included comment fixes but also uses the 'mini-hub component. This makes it easier to see the steps (though it does make me wonder if the NHS England one is in the right place)

Two things I am considering:

1. I'm not entirely sure about the split on the first few pages. Maybe the first page should be Overview with just the concepts and even have a separate page just about creating a GitHub account which could then allow for all the NHS England information to go there?
2. I have also noticed that this pattern is different from the one for the basic prototype which is more like a transactional thing (namely the title hint has switched from above to below) - not sure if this needs to get fixed

[vickytnz]

After more reviews I've done a complete redo to:

Redo the how-to page

Overview page (new)

This is now just about the basic stuff but also links over to the git terminal information

Set up GitHub and GitHub Desktop

This page:

• takes what was the second part of the initial setup page
• added details about installing git as that was missing (PS I hope these instructions work)
• merges the NHS England stuff and cuts it down a lot (I've removed stuff about other orgs and other repos)

Store a new prototype on GitHub

This page adds course corrects to other starting points (new prototype and the github setup)

Download an existing prototype from GitHub

Linking to previous pages

Collaborate on a prototype

Only remaining things for me are:

• consistency of titles (maybe it's overkill on the Github stuff and titles could be just 'Download an existing prototype' etc)
• overall consistency of titles with other sections (e.g. the subheader is different here to the basic prototype)

[frankieroberto]

@sarawilcox would you mind reviewing this too?

[sarawilcox]

Hi @frankieroberto , I've reviewed this and have made a few tiny tweaks. Probably best to publish it as is. I haven't had a chance to test the process myself.

The main change I made was to make people aware that there are 2 main GitHub orgs for NHSE: the NHS Digital one and the NHS.UK one. (There may be more for all we know.)

I think we need to review this when we look at publishing content about CodeSpace - both where it sits in the IA and how we document some content (e.g. commands) that will be common to both.

[sarawilcox]

I did notice that <code>main</code>, for example, displays differently from how it does in the design system. This way of displaying it wasn't very obvious to me.

Compare with <code> in the design system.

[frankieroberto]

I did notice that <code>main</code>, for example, displays differently from how it does in the design system. This way of displaying it wasn't very obvious to me.

Good point. I think we should tackle this as part of #21 and make the styles for code examples consistent with the service manual. 👍