[wp-meta] [Making WordPress.org] #6608: Enable Blocks for the Support Forums editor

[Making WordPress.org]

#6608: Enable Blocks for the Support Forums editor
----------------------------+---------------------
 Reporter:  dd32            |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  high            |   Milestone:
Component:  Support Forums  |  Resolution:
 Keywords:                  |
----------------------------+---------------------
Description changed by dd32:

Old description:

> As discussed during the #forums chat today, using the
> [https://wordpress.org/plugins/blocks-everywhere/ Automattic Blocks
> Everywhere plugin] a few of us have been looking into the possibility of
> using it on the Support Forums to better the support experience.
>
> I've set it up on https://test.wordpress.org/support/ which is showing
> good promise, however, there's a few things that need to be resolved
> before we can consider enabling it on Support Forums.
>
> This is a tracking ticket for any issues experienced, some will be fixed
> upstream in the plugin itself: [https://github.com/Automattic/blocks-
> everywhere/issues Automattic/blocks-everywhere] and others may need to be
> done just for WordPress.org.
>
> ✅ Don't show the full Kitchen Sink in the TinyMCE editor when editing
> existing non-block posts. [https://github.com/Automattic/blocks-
> everywhere/issues/44 upstream issue].
> ✅ Don't show full Block HTML in email notifications from bbPress.
> [https://github.com/Automattic/blocks-everywhere/issues/40 upstream
> issue]. Bonus: Less HTML in existing emails.
> 🔲 Ensure that `@mention` work appropriately. Currently it lists Site
> Users, where it should pull from those who have interacted with the
> current Thread (and potentially the Plugin/Theme reps). This should NOT
> suggest moderators by default, or those whose replies are hidden
> (spammed, archived, awaiting moderation, etc).
> 🔲 Ensure that pasting logs works. The existing "wrap it in code tags"
> doesn't work well, and when pasting into the Block Editor it will split
> it into many blocks instead. This behaviour makes sense for most uses of
> the Block Editor, but creates a worse UX for the forums, especially when
> it comes to attempting to combine the logs into a singular block.
> 🔲 Ensure that fixes we've applied for `<li>` in the past continue to
> work. See #20. The fix currently in place via [9601] breaks/prevents
> nested lists in the Block Editor.
> 🔲 Ensure that blocks copy-pasted from other Block Editor Instances
> pastes correctly into the Support forum editor.
> 🔲 Evaluate if an option to disable the Block editor on a per-user
> profile option is practical. With early iterations of testing support,
> this wasn't possible.
> 🔲 Evaluate additional blocks to be enabled, or created, for the forums.
> This may include a "Pasted content" block as above, or other blocks such
> as pre-defined replies for members of the support team and/or
> plugin/theme support reps.
>
> ''Additional items to be edited in here as discovered, please comment
> below. Bug Gardeners: Please edit my ticket too! ''
>
> For tracking..
> ✅ Enable it for test.wordpress.org/support/
> 🔲 Enable it for wordpress.org/support/
> 🔲 Enable it for all localised support forums, *.wordpress.org/support/

New description:

 As discussed during the #forums chat today, using the
 [https://wordpress.org/plugins/blocks-everywhere/ Automattic Blocks
 Everywhere plugin] a few of us have been looking into the possibility of
 using it on the Support Forums to better the support experience.

 I've set it up on https://test.wordpress.org/support/ which is showing
 good promise, however, there's a few things that need to be resolved
 before we can consider enabling it on Support Forums.

 This is a tracking ticket for any issues experienced, some will be fixed
 upstream in the plugin itself: [https://github.com/Automattic/blocks-
 everywhere/issues Automattic/blocks-everywhere] and others may need to be
 done just for WordPress.org.

 ✅ Don't show the full Kitchen Sink in the TinyMCE editor when editing
 existing non-block posts. [https://github.com/Automattic/blocks-
 everywhere/issues/44 upstream issue].
 ✅ Don't show full Block HTML in email notifications from bbPress.
 [https://github.com/Automattic/blocks-everywhere/issues/40 upstream
 issue]. Bonus: Less HTML in existing emails.
 ✅ Ensure that `@mention` work appropriately. Currently it lists Site
 Users, where it should pull from those who have interacted with the
 current Thread. This should NOT suggest moderators by default, or those
 whose replies are hidden (spammed, archived, awaiting moderation, etc).
  - 🔲 Consider whether to always include the support reps for the current
 plugin/theme.
 🔲 Ensure that pasting logs works. The existing "wrap it in code tags"
 doesn't work well, and when pasting into the Block Editor it will split it
 into many blocks instead. This behaviour makes sense for most uses of the
 Block Editor, but creates a worse UX for the forums, especially when it
 comes to attempting to combine the logs into a singular block.
 🔲 Ensure that fixes we've applied for `<li>` in the past continue to
 work. See #20. The fix currently in place via [9601] breaks/prevents
 nested lists in the Block Editor.
 🔲 Ensure that blocks copy-pasted from other Block Editor Instances pastes
 correctly into the Support forum editor.
 🔲 Evaluate if an option to disable the Block editor on a per-user profile
 option is practical. With early iterations of testing support, this wasn't
 possible.
 🔲 Evaluate additional blocks to be enabled, or created, for the forums.
 This may include a "Pasted content" block as above, or other blocks such
 as pre-defined replies for members of the support team and/or plugin/theme
 support reps.

 ''Additional items to be edited in here as discovered, please comment
 below. Bug Gardeners: Please edit my ticket too! ''

 For tracking..
 ✅ Enable it for test.wordpress.org/support/
 🔲 Enable it for wordpress.org/support/
 🔲 Enable it for all localised support forums, *.wordpress.org/support/

--

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