-
Notifications
You must be signed in to change notification settings - Fork 0
RESOURCES.md
Document Type: Official Resource Directory Project: CeloHT Status: Active Last Updated: August 2026 Authors: Johnny Dubic & CeloHT Community
This document provides a structured directory of resources related to CeloHT, its educational programs, technology, community initiatives, environmental work, governance, and the Celo ecosystem.
The purpose is to make important information easier to discover, verify, and use.
Resources listed by CeloHT should be reviewed periodically to ensure that outdated, broken, or misleading information is removed or clearly identified.
CeloHT resources should be:
- Relevant
- Accessible
- Accurate
- Secure
- Clearly categorized
- Maintained
- Properly attributed
- Appropriate for the intended audience
Where an external resource changes over time, CeloHT should avoid presenting outdated information as current.
Primary CeloHT resources may include:
- Official website
- GitHub organization
- GitHub repositories
- CeloHT Wiki
- Documentation
- Educational materials
- Whitepapers
- Research publications
- Community resources
- Press and media materials
Official resources should be clearly distinguished from third-party information.
GitHub serves as a major technical and documentation platform for CeloHT.
CeloHT repositories may contain:
- Source code
- Documentation
- Issues
- Pull requests
- Releases
- Technical specifications
- Development resources
- Research materials
Repository permissions should be managed according to CeloHT governance and security practices.
CeloHT documentation may include:
README.mdARCHITECTURE.mdSYSTEM_DESIGN.mdTECH_STACK.mdSECURITY.mdGOVERNANCE.mdCONTRIBUTING.mdUSER_GUIDE.mdQUICK_START.mdTUTORIALS.md
Documentation should be updated when material project functionality changes.
CeloHT educational resources may cover:
- Financial literacy
- Blockchain fundamentals
- Web3
- Digital wallets
- Celo
- cUSD
- CELO
- Digital security
- Entrepreneurship
- Environmental education
Educational materials should be appropriate to the learner's level.
CeloHT may provide introductory resources explaining:
- Blockchain
- Decentralization
- Wallets
- Smart contracts
- Digital assets
- Transactions
- Network fees
- Decentralized applications
- Governance
Beginners should be encouraged to understand security fundamentals before performing real transactions.
Financial education resources may address:
- Budgeting
- Saving
- Spending
- Risk management
- Digital payments
- Remittances
- Financial planning
- Fraud awareness
CeloHT educational content should not be interpreted as personalized financial advice unless explicitly provided under an appropriate professional framework.
For Celo-specific technical information, users should consult current official Celo documentation and ecosystem resources.
CeloHT materials should be periodically reviewed against current Celo network functionality to reduce the risk of outdated technical instructions.
Wallet education may cover:
- Wallet creation
- Recovery phrases
- Private keys
- Transaction confirmation
- Network selection
- Address verification
- Security practices
Users should never be instructed to disclose private keys or recovery phrases.
Developer resources may include:
- Programming documentation
- GitHub repositories
- API documentation
- SDK documentation
- Smart-contract documentation
- Testing guides
- CI/CD documentation
- Security guidelines
Developers should use the version of documentation appropriate to the software they are building.
Smart-contract resources may include:
- Solidity documentation
- OpenZeppelin documentation
- Celo developer documentation
- Contract source code
- Deployment records
- Verification records
- Security reviews
Users should distinguish between verified contract source code and unverified third-party claims.
Blockchain explorers can help users inspect:
- Transactions
- Addresses
- Blocks
- Smart contracts
- Token activity
- Network information
CeloHT should identify the relevant network when linking to blockchain explorer resources.
Security education should cover:
- Phishing
- Social engineering
- Fake wallets
- Fake support accounts
- Malicious links
- Private-key protection
- Recovery phrase protection
- Transaction verification
- Device security
Users should verify information through trusted official sources.
Research resources may include:
- Academic publications
- Research datasets
- Government data
- International development reports
- Blockchain analytics
- Environmental studies
- Financial inclusion studies
- Community research
Research materials should include citations where appropriate.
Environmental resources may cover:
- Reforestation
- Tree planting
- Agroforestry
- Biodiversity
- Soil conservation
- Water protection
- Climate resilience
- Environmental education
CeloHT should favor evidence-based environmental information.
The CeloHT Reforestation Program may maintain resources covering:
- Species selection
- Nursery management
- Planting
- Maintenance
- Monitoring
- Survival measurement
- Community participation
See REFORESTATION.md for the program framework.
Community resources may include:
- Educational events
- Workshops
- Community meetings
- Volunteer information
- Training materials
- Program registration
- Community announcements
Community resources should clearly identify whether they are official CeloHT materials or independently created resources.
Potential volunteer resources include:
- Volunteer onboarding
- Code of conduct
- Program descriptions
- Training materials
- Community guidelines
- Contribution procedures
Volunteers should understand their responsibilities before participating in activities.
Technical contributors may use:
CONTRIBUTING.md- Issue templates
- Pull-request templates
- Development documentation
- Testing documentation
- Security guidelines
- Coding standards
Contributors should follow repository-specific instructions.
Governance resources may include:
GOVERNANCE.md- Voting procedures
- Working groups
- Proposals
- Treasury policies
- Conflict-of-interest policies
- Community decisions
Governance information should be transparent and versioned where appropriate.
Where treasury information is publicly disclosed, resources may include:
- Treasury reports
- Funding policies
- Approved allocations
- Expenditure reports
- Financial summaries
- Relevant blockchain addresses
Sensitive financial or security information should not be disclosed merely for transparency.
CeloHT may maintain resources for:
- Partnerships
- Sponsors
- Collaborators
- Community organizations
- Environmental partners
- Technology partners
Partnership claims should accurately represent the relationship and its current status.
Media resources may include:
- Press kit
- Logos
- Brand guide
- Official images
- Founder information
- Project descriptions
- Contact information
- Approved statements
Brand assets should be used according to CeloHT's branding guidelines.
CeloHT publications may include:
- Whitepapers
- Research reports
- Articles
- Technical papers
- Educational guides
- Program reports
- Environmental reports
Publications should identify their date and status.
New users should have access to a simple path:
Start Here
↓
Understand CeloHT
↓
Learn Web3 Basics
↓
Learn Wallet Security
↓
Explore Celo
↓
Use Educational Resources
↓
Join the Community
See QUICK_START.md for the recommended onboarding path.
User guides should help participants understand how to use relevant CeloHT services.
Possible topics include:
- Account setup
- Wallet connection
- Education platform
- Agent services
- Transactions
- Support
- Security
Instructions should be tested against the current version of the relevant product.
Tutorials should provide practical step-by-step guidance.
Each technical tutorial should ideally identify:
- Prerequisites
- Required software
- Versions
- Steps
- Expected result
- Troubleshooting
- Security considerations
Frequently asked questions may address:
- What is CeloHT?
- What does CeloHT do?
- How can someone participate?
- What is Celo?
- What is cUSD?
- How do wallets work?
- How can someone contribute?
- How does governance work?
- How can someone become a volunteer?
FAQs should be updated when recurring questions reveal documentation gaps.
Before publishing an external resource, CeloHT should consider:
- Source credibility
- Publication date
- Current validity
- Security
- Relevance
- Licensing
- Potential conflicts of interest
High-risk links should receive additional review.
External links should preferably point to:
- Official documentation
- Recognized institutions
- Primary research
- Trusted educational resources
CeloHT should avoid directing users toward suspicious websites, unofficial wallet downloads, or unverified financial offers.
Resource maintainers should periodically check for:
- Broken links
- Redirects
- Outdated documentation
- Changed domains
- Removed pages
- Security concerns
Broken or obsolete resources should be replaced or removed.
Where possible, CeloHT may favor open-source resources that allow:
- Inspection
- Modification
- Community review
- Reuse
- Education
Licensing requirements must always be respected.
Resources created by CeloHT should identify applicable licenses where necessary.
External resources remain subject to their respective licenses.
Users should not assume that publication in a CeloHT repository automatically grants unrestricted rights to third-party materials.
Resources should be designed for broad accessibility.
Where practical:
- Use clear language.
- Provide mobile-friendly materials.
- Avoid unnecessary technical jargon.
- Provide alternative formats.
- Consider low-bandwidth environments.
CeloHT may provide resources in:
- Haitian Creole
- English
- French
Language versions should preserve the meaning of the original content.
When technical accuracy requires it, standard technical terminology may be retained with explanations.
Because users may have limited connectivity, CeloHT should consider:
- Lightweight pages
- Downloadable documents
- Compressed media
- Text-first resources
- Offline educational materials
Performance should be considered when publishing large files.
Resources must not expose:
- Private keys
- Passwords
- API secrets
- Authentication tokens
- Confidential credentials
- Sensitive personal data
Public repositories should be reviewed before publication.
Each major resource should have an identifiable maintainer or responsible team.
Responsibilities include:
- Accuracy
- Updates
- Link maintenance
- Version control
- Security review
- Archiving
Resources may follow:
Draft
↓
Review
↓
Published
↓
Maintained
↓
Updated
↓
Deprecated
↓
Archived
Archived resources should be clearly marked when they remain publicly accessible.
A resource should be reviewed when:
- Users report errors.
- Underlying technology changes.
- A linked source becomes obsolete.
- Security guidance changes.
- Program rules change.
- New evidence contradicts an existing claim.
A future resource directory may use:
Resources
├── Getting Started
├── Education
├── Web3
├── Financial Literacy
├── Celo
├── Security
├── Development
├── Research
├── Environment
├── Governance
├── Community
├── Partnerships
└── Media
For a new participant:
- Read
WHY_CELOHT.md. - Read
QUICK_START.md. - Review
WEB3_101.md. - Review wallet security guidance.
- Explore CeloHT programs.
- Explore available educational resources.
- Join appropriate community activities.
Developers should start with:
- Repository
README.md TECH_STACK.mdSYSTEM_DESIGN.mdSDK.mdCONTRIBUTING.mdTESTING.mdSECURITY.md- Repository-specific development instructions
Researchers should start with:
RESEARCH.mdPUBLICATIONS.md- Data documentation
- Relevant program documentation
- Methodology documentation
- Available datasets
- Source references
Partners should review:
PARTNERSHIPS.mdPROGRAMS.mdWHY_CELOHT.mdGOVERNANCE.mdTRANSPARENCY.md- Relevant program documentation
Specific partnership terms should be handled through appropriate agreements.
Contributors should review:
CONTRIBUTING.mdCODE_OF_CONDUCT.mdSECURITY.md- Repository issues
- Development documentation
- Testing requirements
Contributions should follow the applicable repository workflow.
Users may report:
- Broken links
- Incorrect information
- Outdated documentation
- Accessibility problems
- Security concerns
- Missing resources
Feedback should be reviewed by the appropriate maintainer.
CeloHT should use resource usage and community feedback to identify documentation gaps.
The resource directory should evolve alongside:
- CeloHT products
- Educational programs
- Community needs
- Technical infrastructure
- Governance
- Research
- Environmental initiatives
Good resources reduce barriers to participation.
CeloHT therefore aims to maintain a resource ecosystem that makes it easier for users, learners, developers, researchers, partners, volunteers, and communities to find reliable information, understand the project, participate safely, and contribute meaningfully.
The goal is not to publish the largest possible amount of information.
The goal is to make the right information available, understandable, verifiable, and useful.
Document Status: Active Maintained By: CeloHT Community Primary Authors: Johnny Dubic & CeloHT Community
© 2026 CeloHT - Open Source. Global Impact. Licensed under Apache.