Start here
Build a plain-language mental model before reading technical specifications. The foundations guide explains the vocabulary used throughout the site.
Open glossary →LEARNING PATHS
Guides for understanding Solana
Gajema guides are structured reading paths for people arriving from different backgrounds. A beginner may need a vocabulary and a mental model, while a developer may need clearer boundaries between a program, an account, an endpoint, and an interface. Each guide states its scope so a reader can choose an appropriate starting point.
The guides are informational. They do not provide financial, legal, tax, investment, or security advice, and they do not replace current official documentation or professional review. Use them to organize questions, then verify details before relying on them.
Choose a path
- Foundations: terms, transaction flow, accounts, programs, and network roles.
- Architecture: how the main technical components relate to one another.
- Infrastructure: operation, endpoints, maintenance, monitoring, and evidence.
- Development: software workflow, testing, permissions, and documentation.
Go deeper
Follow the architecture path when you want to understand data objects, programs, instructions, validation, and operational boundaries.
Read architecture →Apply questions
Use the developer and infrastructure pages to turn abstract concepts into review questions for software and service documentation.
Read developer notes →Guide comparison
| Guide | Reader profile | Questions answered | Suggested next step |
|---|---|---|---|
| Foundations | New reader | What do the core words mean? | Glossary |
| Architecture | Technical learner | How do components interact? | Infrastructure |
| Developers | Builder or reviewer | What should be tested and documented? | Security |
| Research | Analyst or journalist | How should evidence be interpreted? | Editorial policy |
Reading checklist
- Read the scope and review date.
- Mark unfamiliar terms and open the glossary.
- Separate descriptive statements from interpretation.
- Follow primary sources before making a consequential decision.
- Send a correction when a material detail appears outdated.
“A guide should reduce confusion without hiding the parts that still require careful reading.”
How to move between pages
Use the architecture guide for system relationships, the infrastructure guide for operational layers, the developers page for software questions, and the research page for evidence. Community and editorial pages add context about how knowledge is created, checked, and maintained.
- Use short pages for orientation.
- Use tables for comparison.
- Use source notes for verification.
- Use contact.php for corrections or accessibility requests.