Replies: 2 comments 1 reply
-
Big downside: functionality changes would no longer be together in one commit with the corresponding docs changes. I do not think it reduces maintenance burden. I doubt they really want to give out docs approval permissions to a bunch of people. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Closing because I realised this would be more trouble than its worth, because some parts of the documentation are generated from the source code. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now Helix's documentation lives in the
book
directory. But I think it can be beneficial to move it to a separate repository, likehelix-editor/docs
:Decreases maintenance burden. All issues and PRs related to the documentation live in that repository
Push and merge access can be handed out much more freely.
Right now the maintainers that review pull requests also have to review documentation PRs. Reviewing documentation changes takes away time from reviewing code-related PRs.
It'll mean changes to documentation will be merged quicker as well.
If we want to port the following wiki pages to the official documentation:
Then that will further mean that the docs are edited more often. It'll become harder for the maintainers to review every little PR such as "Add X formatter for X language"
So, any thoughts on this?
Beta Was this translation helpful? Give feedback.
All reactions