catehstn 10:09 am on November 19, 2018
Tags: core-editor ( 433 ), editor ( 184 ), gutenberg ( 284 )

5.0 / Gutenberg Status Update – Nov 19

Current open PRs for review: 46 in 4.5 Milestone (+1)
Current open issues milestoned RC: 61 (-1)
Current open issues milestoned 5.0.0: 14 (+1)
Current open issues milestoned 5.0.1: 7 (-1)
Current open issues milestoned 5.0.x (fast follow): 68 (+1)
Current betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.: Beta 5, released Thursday.
Current pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party: 4.4, released Thursday.
Next release: 5.0 RC, to be released later today.

Note: this is a daily update on progress towards WordPress 5.0, as outlined in this post. This status update is also shared in the #core-editor channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#core-editor, #editor, #gutenberg

Joe McGill 3:38 pm on November 19, 2018

With 75 open issues remaining between the RC and 5.0.0 release milestones—many of them significant issues—I do not see how we can seriously ship a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). today. In doing so, we are either saying we’re ok with shipping a major version of WordPress with this many known issues, or that the term “release candidate” does not actually have meaning.

I would suggest that we revise the schedule to push back RC for at least 4 weeks so we have a reasonable deadline and, in the mean time, continue releasing betas.
- Milan Petrovic 5:48 pm on November 19, 2018
  
  I would expect that RC milestone would be at zero (or close to zero) when RC is released and gather more info and open new issues assigned to next RC, and iterate for few weeks (as it was done with previous major WP versions) until you are confident release is ready.
  
  Add to all these another 100+ issues not even assigned to RC or any other release, some quite serious issues, this turns into quite a mess and complete disregard to any previous rules of WordPress major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope..
  
  Based on the last few weeks of development, RC is at least a month away, with major US holiday this weekend, I don’t expect developers to work more to be ready for next Tuesday release. This schedule is madness, and it has to be pushed to next year.
- Mike Schroder 12:11 pm on November 20, 2018
  
  I entirely agree @joemcgill.
Dominik Schilling (ocean90) 5:32 pm on November 19, 2018

The status updates are not that helpful with regards to new issues which don’t get assigned to a milestone although the report was tagged as a valid bug. Any thoughts on this?
K. Adam White 6:54 pm on November 19, 2018

I concur with @joemcgill‘s assessment above, and I echo @ocean90‘s question. While I am extremely enthusiastic about the upcoming launch of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and I am blown away by the extraordinary work done to get us to this point, the number of issues (and perhaps above all the incomplete state of the documentation) compel me to say I think we should defer to January.

I’m also concerned that continuing to push towards this initial deadline will negatively impact community morale, energy and motivation post-release. I do not think the rate of change we’ve seen lately is sustainable, especially given the intent to release every two weeks in perpetuity post-5.0. A January release would give us time to actually get to an RC state with less risk of burning out the leads and top contributors.
- pcarvalho 5:00 pm on November 20, 2018
  
  as an news organization, we’re already set our timeline to only review wp 5 update in January. If they plan for bi-weekly patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. releases, and maybe a few minor releases, we’ll probably be in 5.2.x around late Jan, It should have stabilized by then.
  - Birgit Pauli-Haack 7:20 pm on November 21, 2018
    
    That’s how we approach it too for our nonprofit and small business sites. That being said we need GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ in 5.0 to start testing our custom solutions.
Morten Rand-Hendriksen 9:34 pm on November 19, 2018

Adding my voice to what has already been said. Take an individual issue like 6177 and the resulting PR as an example. Even if these got merged today, there is no documentation on how to manage responsive images (though I’m working on it) and no theme, including Twenty Nineteen, is handling this correctly as there is no documentation or even a best-practice example. Every “GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/-ready” theme needs to be updated with this new feature for wide and full aligned image blocks to work properly. The runway afforded by a release in just 8 days is simply too short to make this feasible. Pushing the release to January gives Gutenberg time to mature and get to a stable state, and gives developers time to adopt to new (and as in this example yet-to-be-finalized) changes to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Josepha 11:11 pm on November 19, 2018
You’re right that we’re not going to make RC today (Nov 19). A few end of day updates for people:
- 54 pull requests were merged for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 4.5 and there are 7 remaining
- 12 pull requests are assigned to WordPress 5.0
- There are a few open issues in the RC milestone that Matias is planning to dedicate some time to.
Currently the plan is to try Gutenberg 4.5 + WordPress RC again tomorrow (Nov 20).
- DavePorter 4:30 am on November 20, 2018
  
  It concerns me when I hear ‘the plan is to try for RC 1 tomorrow’ with only 7 days to release left to go!
  ps – The release date in the right sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. on this page still say the 19th!
  - Gary Pendergast 6:20 am on November 20, 2018
    
    Thank you for noting that the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. is incorrect, @daveporter! I’ve fixed that up. 🙂
    - DavePorter 7:31 am on November 20, 2018
      
      My pleasure!
