Trac tickets with User Manual implications

Hi, my name is Jerry Bates, and I’m new to these parts, but have been building sites for others (and training them too) for some time now.  I’m looking forward to working on this manual, as I think it’s sorely needed.

Anyway, before I start rolling up my sleeves, I thought I’d post up a few of the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket I am aware of that have implications for this project, and will likely require either re-writing existing (from .com) documentation or updated screenshots; in some cases both.

I know many of you are already aware of these tickets, but I don’t see discussions about it, so I figured this would be good to post up, to avoid any duplication of effort.


  • #16379 – Better UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. for doing “Page on Front”
  • #16416 – Settings -> Privacy “blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. search engines” option is not accurate
  • #20993 – Rename the “HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.” editor tab to “Text”
  • #21368 – Welcome screen design – v2
  • #21583 – Improve discoverability and visual design of Screen Options and Help Panels
  • #21598 – Update default button styles in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • #21754 – Replace QuickPress labels with gray prompt texts

If you happen to know any others that I may have missed here, please add them in the comments. 🙂