[wp-meta] [Making WordPress.org] #7520: Move Handbooks to GitHub to ease ability to contribute content
Making WordPress.org
noreply at wordpress.org
Thu Aug 22 13:59:43 UTC 2024
#7520: Move Handbooks to GitHub to ease ability to contribute content
-----------------------------+---------------------
Reporter: oglekler | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Handbooks | Resolution:
Keywords: |
-----------------------------+---------------------
Comment (by greenshady):
I can open a separate ticket if needed, but it would be highly beneficial
to the folks who maintain the Theme Handbook to have this particular
handbook connected to GitHub for management:
https://developer.wordpress.org/themes/
Note that it is a part of the Developer Resources site, and therefore is a
handbook in which developers contribute.
The current process is overly complicated and requires first filing a
ticket here: https://github.com/WordPress/Documentation-Issue-
Tracker/issues?q=is%3Aopen+is%3Aissue+label%3Athemes
Then, manually writing fixes in the ticket, which have to be transferred
elsewhere. For new handbook pages, they are generally written in Google
Docs to be reviewed. Then, they have to be migrated to WordPress.
With GitHub, it would give developers a tool that they are accustomed to
using the ability to contribute to the Developer Docs. Right now, only 2-3
people actively contribute to the handbook at all. There's just such a
huge barrier to entry that no one even bothers contributing (and, yes, I
do get this direct feedback that folks would contribute more if it worked
like the Block Editor Handbook).
With that in place, we could reintegrate WP via the Playground Docs
Workflow project, as @zieladam mentioned.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/7520#comment:19>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list