You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People can update the doc in the same PR as the code change
More activities can happen in the one repo
It's easier for people to open the issue in the correct place. All issues (for doc / for code / for website) can go to one place and there is no need to move/track them in several places.
Cons:
Increase the main repo's size. But this is trivial under the developer's modern network environment.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion, this is a website project and we are planning to refactor with the new website framework, this will be taken into account when refactoring.
Many famous open source projects put the doc into the same repo of the source code. For instance:
APISIX: https://github.com/apache/apisix/tree/master/docs
Envoy: https://github.com/envoyproxy/envoy/tree/main/docs
Some projects even put the website into the same repo:
Pulsar: https://github.com/apache/pulsar/tree/master/site2/website
Here I suggest higress merge this repo into https://github.com/alibaba/higress.
Pros:
Cons:
The text was updated successfully, but these errors were encountered: