How ogeon/palette works
Project type and purpose
• palette: the core library crate
• integration_tests, no_std_test, benchmarks: test harnesses and performance benchmarks
• GitHub Actions and workflows for CI, release-note generation, version bumping, docs publishing
File structure
• Top-level Cargo.toml declares a workspace.
• Subdirectories each contain their own Cargo.toml and source:
• codegen/src: code that reads resources (svg_colors.txt) and emits Rust LUTs at build time
• integration_tests, no_std_test, benchmarks: stand-alone crates that depend on palette to validate behavior
• .github/workflows and .github/actions contain CI/CD pipelines and custom GitHub Actions (release notes, version increment)
README for additional insights
• Points to examples in palette/examples and online docs via docs.rs