📖Editorial and Style Guide

Use this framework as a guide for creating content that is not only informative but also reflects our core values of Canopy.

To foster a community of high-quality contributors and ensure clear, consistent communication, this guide establishes the editorial standards for all Canopy Network content. By adhering to these principles, we can collectively reinforce our commitment to quality, transparency, and impactful collaboration.

A consistent voice and style are crucial for building trust and recognition. This guide ensures that all content created by and for the Canopy Network community meets a high standard of quality, clarity, and professionalism. It is a living document, intended to evolve as our network grows and our communication needs change.

Inspired by the work of Starbased (Danica Swanson) and the Base brand kit, this guide empowers our community members by providing a framework for creating content that is not only informative but also reflects our core values: clarity, conciseness, professionalism, honesty, and providing context without hype or exaggeration. We encourage a self-starting and self-directed approach, and this guide is a key resource to support that initiative.

About Canopy

Canopy is a recursive security network and building framework designed to eliminate the need for layers and guarantee true digital sovereignty. By creating a more secure, streamlined, and scalable environment, Canopy empowers developers to build the next generation of decentralized applications with confidence and efficiency.

Style Conventions

To maintain a clear and consistent brand identity, please adhere to the following naming conventions:

• Branding: Always refer to the project as Canopy, not Canopy Network, $CNPY, or any other variation. For logos and visuals, please refer to the Brand Kit.

• Nested Chains: Applications designed and built as application-specific blockchains are referred to as Nested Chains. Do not use subnet, subchain, or any other variation.

• CNPY: Canopy's native token is CNPY, pronounced "Canopy".

• Native Tokens: Nested Chain tokens (if applicable) are referred to as Native Tokens.

What to Avoid

To maintain our standard of clear, honest communication, please avoid the following:

• Jargon and technical terms: If a technical term is necessary, always provide a clear and concise explanation.

• Hype: Our work is important, and its value should be communicated through facts and clear outcomes, not superlatives or sensationalism.

• Vague or Abstract Language: Be specific and provide concrete examples and actionable advice.

• Speculation or unsubstantiated claims: All information should be accurate and verifiable. Cite the sources of any data presented.

• Using Financial Terminology: Avoid using financial terms such as gains, profits, investments, high yields, leverage, etc. Do not offer investment recommendations or strategies.

• Token Focus: When discussing Canopy, highlight its comprehensive vision beyond the utility of the token. In your content, integrate the token's role within the broader objectives, rather than centering the discussion solely on the token itself.

• Mentioning Specific Tokens: Focus on your utility, value, or experience instead of specific tokens, token rewards, etc.

• Lack of Context: It’s always someone's first time, once. Avoid solely focusing narrowly, without providing readers an understanding of the context of your/our underlying project.

• Approved Project Descriptions: Use phrases like "launched on Canopy," "built on Canopy," or "integrated with Canopy" instead of terms like “partnership” or “collaboration” with Canopy.

• NSFW Content: Refrain from using offensive, NSFW, or explicit language or content in any communication, including your website.

• Unlicensed IP: Remove any IP in your post and website that is not properly licensed.

Content Guidelines

• Emphasize Canopy's vision and mission: Canopy has a grand vision to create a new foundation for decentralized systems and a mission to build a global framework for sovereign applications. Highlight how Canopy aims to make this secure future more accessible for every developer and user, everywhere.

• Highlight progress and what’s next: When discussing Canopy's ongoing developments, celebrate recent milestones and accomplishments in building out the network. Outline the priorities and initiatives planned for the current or upcoming period, grounding them in Canopy's overarching vision and mission. Invite collaboration from the community, fostering an environment where external perspectives can contribute ideas and feedback.

• Focus on concrete examples over abstract concepts: Avoid excessive abstract language about "the future of security" or overly technical language around "cryptographic primitives," etc. Ground writing in concrete examples of what Canopy enables: Day 1 security, seamless dApp deployment, simple developer tooling, sovereignty, etc.

• Use clear examples to illustrate concepts: While technical depth is unavoidable, aim to make abstract concepts like "recursive security" accessible through clear examples and analogies. Compare new paradigms (like layerless architecture) to familiar ones (like traditional layered security) to build understanding. Use specifics and walk through sample user or developer flows to demonstrate core value propositions.

• Whenever possible, celebrate builders: Canopy exists to empower those building a sovereign future, and "building" can be defined with a wide net: developers, security researchers, creators, writers, and community leaders. Frequently highlight and celebrate the projects, people, and communities utilizing the Canopy framework.

• Be a bridge: Assume your audience includes newcomers to decentralized technology. Use analogies and examples to make clear connections between the tools and platforms people know today and the more secure, sovereign future Canopy is building.

Voice

Our content should always be:

• Clear and Concise: Use simple language and sentence structures. Get to the point quickly and avoid unnecessary words.

• Professional: Maintain a respectful and knowledgeable tone.

• Honest and Transparent: Be upfront about what we know and what we don't. Acknowledge uncertainties and challenges.

• Contextual: Ensure all information is presented with relevant background to aid understanding. Explain the "why" behind the "what."

• Action-Oriented: Whenever possible, provide clear next steps or calls to action for our audience.

Tone

Our tone should reflect our values and our commitment to our community. It should be:

• Empowering: We want our audience to feel capable and equipped to take action.

• Approachable: While professional, our tone should be welcoming and accessible to a broad audience.

• Authoritative but not Arrogant: We are experts in our field, but we communicate our knowledge with humility and a genuine desire to help.

• Pioneering: We are building something new and foundational. Our tone should be confident, forward-looking, and inspiring.

• Pragmatic: While visionary, our communication must be grounded in reality. We are engineers and builders speaking to the same.

• Intellectually Honest: Acknowledge complexities and challenges openly. Our community values rigor and transparency.

• Empowering: We want developers and users to feel they have the ultimate tools for security and sovereignty.

Writing Guidelines

To ensure consistency and readability, please follow these grammatical guidelines:

• Use the Oxford comma: In a series of three or more items, use a comma before the final "and" or "or."

• Titles: Use title case for headings and subheadings.

• Acronyms: Spell out the full name of an organization or term on its first use, followed by the acronym in parentheses. Subsequent mentions can use the acronym.

• Numbers: Spell out numbers one through nine. Use numerals for 10 and above.

Standard of Quality

For contributors engaged in the creation and promotion of content who aspire to receive broader amplification and reach a wider audience, we kindly request that content producers deliver material of the utmost quality. High-quality content not only reflects well on individual creators but also upholds our community's standards and brand integrity.

To assist you in understanding our definition of high-quality content, we encourage you to view examples available on our official accounts. These samples serve as benchmarks and guidelines that align with our established expectations and can guide you in crafting exceptional content.

It is important to note that content that fails to meet our established quality benchmark will not be eligible for promotion through official Canopy channels. We reserve the right to reject content that does not meet our standards, with reasons for rejection including, but not limited to, the following: failure to adhere to all Content Guidelines, Writing Guidelines, Tone, and Voice requirements. Additionally, content may be rejected upon review and objection by the Canopy Legal team.

Credits

This style guide was developed with deep appreciation for the foundational work of:

• Starbased (Danica Swanson): For providing a comprehensive and insightful framework for editorial excellence.

• Base: For their open and collaborative approach to brand and communication guidelines.

By embracing this style guide, we can all contribute to a stronger, more unified Canopy, empowering our community and advancing our mission of creating a safer, more resilient world.