You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "kayx23 (via GitHub)" <gi...@apache.org> on 2026/09/11 09:17:43 UTC

Re: [PR] fix(seo): clarify APISIX capabilities and search intent paths [apisix-website]

kayx23 commented on code in PR #2118:
URL: https://github.com/apache/apisix-website/pull/2118#discussion_r3987710028


##########
blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md:
##########
@@ -25,6 +25,8 @@ image: https://static.api7.ai/uploads/2025/02/17/gWz2QJYq_api-gateway-comparison
 
 Cloud-managed, open-source, and commercial API gateways are not mutually exclusive categories. A vendor can offer a managed service built on open-source software, while a commercial gateway can support self-managed and hosted deployments. The useful question is therefore not which label is universally best, but which operating and support model matches your requirements.
 
+For a product-by-product evaluation, compare Apache APISIX, Kong, Envoy, and Traefik in the [open-source API gateway comparison](/learning-center/open-source-api-gateway-comparison/).

Review Comment:
   This second paragraph should sit below `<!--truncate-->`, not above it.
   
   The first paragraph is already ~370 characters. The Docusaurus list renderer in `blog/src/theme/BlogPosts` still treats everything above the marker as the card excerpt and truncates each `<p>` at 200 characters. A second paragraph therefore renders as another excerpt block under the sliced first paragraph, so this card grows taller than the rest of the grid.
   
   Keep the original paragraph as the excerpt. Put the comparison sentence immediately after `<!--truncate-->` so the article still opens with it.



-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org