Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Scope & Features: MVP #4894
Editor Feature Complete
The following is an overview of the major functionality to be introduced by the new WordPress editor, helping visualize what has been done and what remains to be done in terms of product scope.
Have to wonder who exactly defined this as "MVP"? I do not remember any slack discussion in any of the main developer chats, not a "make" post open for discussion. Requests for a definition of the content of the project on github went un answered.
Specifically for me an official API to turn gutenberg off, at least for the first few releases until it is stabilized and bugs and design problems are worked out is a must and should be part of any MVP.
yeh yeh yeh I know what @pento said, but with all due respect this is a decision for the community to make, not a decision of one person.
@maddisondesigns changing the page template was merged in #4662. Editing the permalink was added in #3418 but reverted due to UX issues. Should come in one of the future releases as part of the merge proposal milestone.
@markkap this is just covering what we have been working on and what has been on the radar for the plugin version of Gutenberg. It doesn't cover the merge proposal or what would be shipped in 5.0 — we might remove certain features, add others, etc.
referenced this issue
Feb 9, 2018
@mtias A couple related questions for when you have the time.
Mostly in the context of what wasn't part of the "feature complete" milestone. There are various high-level issues that had been discussed in multiple places, including REST API issues, packages and JS modules, cleaning function names, hook documentation, etc. Probably the best is to have a core dev chat once we wrap the "feature complete" milestone to discuss this and figure out the next steps.
For the most part, yes. Though it hasn't had a lot of dedicated attention, and some things might not be necessary for a merge proposal provided we add them for the betas. This is something we need to discuss. It's likely that the merge proposal itself will bring things more into the light and more people would engage, which would be very beneficial, so that's also something to keep in mind.
As much and as varied as possible, while being aware that this could also be an endless effort. There's the item, punted from 4.9, about showing a notice in wp-admin for trying out the new editor. That might be something we'd want to look at in the coming weeks for a point release once we feel comfortable with the experience. We are also likely looking at beta testing on WP.com around a similar timeframe to get more broad feedback and usability testing running in parallel.
My current thinking is along the lines of getting things ready and polished enough for merge proposal so that we can do broader testing with it. The whole process for 5.0 is very much something we should discuss more broadly and with more participation.
Just added that to the merge proposal milestone. It would be great to get more help from core contributors during the triage sessions @jeffpaul is running on Thursdays to cover more ground.
Thanks for the questions @johnbillion !
I have some questions and concerns.
As an outsider, how can I be assured that the product is anywhere near satisfying the functional and non-functional requirements. I don't know what's in scope, what's out of scope or how complete anything is. This is a complex project with many more risks than there have been in the past. I've been trying to get close to the project but really have no idea of the big picture.
According to "Our philosophies", Every version of WordPress should be easier and more enjoyable to use than the last. While this may be true for a new install, I see very little concern for existing sites.
I would like to know what each stage of the project will deliver with regards to the reference documentation that will be required by any user/developer who has a problem.
I'm not aware of any trackable plan. I'm not even sure if there is a plan for the plan.