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

Open
youknowriad opened this Issue Dec 27, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@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.

Actionable Items

💡 Focuses

Widgets to blocks

Widget-block interface integration

  • Integration of the blocks editor to the Widgets screen [#13204]
  • Integration of the blocks editor to the customizer [#13205]
  • Reusable BlockEditor component that can be embedded in several screens [#13088]

Navigation block

  • Menu Navigation Block [#1466]
  • Integration of the blocks editor to the Menu Screen [#13206]

Themes registering content areas in Gutenberg

  • Theme registering content areas for Gutenberg editing

💎 Tightening Up

  • Server-side registration [#2751]
  • Section/Container block [#4900]
  • Quote/Cover block with nested elements
  • Drag & Drop Gallery Items [#743]
  • Resizing columns in the column block
  • Improve Keyboard Interactions (list shortcuts, tabbing..) [#9611, #11581 ...]
  • Improvements to Media Interactions #11952
  • Drag an image over another to create a Gallery [#9783]
  • Better undo
    • Fixing any undo traps
    • Making sure undo steps in macro-interactions (conversions, etc.) feel right
    • Making sure undo steps in micro-interactions (mostly: rich-text editing) feel right
    • Fixing "misplaced" carets, likely by tracking selection state in undo history
  • Accessible Autocomplete component to use instead of unbounded requests [#7384]
  • Continual work on performance [#11782]
  • Tip improvements to help with the paradigm shift of blocks. [#9242]
  • Microinteractions [#8029]
  • Continual triage

🗺 To discuss

  • Better style variations and theme integration API [#7551]
  • Responsive layouts and grids[#4314, #13203, #13363]

Blocks

  • Improvements to the Nested Blocks interactions (selection…) [#13319]
  • Title block [#11553]
  • HTML block with components and custom CSS
  • Simple block + simple block = complex block (combining blocks by drag n drop to form more
    complex existing blocks) [#13202]
@nicholasio

This comment has been minimized.

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

This comment has been minimized.

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.

@CGlingener

This comment has been minimized.

Copy link
Contributor

CGlingener commented Jan 13, 2019

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

@youknowriad

This comment has been minimized.

Copy link
Contributor

youknowriad commented Jan 14, 2019

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment