Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phase 2 Scope & Features #13113

Closed
1 of 22 tasks
youknowriad opened this issue Dec 27, 2018 · 13 comments
Closed
1 of 22 tasks

Phase 2 Scope & Features #13113

youknowriad opened this issue Dec 27, 2018 · 13 comments
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript
Milestone

Comments

@youknowriad
Copy link
Contributor

youknowriad commented Dec 27, 2018

The following, initially outlined here, is an overview of the major functionality to be introduced in Phase 2 to help visualize the progress in terms of product scope. There’s a lot of unknown unknowns at the moment so this is a living document that will evolve and adapt over time.

💡 Focuses

Blocks beyond the Editor

Navigation block

Block Style System [#20331]

Refer to the link provided above.

Block Patterns

Full Site Editing [#24551]

Refer to the link provided above.

💎 Tightening Up

✨ New Features

✅ Done

@youknowriad youknowriad added the Framework Issues related to broader framework topics, especially as it relates to javascript label Dec 27, 2018
@youknowriad youknowriad added this to the Future: Phase 2 milestone Dec 27, 2018
@youknowriad youknowriad pinned this issue Dec 27, 2018
@iandunn iandunn unpinned this issue Dec 28, 2018
@iandunn iandunn pinned this issue Dec 28, 2018
@nicholasio
Copy link

nicholasio commented Jan 12, 2019

For the idea of themes registering content areas, Themes already do something similar using "sidebars" it looks like it might be worth seeing how this notion of content area can be used to rework Widgets/Sidebars into something more generic like content areas while maintaining backward compatibility.

@mapk
Copy link
Contributor

mapk commented Jan 12, 2019

I organized the focuses to explicitly reflect the project post of 2019 mentioned above. Also moved the previous research items up since research is an actionable item.

@glingener
Copy link
Contributor

No explicit plans for Resizing columns in the column block yet?

@youknowriad
Copy link
Contributor Author

@CGlingener If this is something that interest you, feel free to join our meetings, claim it and explore it to figure out more explicit plans. Thanks.

@michaelswengel
Copy link

Any plans to add block indentation? Indenting subparagraphs is an important feature.

@swissspidy
Copy link
Member

@michaelswengel Feel free to create a new issue for that to describe your use case there.

@michaelswengel
Copy link

@swissspidy Already done. :) #14554

@jasmussen jasmussen unpinned this issue Apr 8, 2019
@pento pento pinned this issue Apr 8, 2019
@WordPress WordPress deleted a comment Apr 9, 2019
@karmatosed
Copy link
Member

I added in user facing/tools as section with some recent issues made.

@mrfatguy
Copy link

mrfatguy commented Nov 4, 2019

Is there any priority roadmap for bugs in Gutenberg development? Is there any general idea of resolving bugs before introducing new features?

I see a lot of discussions around here about new features or how to ease Gutenberg user's lives... Yet, still no resolution on something as stupid (and in the same time affecting millions) as adding spaces when pasting text (#16172).

To paraphrase the "Upcoming Projects & Roadmap" document: Gutenberg is already in use by millions of sites through WordPress... and yet millions of editors of that millions of sites is still forced to delete two spaces, stupidly added in the beginning and end of each pasted text.

How long do we have to wait before a bug that affects general usage of Gutenberg is resolved?

@paaljoachim
Copy link
Contributor

Should this issue be updated?

@youknowriad
Copy link
Contributor Author

I think we should close this issue for now, as we have different "overview" issues for the different projects of phase2 with better organization and that are easier to follow.

@annezazu
Copy link
Contributor

annezazu commented Feb 8, 2021

For good measure since there are a lot of posts that link to this issue and many of the above linked issues are closed, here are some of those current overview issues:

Hopefully this helps anyone who finds this issue linked in other places :)

@youknowriad
Copy link
Contributor Author

Thanks @annezazu that's very helpful :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues related to broader framework topics, especially as it relates to javascript
Projects
None yet
Development

No branches or pull requests

10 participants