Contributing

Julia is an open, modular framework designed to grow with its community. Whether you're building plugins, fixing bugs, or enhancing the runtime, this guide will help you contribute effectively.

Philosophy

Julia encourages a plugin-first mindset. Instead of adding features directly to the core, most logic should be shipped as plugins.

If a feature can be isolated, versioned, and documented — it likely belongs in a plugin.

Ways to Contribute

🧩 Build a Plugin

The best way to start is to create and share a custom plugin.

Ideas:

AI models (e.g., wallet_analyzer)
Governance tools (e.g., voting_weights)
Oracle adapters (e.g., chainlink_bridge)
Meme utilities (e.g., shiller_detector)

Submit via pull request or plugin registry.

🐛 Fix Bugs

Find something broken in the runtime?

Check open issues
Submit test cases
Write a patch or fix with a clean commit message

All contributions are peer-reviewed before merging.

⚙️ Extend the Runtime

Power users can contribute improvements to:

Plugin host execution
Sandbox management
Telemetry and metrics
Developer tooling (CLI, SDKs)

If you’re proposing a major change, open an issue or discussion thread first.

Repository Structure

/src/Julia.Web/           - Main API host
/Plugins/                 - Community and core plugins
/docs/                    - This documentation site
/.github/                 - Contribution templates

Coding Guidelines

C# 10 / .NET 7
Use async/await properly
Favor composition over inheritance
Keep plugins self-contained
Use feature folders if extending runtime

Pull Request Checklist

PR has a clear title
Plugin has tests (if logic-heavy)
Documentation is updated
Commits are clean and atomic
Linked to an issue (if applicable)

Join the Community

🐙 GitHub: github.com/your-org/julia
💬 Discord: discord.gg/julia-exec
🧠 Twitter: @julia_core

We believe composable logic is the future of Web3.
And the best way to shape it is to build it — together.

Ready to ship your first plugin?
Let’s go.

Contributing

On this page