- Milan Petrovic 8:15 am on November 20, 2018
  
  This is heading for the trainwreck, and developers making decisions are ignoring all the signs along the way. How can you properly test 50+ pull requests done in a day?
  
  GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ development is still ongoing, with features added faster than a few months ago, in a shorter time, with significantly less testing and feedback, and everyone working on this is fine with what is done. Instead of feature freezing Gutenberg back in July, you are merging ongoing daily development into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. that apart from developers, no one has time to properly test because we had 5 betas and RC coming, with only 5 or 6 days remaining to test RC.
  
  I was really supporting the Gutenberg in a core, but the way it is done, it simply unacceptable for the software that has to run third of the websites on the internet today.
  - Pascal Birchler 9:06 am on November 20, 2018
    
    Note that these aren’t 50+ pull requests in a single day, but all the pull requests that will make it into GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 4.5.
    - Milan Petrovic 12:47 pm on November 20, 2018
      
      Yes, but they also need to go into WP 5.0, am I right? How much time is needed to test in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and then move them to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? It is insane tempo that has zero chance of being tested properly, and each change can affect plugins made for Gutenberg and WP 5.0 already, that will not have time to test everything before 5.0 is released.
      
      And, considering that Gutenberg is still in development and each change is going into WP 5.0 next week, now without any time to test, this is going to break so many plugins when released. Gutenberg development has to stop, WP development has to stop, and give users and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme authors at least 2 months to test everything, report bugs, and get bugs fixed, and only push bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes into the core, not new features Gutenberg is getting daily now.
      
      But, whatever any of us plugin/theme developers say, it is not going to matter at this point. WordPress is more than just a core, it is an ecosystem of plugins and themes, that can’t be tested and updated in a matter of days to accommodate this insane release schedule.
Matt Mullenweg 1:37 am on November 20, 2018

If anyone feels like digging into data I’m curious how many open issues on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. previous major releases of WordPress shipped with.
- DavePorter 2:05 am on November 20, 2018
  
  No disrespect meant, but I think this v5 release is far more significant that anything before it! And it needs to be 99.9% right before it is released.
- Jon Brown 2:19 am on November 20, 2018
  
  Nothing wrong with punting trivial issues to release… but…
  #1 It’s more about what’s getting punted, then that there are issues to be punted.
  #2 The editor is central to everything that is WordPress publishing, it is hard to think that anything affecting the editor is trivial.
  
  I still don’t trust that things have stopped changing enough to truly validate the editor in 5.0. I still want to see 4 weeks of RC, anything less to me is irresponsibly rushing things. As much as I’m looking forward to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, I sure won’t be updating anything but hobby sites until 2019.
- Tim 9:56 am on November 20, 2018
  
  For the sanity of all us small businesses out here built on WP with lots of clients please don’t rush this. It is going to be pretty tough transitioning all our clients (many not very IT literate) to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, especially as we also have end of life for php 5.6 and 7 to deal with and in the UK ate least our biggest holiday period. We will all respect a decision to delay until early 2019.
  
  We are genuinely excited about version 5.0 but I know I’d rather wait.
- John Blackbourn 11:09 am on November 20, 2018
  
  Your inference is completely correct. WordPress 4.9 shipped with over five thousand open tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., as have most releases in recent years, and as will 5.0.
  
  The difference with 5.0 is that the approximately 75 open issues for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ all relate to the single headline feature. You don’t need me to tell you that 4.9 was only ready for RC when all of the issues relating to the work being done on the customiser, pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party/theme editor, and new widgets had either been addressed, or discussed and punted in the weeks prior to RC, instead of on the day.
  
  I don’t understand the rush to release 5.0 when its only new feature is not ready. If the plan is to avoid developer burn-out in the lead up to the release, then that’s fine, but those fortnightly fast-follow releases will have just the same effect with the added bonus of having knowingly shipped incomplete software to 30% of the web.
  
  Are you concerned about the negative PR impact of further delays to the release of 5.0? Because that ship sailed a few weeks after WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe.
