

Subscribe to Onchain spotlight
Subscribe to Onchain spotlight
Share Dialog
Share Dialog
Hello builders, How much do you know about the Base Editorial Style Guide? Or does it seem unnecessary to have a regulatory guide for contents, promotions etc on Base?
Well, It is absolutely necessary. The Base Editorial Style Guide is a documentation of the acceptable naming conventions, writing guidelines and general do's and don'ts for non-technical contributors on Base. It exists to:
Ensure baseline quality and consistency across all media types
Help all contributors maintain editorial standards
Align all communications from Base tonally.
Write 'Base' not 'BASE', 'Base Chain' or Base Network
Use 'onchain' instead of 'crypto', 'web3' etc and it is spelt 'onchain' and not hyphenated or separate
Use technical terms sparingly and explain well when you do
Use ETH and not USD to emphasize global economy
Brands should supercede Base i.e (BRAND x Base, not Base x BRAND) in logos.
Emphasize Base's vision and mission (bringing a billion people onchain)
Highlight progress and next steps
Leave out abstract concepts and give concrete examples
Prioritize clarity to ensure that the content is understandable by all. Opt for simpler words and use active voice over passive
Be concise. Avoid redundant sentences and if you need improvement on those areas, you can consult the Purdue OWL page on https://owl.purdue.edu/owl/general_writing/academic_writing/conciseness/index.html
Celebrate builders when possible
Use a progressive, conversational, direct and realistic voice
Use a conversational, unique, direct and compelling tone
These are slight variations on writing conventions that are used on Base.
Base follows the Purdue OWL guidelines on capitalization which capitalizes:
The first words of a sentence,
The pronoun 'I',
Proper nouns
Directions that are names. Example: 'They moved to the Southwest
Periods and event etc
For more guidelines, check out the Purdue OWL .
Here, use title case, not sentence case. The first letter of each major word is capitalized. Example: Base is for Everyone.
Base uses the Oxford comma — the comma after the penultimate item in a list of items. Example: I love bananas, apples, and oranges. the oxford comma is the one after apples. This is the accepted convention on Base.
Em Dashes ( — ) - They should have spaces on both sides.
Ampersands (&) - should only be used in business names and not as a substitute for the word 'and'.
Write numerals 0 - 9 as words
Write numerals 10 above as Arabic numerals
Abbreviate 10,000 and above with k
Write dates in shortened form
Always refer to time with respect to the period of the day and time zone. Example: 7am ET
Use lowercase version number prefix for software. Example: v1, v2.3 etc
Avoid:
Using financial terminology - terms indicating 'gains', 'high-yields', 'investments' etc as they could convey the wrong message about Base
Disputable Superlatives - avoid using unverified superlatives like 'the fastest performing', 'the best' etc
Unapproved partnerships
Non-Compliant Contests or DeFi Offers - Do not offer contests, sweepstakes or DeFi applications without the appropriate regulatory terms and conditions
False Information - Ensure all disseminated information is verified
Negative Comparisons - Do not put down other competitors while promoting Base
Offensive Language - Do not use fowl language in any communication
Now count out on your fingers the number of times you have flouted these rules... Well, not anymore.
Check out the Base Editorial Style Guide here so we all help tell the Base story consistently https://github.com/base-org/brand-kit/blob/main/guides/editorial-style-guide.md
Happy building!!!
Hello builders, How much do you know about the Base Editorial Style Guide? Or does it seem unnecessary to have a regulatory guide for contents, promotions etc on Base?
Well, It is absolutely necessary. The Base Editorial Style Guide is a documentation of the acceptable naming conventions, writing guidelines and general do's and don'ts for non-technical contributors on Base. It exists to:
Ensure baseline quality and consistency across all media types
Help all contributors maintain editorial standards
Align all communications from Base tonally.
Write 'Base' not 'BASE', 'Base Chain' or Base Network
Use 'onchain' instead of 'crypto', 'web3' etc and it is spelt 'onchain' and not hyphenated or separate
Use technical terms sparingly and explain well when you do
Use ETH and not USD to emphasize global economy
Brands should supercede Base i.e (BRAND x Base, not Base x BRAND) in logos.
Emphasize Base's vision and mission (bringing a billion people onchain)
Highlight progress and next steps
Leave out abstract concepts and give concrete examples
Prioritize clarity to ensure that the content is understandable by all. Opt for simpler words and use active voice over passive
Be concise. Avoid redundant sentences and if you need improvement on those areas, you can consult the Purdue OWL page on https://owl.purdue.edu/owl/general_writing/academic_writing/conciseness/index.html
Celebrate builders when possible
Use a progressive, conversational, direct and realistic voice
Use a conversational, unique, direct and compelling tone
These are slight variations on writing conventions that are used on Base.
Base follows the Purdue OWL guidelines on capitalization which capitalizes:
The first words of a sentence,
The pronoun 'I',
Proper nouns
Directions that are names. Example: 'They moved to the Southwest
Periods and event etc
For more guidelines, check out the Purdue OWL .
Here, use title case, not sentence case. The first letter of each major word is capitalized. Example: Base is for Everyone.
Base uses the Oxford comma — the comma after the penultimate item in a list of items. Example: I love bananas, apples, and oranges. the oxford comma is the one after apples. This is the accepted convention on Base.
Em Dashes ( — ) - They should have spaces on both sides.
Ampersands (&) - should only be used in business names and not as a substitute for the word 'and'.
Write numerals 0 - 9 as words
Write numerals 10 above as Arabic numerals
Abbreviate 10,000 and above with k
Write dates in shortened form
Always refer to time with respect to the period of the day and time zone. Example: 7am ET
Use lowercase version number prefix for software. Example: v1, v2.3 etc
Avoid:
Using financial terminology - terms indicating 'gains', 'high-yields', 'investments' etc as they could convey the wrong message about Base
Disputable Superlatives - avoid using unverified superlatives like 'the fastest performing', 'the best' etc
Unapproved partnerships
Non-Compliant Contests or DeFi Offers - Do not offer contests, sweepstakes or DeFi applications without the appropriate regulatory terms and conditions
False Information - Ensure all disseminated information is verified
Negative Comparisons - Do not put down other competitors while promoting Base
Offensive Language - Do not use fowl language in any communication
Now count out on your fingers the number of times you have flouted these rules... Well, not anymore.
Check out the Base Editorial Style Guide here so we all help tell the Base story consistently https://github.com/base-org/brand-kit/blob/main/guides/editorial-style-guide.md
Happy building!!!
<100 subscribers
<100 subscribers
This week I built: I attended the writers workshop last week where I got to know about the Base Editorial Style Guide. I'm aware most builders don't know there are rules to be kept while contributing on Base so I minted all I gathered from it on paragraph 👇
4 comments
This week I built: I attended the writers workshop last week where I got to know about the Base Editorial Style Guide. I'm aware most builders don't know there are rules to be kept while contributing on Base so I minted all I gathered from it on paragraph 👇
https://paragraph.xyz/@ucheasogwa/the-base-editorial-style-guide
Nice one mate 💙
Nice