-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Style Guide #4741
Comments
It's probably out of date but the wiki has one from 2018 |
Thank you -- that'll be a good start. |
This issue is marked as stale due to no activity within 30 days. If no further activity is detected within 7 days, it will be unassigned. |
Still on my plate |
Limiting this to a style guide for the user documentation. The style guide from the wiki above deals with the app itself. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Create a style guide
Why?
Consistency. Save time on review of current materials
Details
It doesn't have to be extensive, but it would cover things like:
Ultimately, we might like to have this "live" -- in that we can show actual examples -- that is, it would be an erb.
Linked to from Contributing.md
Thoughts?
The text was updated successfully, but these errors were encountered: