Overview
| Artifact ID: | c875f26773f86bc207e77efcc99a7866fc3ca8ffa1ba17fae49e8298a0f4f365 | 
|---|---|
| Page Name: | Style Guide | 
| Date: | 2018-08-27 19:29:45 | 
| Original User: | joel | 
| Parent: | b4adbd218e1a312620a1750f179ec0bd40c1949c3144aadbdf4b2684e4a25fc8 (diff) | 
| Next | 2f5ce2a9231e2fef0986b77d796ba11ca5d20056e6599fd3abc0d81014f77991 | 
Content
These are notes for my own use.
Prose
- The Local Yarn should be italicized.
 - The Local Yarn is emphatically not “a web site”.
 
Punctuation
- In a list of actions, list items should end with a period.
 - In a list of things, list items should not end with a period.
 - Place trailing commas and periods outside of quotation marks unless they are part of the quoted text.
 - Em- and en-dashes, “smart” quotes and apostrophes, emoji, and math symbols should be stored as such in the original text source. Do not rely on smartypants-style text processing at any step after writing to produce typographically correct punctuation.
 
Source files
- Header comment includes copyright notice, license information, and author contact info.
 - (Racket) All comments on their own line begin with 
;; 
Pre-commit checklist
- Run 
fossil changes --differto ensure no extra files need to be added. - Run 
fossil diff --tkto ensure all edits are related. - If any files have been added with 
fossil add, ensure the makefile is up to date. - Ideally, any documentation (Scribble files) should be updated at the same time as the source code.
 - Make sure you’re on the correct branch.
 
Commit messages
- Commit messages should use the imperative voice.
 - Commit messages should be no more than ≈ 50 characters long.
 - If more explanation is needed, create a ticket and cross-reference it with the commit message.
 - Link a commit to a related ticket by using brackets 
[ ]containing at least the first 6 digits of the UUID. - Comments added to tickets in connection with a resolving check-in should describe why the change was made, not how (the code does that part already).