- Joe McGill 3:10 pm on November 20, 2018
  @matt – Out of curiosity, I’ve taken you up on this and looked back at how many open tickets were in the past three major releases — limiting the data to tickets which were in the release milestone, since that seems like the most relevant data for this conversation. Here’s what I found:
  - 4.9: 2 open issues, approved by the release leadRelease Lead The community member ultimately responsible for the Release. at RC – Source
  - 4.8: 5 open issues day of RC1, all handled before RC1. Followed with RC2 – Source
  - 4.7: 5 open day before RC1 — 3 approved as post-RC tasks, 1 fixed, 1 punted – Source
  Additionally, when 4.7 was in question because of the readiness of the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. endpoints on the day of RC, your response was this:
  
  “I feel we are including it in the release largely because everyone is too tired to argue for something other than the status quo of leaving it in, which is an immediate cost and pain vs pushing which will be felt in the future, and possibly by other people. We should learn from this: At no point in the future should any feature project or pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party have merging as the only goal and method with which to measure success.”
  
  – Source
  
  At the moment, we are 1 day past the scheduled RC date and there are 38 open issues on the 5.0-RC milestone for the main release feature, with an additional 12 open for the 5.0 release. It seems to me that, in spite of heroic efforts by many very committed and talented professionals, the release is not ready by historic standards and should be pushed.
  - Matt Mullenweg 3:47 pm on November 20, 2018
    Joe, thank you for looking into that! I didn’t think to look in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., was hoping we could extract from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. database or something. I also really hope we can start to whittle down the 5,000+ open tickets WP seems to have permanently hanging around and I’m thinking of ways to do that in 2019.
    
    With regards to 4.7, we’ve definitely felt the pain of the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. being in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. since then, especially in security and lack of usage. (It still is a small fraction of XML-RPC usage.) I’m excited about GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ being our first first-party usage of the REST API shipping in core and we’ve made a ton of improvements to the posting APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. as a result of that.
    
    The context of my “measuring success” comment was that there weren’t very many regular people using the REST API. None of the ideas for what would happen once it was in core have really happened, with the notable exception of “Imagine a feature project that looked at a completely rethought post-new.php.” 🙂
    
    We obviously don’t have that problem with Gutenberg and we’re fast approaching a million (Jetpack tracked) posts made through the editor, with the non-tracked number probably a multiple of that. There’s been an explosion of plugins building on top of Gutenberg and some things like the work ACF and Block Lab have done that seem really transformational for WordPress. For those whom the editor is not a good fit they can opt in at any point, including post-5.0, to Classic and continue using WP exactly as they had before until at least 2022 and likely beyond.
    
    Some good measures of success for Gutenberg:
    
    Are people, when given the choice, choosing to use it over the old editor?
    
    Can they create things they weren’t able to create before?
    
    Are new-to-WP users more successful (active, happy with what they create) than pre-Gutenberg?
    
    Are interesting things being built on top of it?
    - herbie888 4:09 pm on November 20, 2018
      
      Can they create things they weren’t able to create before?
      
      Or can they create things they were able to create before?
      
      Like simply coloring a single word in a paragraph?
      
      Like coloring a headline or a word within?
      
      Like coloring a list or a list item or a word in list item?
      
      …
      - Pratik Kumar 12:16 pm on November 21, 2018
        
        It is possible by Advanced Rich Text Tools for Gutenberg
        
        herbie888 1:48 pm on November 21, 2018
        
        So to be able to create things they were able to create before, they now need an extra pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party?
        
        Huge success.
        
        Why is this not in 5.0 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? Plugin author is in core team…
    - Joe McGill 4:37 pm on November 20, 2018
      
      Thanks for the context and for explaining how you’re thinking about success for this project. I don’t think it’s valuable to rehash whether having the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. at this point is/was a success, but instead focus on how to ensure success of the WP 5.0/GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release—which I believe will be a positive thing for many people using WordPress.
      
      To that end, based on the number of unresolved issues that the Gutenberg team themselves have deemed needing to be addressed before release, and the fact that this release (unlike past major releases) relies entirely upon the readiness of Gutenberg to ship, I stand by my belief that we should delay and give the team the time needed to complete the necessary work.
    - spencerfinnell 4:38 pm on November 20, 2018
      
      > Are interesting things being built on top of it?
      
      Trying, but they break with every release. A week of “stable” code doesn’t quite give enough time to make much.
      For those whom the editor is not a good fit they can opt in at any point
      
      “at any point” means forever, not 2022. Own the breaking change or don’t break it. I’m 100% for breaking changes but “the will they/won’t they” is hard to follow.
      
      *Obligatory I love GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ as a user but this schedule is crazy as a developer.*
      - Matt Mullenweg 5:05 pm on November 20, 2018
        
        I don’t think there is a “forever” in software, but the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. nature of WordPress and the control and ownership you have of the code does insure that whatever there is market demand for will exist.
        
        spencerfinnell 5:09 pm on November 20, 2018
        
        I’m just wondering why it was announced that the Classic Editor pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party was going to be maintained until 2022 but now you’re saying it will always be available.
        
        Is there an expectation of someone maintaining a fork/something similar once official support has ended?
        
        It’s just strange that this is given a 3 year life when old PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher versions have been supported for much longer (forever).
        
        Matt Mullenweg 5:39 pm on November 20, 2018
        
        It’s not the same as running on old versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher, MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/., or ApacheApache Apache is the most widely used web server software. Developed and maintained by Apache Software Foundation. Apache is an Open Source software available for free.. The best place to read about it and ask further questions would be the announcement, which talks about it a lot more:
        
        https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/
        
        DSConcepcion79 7:43 pm on November 20, 2018
        
        I for one would like to see the classic editor along side GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. It makes maintaining sites more organic when we have options to choose from. IHMO. While Gutenberg amazing. Options are important for legacy users.
        
        Birgit Pauli-Haack 7:29 pm on November 21, 2018
        
        GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and Classic Editor can exist side by side. There is a flag available in Setting > Writing to allow for it, when Classic Editor is present on a site.
    - Frank Klein 4:49 pm on November 20, 2018
      
      Are interesting things being built on top of it?
      
      To me, this is the crucial question. But more importantly who is building these things?
      
      I would disagree that there was an “explosion” of plugins build on top of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, however I agree that there are definitely some of them.
      
      However these are all plugins either developed by commercial entities, or entities that are clearly going for monetisation in the future. The other developers using Gutenberg have, judging from what I can see, very senior profiles.
      
      I do consider that Gutenberg will be the moment that WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. finally breaks away from its hobbyist roots. Developers will either have to skill up, or be left behind eventually.
      
      The issue we currently have is that there are too few developers that can work on and with Gutenberg. So it is important that we bring a large part of the existing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher developers along when Gutenberg lands.
      
      The problem is that the available documentation is not enough, and there is not enough time between now and the release to complete it. Which does not even account for the skills needed to write that documentation, or even the time needed to maintain it with all the deprecations left and right.
      
      There’s also lack of good developer tooling, making Gutenberg a very bad experience, and a significantly worse one than just a plain ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. & Redux app. And that’s just unfortunate, because the popularity of things like React is just because of the great tooling and documentation surrounding it.
      
      So that’s why I consider that while the current back and forth on the issues is valid, it does not take into account all these other important points.
      
      Let’s not repeat the same mistake as was done with the Media relaunch in Backbone, which suffered from the same lack of documentation, and which therefore wasn’t the success it could have been.
      
      Developers should be excited to work on Gutenberg. And judging from what I hear, they are excited about the possibilities, but not really excited about having to deal with all it’s numerous issues and inadequacies.
      - Matt Mullenweg 5:07 pm on November 20, 2018
        
        That’s great feedback, and I think PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher developers learning JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors., better documentation, and tooling are crucial to continue working on. I don’t hope we will lose hobbyists, and if you’re a hobbyist learning to code today you are almost definitely learning JS and not PHP so it may even open us up to more.
        
        Milan Petrovic 11:35 am on November 21, 2018
        
        Good GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ documentation was promised last year, and we are no closer to that. Gutenberg documentation is just like any other JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. documentation in WordPress: unusable and confusing. Even the links on the first page of the Handbook don’t work properly.
        
        A friend of mine, experienced ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. developer opened the handbook to learn how to make Gutenberg 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. (and he wanted to use only the official Handbook, no other websites or tutorials). And, after two days, he gave up.
        
        I really believe that Gutenberg will be good for WordPress (just like the most of other developers posting here), but the way it was done until now, is not what WordPress is about.
        
        Developers working on Gutenberg have to stop developing, and start putting their knowledge of Gutenberg into usable documentation, into tutorials that will start with absolute basics: setup the development environment, what you need to build the code on Linux, Windows and MacOS, followed by everything else. It has to be in the official Handbook, not scattered all over the Internet. That had to be done months ago, and we are again getting same lines: it will be done sometimes in the future. Without a good Gutenberg documentation, Gutenberg will fail where it matters the most: developers embracing it and working with it.
    - Zach Tirrell 7:45 pm on November 20, 2018
      
      Here at Modern Tribe we’ve built a number of really great things on top of the WP REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.. Many of those things are proprietary to the clients we work with, but there are also a fair number of things we’ve built and released that I’d be happy to talk about.
      - Matt Mullenweg 12:11 am on November 21, 2018
        
        Yeah the agency use case was always strong, from the very beginning, just didn’t see much targeted at end-users. Please email me your examples I’m always looking for ones to highlight in the State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/., it’s been a bit of a struggle every year despite public calls to find ones we haven’t talked about already.
        
        Ross Wintle 9:40 am on November 21, 2018
        
        Yeah the agency use case was always strong, from the very beginning
        
        Well, for bigger agencies maybe.
        
        Please don’t forget that there are thousands of smaller agencies who are busy earning their living and don’t necessarily have the time to invest in re-tooling, re-skilling, etc. Many will be non-developers who’ve learned some PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher along the way and would find learning JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. a huge challenge (because with events and asynchronicity and callbacks and so on, it’s such a different paradigm).
        
        I almost raised a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ ticketticket Created for both bug reports and feature development on the bug tracker. yesterday that said PLEASE PLEASE SERIOUSLY RECONSIDER MAKING GUTENBERGGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ OPT-IN FOR UPDATED INSTALLS. I’d installed Gutenberg on a site I’m supposed to be launching in the next couple of weeks, and edited existing pages and the whole thing was an incomprehensible mess:
        
        Existing posts/pages will have a single classic editor 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., whereas new posts will open with full Gutenberg – this is very confusing and there is no prompt to convert to blocks and the convert to blocks option it hidden away
        
        Convert to blocks is buggy anyway
        
        I discovered that you can’t move a floated image. So when convert to blocks puts the image in the wrong place you’re stuck. This is a known issue that has been closed because it’s too hard to make the UIUI User interface work properly and moving a floated image is considered an ‘enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.’
        
        I still, even after a few months of using GB on and off can’t find stuff in the user interface. It’s simply too confusing. A prime example is that to fix broken convert-to-blocks I wanted to get into the “Text” tab of the classic block, but this is now not a tab and is tucked away under one of the several three-dot menus.
        
        As a small (one-man) agency owner, I simply can’t put this editor in front of existing clients, or anyone that has existing posts and pages. It’s confusing, it’s broken and I know for sure that people won’t like it.
        
        And as the developer on the job, I need more time with a stable APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and proper documentation to learn how to effectively use GB for my client projects.
        
        So please consider that yes, the 10-ups and the Human Made’s and the Modern Tribe’s have resources and time and skills to get to work with Gutenberg. But many agencies are not like this.
        
        The agency use-case is actually, in my opinion, extremely weak.
        
        Mark Wilkinson 12:49 pm on November 21, 2018
        
        Couldn’t agree more with Ross on this one.
