Joen Asmussen

Hi there. I’m helping with date picker improvements in Gutenberg, you can see that tabbing will be improved in the next version here: https://github.com/WordPress/gutenberg/pull/7621#issuecomment-412383364

Appreciate your time to elaborate, thank you.

I don’t understand why core team is focused on this extend. We still haven’t native SEO fields, Accents in attachment file names are still there (5 years ticket https://core.trac.wordpress.org/ticket/22363 )

To clarify, the Gutenberg team is not the core team. We’re a small band of people crazy enough to take on this task, knowing how difficult it would be. While we’ve had a whole slew of contributions from the community (just look at this list), there’s still only six or seven of us doing the bulk of the work. We’ve made a bunch of progress in a short time, but we know that there’s still a long way to go.

What make WordPress is, is the simplicity and the fact of being able to do everything that one wishes. Why compromise the core and this philosophy?

I agree. This is exactly why we are building Gutenberg. It is built on the idea that we can take the flexibility and strength that you get with shortcodes, custom HTML, theme styles, and expand it drastically, put it front and center, and make the UI much easier. Take the Cover Image, for example, it expands quite a bit the kind of layouts you’re able to do with just a simple block. Here’s a video:

Right now we are focused on building this _editor_, and working hard to get the blessing that we might be considered for merge into WordPress. This is not a done deal.

If we get that blessing, there are many ways a merge can happen, probably including ways that’ll let you keep using the old editor. See some of the ideas here.

@thierrypigot I would really appreciate if you could expand on _why_ you so dislike Gutenberg.

I’m very sorry you haven’t had a good experience testing the plugin. I’d also like to clarify that it’s not up to me whether it reaches core or not. I can only do the best work I can, try to build the very best editor.

My deeply personal motivation in working on Gutenberg is to ensure WordPress has a future, that it is relevant for the webdesigners of tomorrow. Balancing that fact with ensuring we don’t break backwards compatibility unless we _absolutely have to_, and formulating a strategy for actually rolling Gutenberg into core (should it hopefully reach a state of completeness when we could get such a blessing) — it’s just difficult, and we have to be thoughtful about it.

In the mean time, our highest priority is improving Gutenberg to a point where people can see what it might do for WordPress. As uamv says, we are absolutely working very hard on that, and I hope you’ll try a more recent version of Gutenberg and give us actionable feedback! Thanks.

There are many many ways to roll out Gutenberg. Right now we are focusing on making it as good as we possibly can, so that it might be considered for inclusion in WordPress. Actionable feedback would be really helpful to make that happen.

I’m sorry you didn’t like the experience, and hope that you’ll try it again. We are making weekly releases, and I’m crossing my fingers you’ll like 0.8 planned to come out friday.

Sorry you had a bad experience. We’d love to hear any specific feedback, as we’re working hard on this project every day, and are making weekly releases.

Please see also our FAQ, and our design/vision document:
https://github.com/WordPress/gutenberg/blob/master/docs/faq.md
https://github.com/WordPress/gutenberg/blob/master/docs/design.md

I’m easy to reach if you have further questions.

Thank you so much for your review, it’s very motivating. As you can no doubt tell it’s very hard work, and I completely agree, we have much more work to do still, lots of rough edges to polish. Reviews like this will let us keep up the steam so hopefully we can improve Gutenberg faster!