Professionalize bpfcompat landing page: scope reframe + why + comparison#6
Merged
Conversation
The "It is / It is not yet" panel read as a list of deficiencies. Reframe it as deliberate scope + roadmap: "Available today / On the roadmap", surface the GitHub Action and ARM64 coverage that already exist, and replace the "serious MVP on purpose" footer with one that points to the repo evidence. Avoid hard dates to not over-promise. Applied across all 8 locales. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying kernel-guard-frontend-git with
|
| Latest commit: |
d3fe278
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f6293db9.kernel-guard-frontend-git.pages.dev |
| Branch Preview URL: | https://landing-professionalize-bpfc.kernel-guard-frontend-git.pages.dev |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
kernel-guard-frontend | d3fe278 | Commit Preview URL Branch Preview URL |
Jun 19 2026, 04:04 PM |
Two new sections, localized across all 8 locales: - Why this exists: motivation grounded in the publicly-documented fact that major eBPF teams build their own kernel-testing (Cilium/Tetragon use little-vm-helper; Falco maintains a Firecracker kernel-testing framework). No endorsement implied; links to the public projects as references. - How it compares: a fair table vs LVH (Cilium), bpfvalidator, and roll-your-own (vmtest), with a "best when" row that concedes their strengths. Capability cells use universal symbols; only prose is localized. Build: 288/288 routes prerendered, tsc --noEmit clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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.
Makes the bpfcompat page reflect what already ships. Three changes, all localized across 8 locales, build verified (288/288 routes prerendered,
tsc --noEmitclean).1. Scope panel → scope + roadmap
The "It is / It is not yet" panel read as deficiencies. Reframed as "Available today / On the roadmap", surfaces the GitHub Action + ARM64 that already exist, footer now points to repo evidence instead of "serious MVP on purpose". No hard dates.
2. New "Why this exists" section
Grounded in the publicly-documented fact that major eBPF teams build their own kernel-testing (Cilium/Tetragon use little-vm-helper; Falco maintains a Firecracker kernel-testing framework). No endorsement implied; links the public projects as references.
3. New "How it compares" section
Fair comparison table vs LVH (Cilium), bpfvalidator, and roll-your-own (vmtest), with a "best when" row conceding their strengths. Capability cells are universal symbols; only prose is localized.
Brand note: per your call, social proof is the generic version (no Federico quote / no implied Falco endorsement); the comparison names competitors per your approval.
🤖 Generated with Claude Code