Jonny Harris 11:01 pm on November 20, 2018

I agree with statements that @kadamwhite said. The progress with on gutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ has been amazing and I for one can’t wait for it to go into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. But things are changing for to quickly to keep up. Major changes are happening on a daily basis meaning that there no time for real user testing and reporting bugs. From my client projects using gutenberg, as soon as I get a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. report from them there is a new version of gutenberg to test it against.

I also think this the lack of offline editoring should be a showstopper, this is functionality found in core already and it’s removal without warning could have major effects on users workflows.

I wish we could get to a stage post, 4.5, we should leave the editor for a while and let people really test a stable version. Pushing to January will also give the community time to get documentation up to date and for third party plugins can be updated. This will make the update process much less painful for users and take stress of those of us who run WordPress businesses.
Robert Dall 11:59 pm on November 20, 2018

In my history in WordPress development, I have never seen so many former release leads, deputies voice concern over the launch of a feature as I have seen GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.

Where is the code freeze? I remember when you @matt wanted a code freeze where not a single confirmed bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. was ticketed for 48 hours before the release. I am not saying we need that extreme, but the flux of this code is not stable.

Yes the code will never be perfect but I just agree with @joemcgill in saying

Push back RC for at least 4 weeks so we have a reasonable deadline
- Matt Mullenweg 12:12 am on November 21, 2018
  
  I remember that attempted freeze! It was a good one.

Comments are closed.

WordPress.org

Welcome!

Communication

5.0 / Gutenberg Status Update – Nov 19

WordPress.org

Welcome!

Communication

Share this: