docs: logo and prepared directory-listing assets#100
Merged
Conversation
The project had no logo, which blocks both the ebpf.io landscape and the CNCF landscape -- each wants an SVG. Adds a mark-only logo (no <text>, no raster) because both sets of guidelines reject font-rendered text, and a prepared ebpf.io entry matching their emerging.json shape. Also records what the check turned up: the GitHub Action is already listed on the Marketplace (marketplace/actions/bpfcompat-ebpf-compatibility-gate), so that item needed nothing. Signed-off-by: ErenAri <erenari27@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
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.
Tier-5 listing work. Findings first, because two of the four items were not what I expected.
Already done — GitHub Marketplace
The Action is listed: marketplace/actions/bpfcompat-ebpf-compatibility-gate. My first check guessed the wrong slug and 404'd; the real slug derives from
action.yml'sname:. No action needed.Blocker found — the project had no logo
Nothing SVG existed anywhere in the repo, and both ebpf.io and the CNCF landscape require one. Added
docs/assets/bpfcompat-logo.svg:<text>— both guidelines reject font-rendered text (it doesn't render identically without the font; the standard fix is converting to outlines, which a text-free mark sidesteps).It's serviceable, not a designed identity — worth replacing if this becomes a public-facing brand.
Prepared, not submitted — ebpf.io
docs/assets/ebpf-io-entry.jsonmatches the shape in theiremerging.json. Not submitted yet, for two honest reasons:logoNamehas to be wired into their asset pipeline. Their CONTRIBUTING covers blog posts only and says nothing about landscape entries, so the process is worth confirming in#ebpf-websiteon Cilium Slack rather than guessing.Not attempted — CNCF landscape
Needs a Crunchbase organisation entry alongside the logo, which is a real prerequisite rather than a form field. Deferred rather than half-submitted.