fix: page not found for apisix docker and apisix helm chart

[KishaniKandasamy]

Fixes: #281

Changes:

update docusaurus.config.js

[juzhiyuan]

wow thanks, this will need @qier222's help to review :)

[juzhiyuan]

Hi @KishaniKandasamy, I noticed that we use downloads fields to render both Doc Selector on the navbar and Downloads part, that's not a good way, due to we don't need docker on the Download page.

Because we removed them from Downloads field, then there have some conflicts, would you like to add a new field like docs on the config file? and render the navbar from it.

[KishaniKandasamy]

Hi @KishaniKandasamy, I noticed that we use downloads fields to render both Doc Selector on the navbar and Downloads part, that's not a good way, due to we don't need docker on the Download page.

Because we removed them from Downloads field, then there have some conflicts, would you like to add a new field like docs on the config file? and render the navbar from it.

yes I will 👍🏻

[KishaniKandasamy]

Hi @KishaniKandasamy, I noticed that we use downloads fields to render both Doc Selector on the navbar and Downloads part, that's not a good way, due to we don't need docker on the Download page.

Because we removed them from Downloads field, then there have some conflicts, would you like to add a new field like docs on the config file? and render the navbar from it.

Hi Zhiyuan, then "@docusaurus/plugin-content-docs" for helm chart and docker??

[juzhiyuan]

Hi @KishaniKandasamy, I noticed that we use downloads fields to render both Doc Selector on the navbar and Downloads part, that's not a good way, due to we don't need docker on the Download page.
Because we removed them from Downloads field, then there have some conflicts, would you like to add a new field like docs on the config file? and render the navbar from it.

Hi Zhiyuan, then "@docusaurus/plugin-content-docs" for helm chart and docker??

We should keep them :) Because Docusarus will render docs.

[jbampton]

Suggested change

Traffic split (Canary release) in Ingress Nginx supports weight-based scheme and header rule-based one, but it relies on annotations, which semantic is weak; The Kong way only supports to configure canary release by weight, the scenarios are somewhat narrow, and the configuring is complicated (you need to configure several resources); In contrast, traffic split in Apache APISIX Ingress Controller is flexible and easy to configure, it works well for both the weight-based and rule-based traffic split scheme.

Traffic split (Canary release) in Ingress Nginx supports weight-based scheme and header rule-based one, but it relies on annotations, which semantically is weak; The Kong way only supports to configure canary release by weight, the scenarios are somewhat narrow, and the configuring is complicated (you need to configure several resources); In contrast, traffic split in Apache APISIX Ingress Controller is flexible and easy to configure, it works well for both the weight-based and rule-based traffic split scheme.

https://www.thefreedictionary.com/semantically

[juzhiyuan]

Hi @jbampton, after I merged this PR, I noticed that you have a suggestion change 🤣🤣