docs: vendor Rayforce logos in-tree, explicit picture sources#11
Merged
Conversation
PR #10 merged before two follow-up commits landed; this brings the intended end state onto main: 1. Logo files copied from ../rayforce/docs into raysense's own docs/. Both projects are owned by the same author, no attribution issue. raysense is now self-contained for README assets and no longer depends on rayforce/master staying public or stable. 2. README references them via relative path, which works in: - GitHub README rendering on main - GitHub PR preview on a feature branch - crates.io README rendering once `docs/*.svg` ships in the .crate 3. <picture> now declares both light and dark sources explicitly (the prior single-source-plus-fallback worked on github.com but was fragile on some other markdown renderers): dark theme -> logo-light.svg (white mark, visible on dark bg) light theme -> logo-dark.svg (navy mark, visible on light bg) 4. Cargo.toml `include` whitelist updated with `docs/*.svg` so the published .crate ships the SVGs.
singaraiona
added a commit
that referenced
this pull request
May 1, 2026
PR #10 merged before two follow-up commits landed; this brings the intended end state onto main: 1. Logo files copied from ../rayforce/docs into raysense's own docs/. Both projects are owned by the same author, no attribution issue. raysense is now self-contained for README assets and no longer depends on rayforce/master staying public or stable. 2. README references them via relative path, which works in: - GitHub README rendering on main - GitHub PR preview on a feature branch - crates.io README rendering once `docs/*.svg` ships in the .crate 3. <picture> now declares both light and dark sources explicitly (the prior single-source-plus-fallback worked on github.com but was fragile on some other markdown renderers): dark theme -> logo-light.svg (white mark, visible on dark bg) light theme -> logo-dark.svg (navy mark, visible on light bg) 4. Cargo.toml `include` whitelist updated with `docs/*.svg` so the published .crate ships the SVGs. Co-authored-by: Anton <anton.kundenko@gmail.com>
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
1 participant
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.
Why this exists
PR #10 merged before two follow-up commits landed on its branch, so the intended end state for the logo never reached main. This PR brings it over cleanly.
What changes
Logos copied into
docs/(logo-dark.svg,logo-light.svg) from../rayforce/docs/. Both projects share an author, so no license/attribution issue. raysense is now self-contained for README assets.README references them via relative path. Works on GitHub README, GitHub PR preview, and (because of Release 1.0.0 #4 below) crates.io.
<picture>declares both light and dark sources explicitly. The prior single-source-plus-fallback was correct on github.com but fragile on other markdown renderers. Mapping is:docs/logo-light.svgdocs/logo-dark.svgCargo.toml
includeaddsdocs/*.svgso the published.crateships the SVGs and the relative paths render on crates.io too.Verified
cargo package --listincludes both SVGs.Test plan
cargo packageincludesdocs/logo-*.svg.