Documentation for contributing content

[Scotchester]

Needing to be documented:

• [x] How to fork the manual and use Prose to make updates, then submit pull requests.
• [ ] How to keep one's fork up-to-date.
• [ ] Adding images.

[Scotchester]

Thoughts on where this documentation should live? The README is pretty stuffed to the gills already.

[ohsk]

How to keep one's fork up-to-date, according to @ascott1! https://github.com/cfpb/design-manual/wiki/Merging-your-fork-upstream

[Scotchester]

Ok, we have a start on this!

https://github.com/cfpb/design-manual/wiki/Content-editing-for-non-coders

[Scotchester]

Anyone have a chance to look at this yet? Let me know if it is easy to follow, or if you have any questions I didn't address in it. (Note: Some work still needs to be done, as evidenced by the unchecked items in the OP.)

[duelj]

IN reference to keeping your fork up to date:

Do we need to clone our fork locally in order to be able to "merge upstream" from terminal?

[mebates]

Love this documentation. Thanks @Scotchester !

[klocraft]

Successfully made my first update! Thank you @Scotchester, the instructions were very helpful!

[mebates]

Is this finished, @Scotchester ?

[mebates]

Still needs more work!

[caheberer]

@Scotchester should we continue to document this type of thing in the wiki?