Contributing
Elysium isn’t just a bot — it’s a community project and a philosophy. Our goal is to build wellness, reading, and journaling tools that are empowering, gentle, easy to use, and — above all — human-centered. Whether you’re a developer, writer, UX nerd, avid reader, or someone with fresh ideas, your perspective is welcome here.
You don’t need to code to be a contributor! Contributions come in all shapes and sizes:
- Feature ideas
- Catching typos
- Better button wording
- Clearer or expanded documentation
- Even just asking smart questions that help us clarify confusing systems
Ways You Can Contribute
Here’s a breakdown of how you can get involved, and where to go when you’re ready:
Help with Documentation
We maintain a GitBook for clear, beginner-friendly docs. You can help by:
- Writing or improving command pages
- Catching typos, awkward phrasing, or incomplete instructions
- Suggesting better layouts, visuals, or onboarding tips
- Even small edits make a big difference!
Suggest Features & UX Improvements
We love thoughtful feature suggestions — whether they’re small usability tweaks or big ideas.
Where to do this:
Use this thread for:
- Brainstorming new features
- UI/UX improvements
- Feedback about command flow
- “Would this be helpful?” conversations
It’s collaborative! Your idea doesn’t have to be perfect or final. Comment on others’ ideas, too.
Reporting Bugs
If you run into a bug or weird edge case, let us know!
Where to do this:
Please do NOT open new issues.
Instead, comment on the pinned bug report thread and include:
- What happened (and what should have happened)
- How to reproduce it (if possible)
- Screenshots or error messages, if relevant
- What command or feature was involved
Ask Questions or Get Help
Not sure how something works? Confused about a command? Want examples?
Where to do this:
This is a no-judgment space where you can:
- Ask for clarification
- Share tips or tricks
- Request examples
- Get setup help
Your questions often help shape future documentation!
Developer Contributions
If you’re a developer and want to help with code, you’re welcome to submit PRs — especially for:
- Refactoring / cleanup
- Minor feature additions
- Quality-of-life improvements
- Fixing labeled issues (help wanted, good first issue)
Local Setup (basic):
git clone https://github.com/your-org/elysium-bot.git cd elysium-bot npm install # Add your .env file npm run dev
| Topic | Description |
|---|---|
| Bug Reports | Found something broken or not working as expected? Report it so it can be fixed quickly and efficiently. |
| Feature Ideas | Have an idea that could improve the bot? Share your suggestions to help shape future updates. |
| Join Dev Team | Interested in contributing or helping build the project? Reach out and become part of the development team. |
| Support Server | Need help or want to stay updated? Join the support server to connect with the community. |
Project Values
Clarity is everything: We prioritize ease of use and clear explanations over complexity
Low friction, high value: Contributions should make life easier for users
Community-first: The bot should just “work” — no frustration, no guesswork Respectful and direct: We’re cozy and chill, but serious about quality and kindness
If this resonates with you, you’ll fit right in.
Thank you for wanting to contribute to Elysium.
Every suggestion, comment, and PR shapes this project into something more thoughtful, practical, and human — and you’re now a part of that!