If you're interested in supporting Stump's development, and you know how to code, follow the steps outlined in the developer guide section to get started. There are several areas where help is needed:
- Translation, so Stump is accessible to non-English speakers.
- An automated translation system would be immensely helpful! If you're knowledgeable in this area, please reach out!
- Writing comprehensive integration tests.
- Designing and/or implementing UI elements.
- Docker build optimizations (it is currently horrendously slow).
- CI pipelines / workflows (given above issue with Docker is resolved).
- And lots more!
I keep track of all non-code contributions in a CONTRIBUTORS.md file on Stump's GitHub. If you contribute in that manner, please add yourself to the list!
You can contribute to the project financially by using any of these platforms:
Contributions are very encouraged and welcome!
I put together a small set of resources to get you started with Stump. If you're completely new to rust and/or web development, I recommend reviewing the Rust Book and Getting started with React in that section first.
Please review the CONTRIBUTING.md beforehand. To get started, you'll need to set up your development environment.
Ensure you are on the
develop branch before continuing.
pnpm run setup
This will install the project dependencies, build the frontend bundle (required for server to start), generate the prisma client, and create the sqlite database.
There are multiple client applications within Stump's monorepo, all relying on the Stump server. Each app has a startup script following the pattern
dev:client_app_name. These will start the application along with the server concurrently. For example, to run the web client, simply run:
You can also run the server and the client applications in separate processes:
pnpm server dev # start the Stump server pnpm web dev # start the web client in browser
At this point, you're pretty much all set to start contributing!
I format my code using Prettier and rustfmt. There is a pre-commit hook that will run these for you, but I want to point out that all of the apps within this repository use 4 tab spaces for indentation. This is primarily for accessibility, as well as consistency with the Rust codebase. If you'd like, you can configure your editor to render whatever indentation you prefer, even though the raw code will be as described above. I personally maintain the 4 tab space rendering on the Rust side and shorten it to only render 2 on the frontend side.
A few useful resources for developers looking to contribute: