You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All this excitement around what was mainly a UI only prototype leads into the next question: where do we take this prototype from here? We've discussed creating two actual editor prototypes, one which uses TinyMCE as a parent of all blocks, one which uses TinyMCE as a child of each block. @iseulde has already done stellar work on the former here: https://iseulde.github.io/editor-blocks/
Let's keep it just as a UI playground for now to test ideas and to serve as the dynamic mockup for the other work. We'll be merging the TinyMCE as a parent as a separate prototype so we can work on both.
Here's what I have in mind for the different prototyping efforts:
- /gutenberg — UI prototype.
- /gutenberg/01/ — Ella’s approach.
- /gutenberg/02/ — a TinyMCE per text block approach.
- /gutenberg/03/ — a single instance of TinyMCE without any blocks just to test formatting ideas.
- /gutenberg/parser/ — the parsing explorer to test markup.
- etc
Reacted by Ahmad Awais, Erin Casali and Tammie Lister
Activity
mtias commentedon Feb 10, 2017
Let's keep it just as a UI playground for now to test ideas and to serve as the dynamic mockup for the other work. We'll be merging the TinyMCE as a parent as a separate prototype so we can work on both.
mtias commentedon Feb 10, 2017
Here's what I have in mind for the different prototyping efforts:
jasmussen commentedon Feb 23, 2017
Closing this for now, as we have found a good direction for this.
Merge pull request #51 from WordPress/tag-101-release
Merge pull request #51 from wordpress-mobile/issue/improve_propagatio…