moonming opened a new pull request, #2059: URL: https://github.com/apache/apisix-website/pull/2059
## Summary Adds **five head-to-head comparison articles** to the Learning Center. Comparison content was the biggest gap for the stated goal — *ranking on "API gateway" queries ahead of Kong and the cloud vendors*. Today only `apisix-vs-kong` and the open-source roundup exist, while the SERP for high-intent "X vs Y" terms is dominated by third-party aggregators. APISIX's existing comparisons already rank on page one, so more should follow. > ⚠️ **Stacked on #2058.** Base is `feat/seo-article-structured-data` so the new articles pick up the `Article`/`FAQPage`/`BreadcrumbList` wrapper from that PR (and this PR shows only the new content). Merge #2058 first; GitHub will retarget this to `master`. ## New articles | Article | Framing | |---|---| | `apisix-vs-aws-api-gateway` | Self-hosted open source vs managed cloud service — cost at scale, lock-in, performance | | `apisix-vs-nginx` | APISIX is *built on* NGINX — what a purpose-built gateway adds over raw NGINX / NGINX Plus | | `apisix-vs-envoy` | Turnkey API gateway vs a proxy that needs a separate control plane; north-south vs service mesh | | `apisix-vs-traefik` | Throughput + plugin breadth vs container-native auto-discovery + automatic TLS | | `apisix-vs-apigee` | Open-source gateway vs a full enterprise API management platform — scope and cost | Each follows the existing `apisix-vs-kong` structure (intro → overview → architecture → feature table → when-to-choose-each → FAQ) and carries an FAQ section + matching `faq` front matter, so it emits FAQPage structured data. ## Also in this PR - **`apisix-vs-kong` FAQ backfill** — its FAQ heading is `## FAQ`, which #2058's grep (looking for "Frequently Asked Questions") missed, so it had no `faq` front matter. Added it (answers copied verbatim from its body) so it now emits FAQPage too. - **`/comparisons/` hub** — expanded from 4 to 9 cards, head-to-head comparisons grouped first. - **`llms.txt`** — added the 5 new articles for GEO/LLM discoverability. ## Content approach - **Balanced and credible**, matching the `apisix-vs-kong` tone — favorable to APISIX on its genuine strengths (performance, open-source completeness, dynamic config, no lock-in/cost) while fairly stating when each competitor fits. Credible content ranks better and suits Apache's vendor-neutral posture. - **No fabricated benchmarks** — like `apisix-vs-kong`, performance is discussed qualitatively with a recommendation to benchmark your own workload, rather than inventing head-to-head numbers. - **Honest scope framing** — e.g. NGINX is the foundation APISIX builds on; Apigee is a full platform, not just a gateway (APISIX OSS doesn't bundle a dev portal/monetization). - **Vendor-neutral** — no promotion of any commercial vendor on the Apache site. ## Verification — production (SSR) build Built (`yarn workspace website build`, green) and grepped the output HTML: | Article | Article | Breadcrumb | FAQPage | FAQ answer = body? | |---|---|---|---|---| | apisix-vs-kong | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | | apisix-vs-aws-api-gateway | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | | apisix-vs-nginx | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | | apisix-vs-envoy | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | | apisix-vs-traefik | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | | apisix-vs-apigee | ✅ | ✅ | ✅ 4 Q&A | ✅ 0 mismatch | All 9 `/comparisons/` hub links resolve to built pages. ## Test plan - [x] Production build green; SSR schema verified per the table (incl. FAQ answer ⊆ body check) - [x] `/comparisons/` hub renders 9 cards, all links resolve - [ ] CI deploy build green - [ ] Post-merge: spot-check a couple URLs in Google Rich Results Test -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
