docs: add contribution guidelines and developer setup docs - #93
Merged
jobbykings merged 1 commit intoJun 22, 2026
Merged
Conversation
jobbykings
approved these changes
Jun 22, 2026
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The README referenced a
CONTRIBUTING.mdthat did not exist. This PR adds comprehensivecontributor and developer documentation covering setup, standards, the PR process, testing,
commit conventions, and an architecture overview.
Closes #78
What's included
started, development workflow, coding standards (TypeScript + Rust/Soroban), Conventional
Commits, testing requirements, PR process, and review process.
frontend packages, data stores/external services, request lifecycle, and CI overview.
packages (contracts, backend, frontend), env configuration, supporting services, and
troubleshooting.
and Cargo (contracts), with examples and CI guidance.
breaking changes.
All content is derived from the actual repository (pnpm workspaces, each package's real
scripts, the CI pipeline, and the Soroban/Rust contracts) and is documentation-only — no
source code or build behavior is changed.
Type of change
Checklist