- Editing a doc on GitHub takes more time
- Is less efficient
- Even just editing a link will make a cascading event almost impossible to handle
- Styling and writing is awful, and it looks awful
- No search features on the site
- No breadcrumbs
- editing a “menu” took me editing an entire repo due to no link updates
- Current doc GitHub has I believe a total of 4 contributors. I dare to bet one of the reasons is things like “fork”, “push”, “pull”. Unnecessary and totally alien tech talk to some writer of a doc. No one does nor will contribute to that unless they are real deep developers, who shouldn’t write or maintain doc anyway.
- Not the ideal and made for interface for a content management.
- CP and WP are the ideal tool for this
- Finally, and this is major: code doc will be created by a machine into HTML wp(cp) posts. Do you really want to go and convert, upload, and update over 8k single posts with links to each other on github, along with just as many user docs (in future)?
My last PR to GitHub doc showed how much trouble it is to even update a doc where 30% of the links currently are dead, even if on GitHub they actually lead to content (but on live site lead to empty “coming soon” page). I’m not going to manage 8k posts with raw HTML and zero visual editing, and what’s really really worse, without permalink feature that wp has.
Since 3 years I believe cp exists and the doc still says “coming soon” in some parts.
I don’t understand why we don’t listen to the community, which is overwhelmingly in favour of the simple versus the weird complex solution.
No offense, I love GitHub and open editing, but it is not made for this goal/task and is just an awful “solution” to this problem we face: there’s no doc for cp.
I can setup a full fledged doc directory with search and front end forms and access control and design in less than 2 days. Over a weekend basically.
All I need is a network cp instance with admin access.
Give the community the chance to fix this, because this is what it needs, it’s not “to be implemented” as it is already partially there but truly broken and awful both in editing and visual experience.
Again, no offense intended and no preference pushed, I’d love to use open and public GitHub for this, but it clearly doesn’t work as we mean it to.