This repository was archived by the owner on Jul 19, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 46
This repository was archived by the owner on Jul 19, 2020. It is now read-only.
Adoptation of a formal style guide #74
Open
Description
To standardise the documentation and give a coherent and consistent reading for all readers, I think we should adopt a style guide (on a very informal basis – i.e. this is ideally what we want our documentation to look like but we'd rather have documentation not in keeping with the style guide than no documentation).
Something like The Chicago Manual of Style or Hart's Rules would do the trick.
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.