Skip to content

Professionalize bpfcompat landing page: scope reframe + why + comparison#6

Merged
ErenAri merged 2 commits into
mainfrom
landing/professionalize-bpfcompat
Jun 19, 2026
Merged

Professionalize bpfcompat landing page: scope reframe + why + comparison#6
ErenAri merged 2 commits into
mainfrom
landing/professionalize-bpfcompat

Conversation

@ErenAri

@ErenAri ErenAri commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Makes the bpfcompat page reflect what already ships. Three changes, all localized across 8 locales, build verified (288/288 routes prerendered, tsc --noEmit clean).

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

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>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 19, 2026

Copy link
Copy Markdown

Deploying kernel-guard-frontend-git with  Cloudflare Pages  Cloudflare Pages

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

View logs

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 19, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

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>
@ErenAri ErenAri changed the title Reframe bpfcompat scope panel as scope + roadmap (8 locales) Professionalize bpfcompat landing page: scope reframe + why + comparison Jun 19, 2026
@ErenAri ErenAri merged commit 4cced4b into main Jun 19, 2026
3 of 4 checks passed
@ErenAri ErenAri deleted the landing/professionalize-bpfcompat branch June 19, 2026 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant