WordPress/HelpHub

Proposal: Leverage GitHub for content management

atachibana opened this issue · 3 comments

atachibana commented

WP-CLI handbook (https://make.wordpress.org/cli/handbook/) and Gutenberg handbook (https://wordpress.org/gutenberg/handbook/) manage those contents in the GitHub repository, and publish them as WordPress contents.

This method has some advantages:

  1. We don't need user management. Restricted users can modify contents direct, and general user should send Pull Request.
  2. Revision will be stored in GitHub
  3. Translator can grab contents by fork of repository.

Shouldn't we follow their method?

zzap commented

I think we had a discussion about this at Community Summit 2017 in Paris. I generally love the idea but there is a limiting factor for people who don't know how to use GitHub and have never heard about GIT (let alone used it).

Chances are that people who know about WP-CLI or Gutenberg (at this point of its development) have used, in one way or the other, some sort of versioning system. I don't know what is the structure of end user docs contributors and how well they get along with GIT but I think it's worth thinking about ways to allow wider audience to contribute.

joyously commented

If it's the content for the Docs Handbook, I say Yes!
If it's the content for HelpHub, I say No, mostly because "eat your own dogfood", meaning that WordPress is a content management system whether it calls itself a blogging software or not. It should be able to handle its own content. If using it for its own documentation exposes weaknesses and ways we can enhance it, I think we should make sure those issues are adressed in the software.

atachibana commented

I close this issue because our consensus is that thinking WordPress first.

@joyously I understand your saying.
But there some issues that current WordPress does not track, and will take some time for its supports.

  1. Revision or History. There no way to know the revision or history of contents for non-authenticated user. Even authenticated user, current revision diff functions is poor.
  2. Reviewing process. Multiple users cannot edit & review the single content effectively.

Non-English user requires them for the translation. And that is the reason why my friend had to create export tool from WordPress handbook pages to GitHub repository contents for translation management.