Adds documentation for upgrading the kit via the command line

[paulmsmith]

Adds documentation for upgrading kits via the command line with git. Thoughts? Please check and proof read.

[joelanman]

We've changed from 'updating' to 'upgrading' - probably best to stick to one throughout

[joelanman]

Elsewhere, we assume our primary user is someone who does not have technical experience - so I think we should do that here too and mention the manual instructions first as the common case.

[joelanman]

this is good work, and important as we don't have any instructions on what to do in the case of changes to /app. I think it's important to do some quick user research on this - ideally put it in front of a less confident, and a more confident user, and see if they can follow it. Would that be possible?

[paulmsmith]

I can find a few users of the kit in DWP that will be on 2.X release of the kit. I'll observe and see if there are any scenarios not covered in what I've written. Let's leave this PR open until I can report back.

[paulmsmith]

Made the changes based on your initial feedback @joelanman. Will see if I can get this tested by some appropriate users. Maybe you or others can too?

[paulmsmith]

Had a user with low confidence follow these, they were fine until merge conflicts. Initial fear replaced by 'I want to learn how to deal with this'. Maybe guidance around merge conflicts could be added?

[joelanman]

with the less confident user, did they understand that there was a more basic version for them to follow, and the advanced section was advanced? I'm not so worried if they can't actually follow all the advanced process

[paulmsmith]

I asked them to read the documentation for updating their prototype. Initial action was to update the manual way and that would have been the way they chose. Upgraded via the advanced method to see at what point they struggled, if at all. Only struggled when presented with merge conflicts, resolved them but with some struggle due to lack of visual diff tool and understanding around 'resolving' conflicts.

They read the github docs I've provided a link to but slightly misinterpreted the conflict markers (>>>>>>>>) which is a typical inexperienced user's issue with git conflicts.

[joelanman]

nice work, in that case I'll try and get another pair of eyes on it tomorrow and see if we can get it merged

[joelanman]

many apologies for leaving this so long - couple of things:

Can we stick to 'Update' or 'Upgrade' throughout? NPM refers to update, so maybe that?

also I'm not sure if this line is useful?

The steps below 'Upgrading' describe how to upgrade to the latest release of prototype kit.

[paulmsmith]

@joelanman Good points. Changes made.

[joelanman]

thanks @paulmsmith 🍰