[UXB-6] - Glossary Creation Steps

After content analysis AND the selection of the words to include in the glossary

</aside>

Conduct Research: Fully comprehend the meaning, context, and usage of each term.
Compare Definitions Across Platforms: Examine how each term is defined across different platforms and resources (where available).
Choose Alternative Phrases: Include alternative phrases and synonyms in the definitions to enhance clarity and ensure the glossary is accessible to a wider audience. Different users may be familiar with different terms for the same concept, so providing alternative phrases helps everyone understand exactly what is being discussed.
- Purpose: Adding alternative phrases makes it clearer exactly what we are talking about, as different people will be familiar with different terminology. This approach reduces confusion and bridges the gap between varying levels of familiarity with industry-specific language.
Example: If we prefer not to use the term “parachain” and instead want to standardize on using “blockchain” for all Polkadot parachains, we need to specify that in the definition of “blockchain.” By including “parachain” as an alternative term in the definition, users who are familiar with “parachain” will understand that it refers to the same concept as “blockchain” in this context.
- Implementation: In each definition, list alternative terms in parentheses or as “Also known as…” This ensures that users searching for any of these terms will find the relevant definition.
Create First Draft of the Glossary, including:
1. Terms
2. Alternative terms
3. Definitions
4. Instructions for usage. Eg.

IMPLEMENTATION NOTE: Never use the term parachain. Only people already in the Polkadot ecosystem know what a parachain is. Call your blockchain a blockchain or, in cases where space is limited in your UI, just “chain”

M3.1 - Workshop with stakeholders/community to present the progress

</aside>

Review for Consistency: Ensure consistency in style, language, terminology, etc., throughout the first draft.
Revise for Clarity: Refine the first draft to enhance clarity.
Revise for Conciseness: Make sure the definitions are succinct—we don’t want definitions that take up half a page.

M3.2 - User Testing

</aside>

Focus on User Needs: Once a solid draft is ready, ensure all chosen terms and definitions focus on the users’ needs and perspectives. A newcomer to Web3 should be able to understand everything with little to no additional research. If anything is too complex or uses other Web3 terms in its definitions, ensure those terms are also defined in the glossary or look for ways to revise for simplicity.
- Reasoning: Developers won’t be using the glossary to understand the terms—they already know blockchain terminology better than we do. Instead, they will be using the definitions either as tooltips or as starting points for their own documentation, tutorials, etc. That’s why it is crucial that the definitions are simple and user-oriented.
Provide Multiple Definitions if Necessary: In some cases, we may need to provide multiple definitions for us to choose between internally, e.g.:

Definition #1

> Blockchain (also chain, parachain) — a secure, decentralized technology that lets users directly and transparently conduct and verify transactions without the need for intermediaries, ensuring trust and data integrity in digital interactions.
> 

**Definition #2**

> Blockchain (also chain, parachain) — a technology that lets you securely, directly, and transparently exchange value or information online with others—without needing a middleman like a bank.
> 

*The second definition is obviously easier for non-Web3 users to understand, but we will need to decide which is more useful.*

M3.3 - Final presentation to stakeholders/community to validate the final Glossary V01

</aside>