Contribute to
ArgoBox
38 modules. MIT licensed. Built for contributions.
Every module, every API, every page — fully open source.
Why Contribute
Real code, real impact, real credit
Real Production Code
Not a toy project. ArgoBox runs in production with 38 modules, real users, and real traffic. Your contributions ship to prod.
Standalone Modules
Every module is portable. Extract any module and drop it into your own Astro, React, or Vue project. No vendor lock-in.
Active Development
38 modules, 170+ API routes, and growing. There is always something to build, fix, or improve.
Resume Builder
Every contribution gets proper credit. Build your portfolio with real infrastructure code, not contrived examples.
Ways to Contribute
Pick your path — every contribution matters
Fix Bugs
Browse open issues and squash bugs. Every fix makes the platform more solid.
Build Modules
Create new modules following the 3-tier pattern. Full scaffolding script included.
Improve Docs
Better docs help everyone. Write guides, improve API references, add examples.
Write Tests
Increase coverage across modules. Integration tests, unit tests, E2E flows.
Design UI
Refine the Glass UI system. Build new components, improve accessibility, polish animations.
Report Issues
Found something broken? File a detailed issue on Gitea. Reproduction steps help us fix it fast.
Module Architecture
Every module follows a clean 3-tier pattern
Platform bindings (Cloudflare Workers, KV, D1). Handles data access, auth, and business logic. Framework-agnostic.
Astro pages and components that render the UI. Consumes the core adapter. Swappable with React, Vue, or Svelte.
REST endpoints under /api/. Each module exposes its own routes. JSON in, JSON out.
Module Config
Each module is registered in src/config/modules/*.ts. The config file declares the module ID, display name,
dependencies, feature flags, and toggle state. Modules can be enabled or disabled at runtime through the admin dashboard
without redeploying.
Get Started
Four steps from fork to merged PR
Fork on Gitea
Clone the repo from git.argobox.com and set up your local dev environment.
Pick an Issue
Browse open issues tagged "good first issue" or "help wanted" to find your starting point.
Follow the Module Pattern
Use the 3-tier architecture: core adapter, page layer, API routes. Run the scaffolding script for new modules.
Submit a PR
Push your branch and open a pull request. Describe what you changed and why. We review fast.
Join the Community
ArgoBox is built by contributors like you. Pick an issue, write some code, and ship it.