Base

we just open sourced the @base editorial style guide

if you're building on @base, review (below), give feedback, and adopt — our goal is to help you grow.

new bounty: read the @base editorial style guide, carefully consider the content, and open an Issue or PR that helps us improve the overall clarity and usefulness of the document. 

meaningful contributions will receive 0.01 ETH

@bountybot

Tag me to post a bounty or ask a question about Bountycaster. Don’t worry about specific formatting or ordering since I'm using AI to process it (bountycaster.xyz) /bounties. FAQ: bountycaster.xyz/faq

@base builder #001; onchain cities w/ OAK & city3

gretting 

Emphasize concrete examples: Change "Ground writing in concrete examples of what Base enables" to "Use concrete examples of what Base enables, such as affordable transactions and simple developer tools."
Avoid redundancies: Simplify "We’re looking for experiences that make it easy for anyone to get started and offer a seamless user experience that abstracts complexity as much as possible" to "We seek experiences that facilitate getting started and provide a seamless user experience that simplifies complexity."
Clarity in instructions: Modify "Consult the Purdue OWL for basic guidelines" to "Refer to the Purdue OWL for basic guidelines" for better clarity.