[wp-meta] [Making WordPress.org] #7520: Move Handbooks to GitHub to ease ability to contribute content

Making WordPress.org noreply at wordpress.org
Wed Mar 20 02:21:25 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 dd32):

 As an example; the content for the main WordPress.org homepage (and sub-
 pages) are currently hard-coded [https://github.com/wordpress/wporg-
 main-2022/ in the theme] for translation purposes, but with some horrible-
 to-manually-edit block HTML.

 The block HTML is not edited directly however, instead it's edited via the
 Page Editor; and then sync'd to the theme source through a PR such as
 [https://github.com/WordPress/wporg-main-2022/pull/403 PR403] or
 [https://github.com/WordPress/wporg-main-2022/pull/401 PR401].

 This isn't perfect, as the automated PRs ''(which are a new thing, it was
 previously a process of sending up a smoke signal, and a developer running
 the sync scripts)'' lack information about who made the edits and why, but
 let's them use the full power of the editor.

 Would I suggest this exact process for handbooks? No. No I wouldn't. But
 it's a good example of a hybrid approach, where the page can be edited
 visually, but edits aren't made live without a review first.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7520#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list