Repositories
Repositories
Index of all CyanPrint repositories
CyanPrint Repositories
CyanPrint is organized as a monorepo-style project with separate repositories for each component. This page provides an overview of all repositories and their purposes.
Repository Overview
All Repositories
| Repository | Tech Stack | Purpose | Status |
|---|---|---|---|
| sulfone.iridium | Rust, Clap, Tokio | CLI tool for end users | Active |
| sulfone.boron | Go 1.24, Gin, urfave/cli, Docker | Execution coordinator | Active |
| sulfone.zinc | C#/.NET 8, ASP.NET Core, Entity Framework Core | Registry API server | Active |
| sulfone.argon | TypeScript, Svelte, SvelteKit, Tailwind CSS | Web UI for registry | Active |
| sulfone.helium | TypeScript, Python, C# | SDKs for template development | Active |
| sulfone.silicon | TypeScript, Fumadocs, CodeHike | Documentation site | Active |
Repository Details
Iridium (CLI)
The command-line interface that users interact with directly.
- Language: Rust
- Framework: Clap
- Key Features: Project scaffolding, template management, configuration
Boron (Executor)
The execution coordinator that manages container-based template execution.
- Language: Go 1.24
- Framework: Gin, urfave/cli
- Key Features: Container orchestration, resource management, job scheduling
Zinc (Registry API)
The registry API that stores template metadata and handles authentication.
- Language: C#
- Framework: .NET 8, ASP.NET Core, Entity Framework Core
- Key Features: Template registry, versioning, authentication
Argon (Web UI)
The web-based user interface for browsing and managing templates.
- Language: TypeScript
- Framework: Svelte, SvelteKit
- Key Features: Template browsing, search, user management
Helium (SDKs)
Multi-language SDKs for developing templates, processors, and plugins.
- Languages: TypeScript, Python, C#
- Key Features: Type-safe APIs, input validation, file generation
Development Setup
To contribute to any CyanPrint repository:
Fork the repository on GitHub
Clone your fork locally
Follow the setup instructions in the repository's README
Make your changes and submit a pull request
For detailed setup instructions, see the Development Setup Guide.
Contributing Guidelines
Each repository has its own contributing guidelines, but general principles apply:
- Follow the code style defined in each repository
- Write tests for new functionality
- Update documentation as needed
- Submit pull requests against the
mainbranch - Ensure CI passes before requesting review