Create a style guide
See original GitHub issueCreate a style guide for consistent documentation.
For example, my_function
vs my_function()
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Create a visual style guide for your brand - Canva
A comprehensive visual style guide has everything your audience needs to capture your brand, and your brand alone. Include layout references and examples...
Read more >Create a brand style guide for your business. - Adobe
A brand style guide is the rulebook for everything you create, from what fonts to use to how logo treatments work with different...
Read more >How to Create a Brand Style Guide in 5 Steps (Tips + Examples)
A style guide is simply the documentation of your brand identity, presented in a format that makes it easy to apply the identity...
Read more >How to create a brand style guide - 99Designs
How to create a brand style guide in 5 steps — · Step 1: Collect brand guide inspiration · Step 2: Define the...
Read more >Style Guide: How To Write One for Your Brand
All style guides should include an introduction. This might include a mission statement, letter from the CEO, about us page, or general overview ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For function names, macros etc we should look to how Rust does it, it’s deep enough that we should have some consistency with other Rust docs, assuming people have some familiarity with that already (or will have through reading the rust book first and things like that)
@joepetrowski on Riot, I think we agreed to use US English before 1.0 release, which prompted me to make this issue: https://github.com/paritytech/substrate/issues/1768