The customization team thought about the issues they can tackle this year \u2014 as well smaller problems for the first months of the year as bigger projects for the rest. Besides that, they noted things which should be possible by the end of the year.<\/p>\n\n\n\n\n\n\n\n
Mat\u00edas Ventura wrote in his post \u00bbEditor Technical Overview\u00ab, which aspects should be respected for the new editor<\/a>. His first point is that the whole content should stay in Second, he points out \u00bbSimplicity and Semantics of Representation\u00ab. This means that the markup to identify the blocks should be as minimal as possible because WordPress is a \u00bbchampion of web standards\u00ab and should remain it. His third point is static and dynamic blocks. Most used blocks will be static, like text or images, dynamics are something like shortcodes and widgets.<\/p>\n\n\n\n His fourth requirement is a consistent user experience. Fifth and last is the system. There are three different aspects: The UI for editing a block, the demarcation of the block and the rendering of the block. The team has to find the best technical and design solutions for these.<\/p>\n\n\n\n Finally, Mat\u00edas proposes to first tackle relatively simple blocks like text, images with and without captions, and quotes. A possible solution for demarcating the blocks could be HTML comments (code from his post):<\/p>\n\n\n The meeting was mainly about the demarcation of blocks but without a final decision. There were different proposes:<\/p>\n\n\n\n Another subject was blocks inside blocks, to realize multi-column layouts, for example. It should be kept in mind, that this possibility of nesting could be useful.<\/p>\n\n\n\n Mel Choyce published a rough plan for the customization team in her post \u00bbCustomization in 2017\u00ab<\/a>. At first, she noted, that Customization<\/em> does not only mean the customizer but the whole experience of setting up a page and editing an existing one. The two following goals should be reached (quoted from Mel\u2019s post):<\/p>\n\n\n\n For that, she listed some tasks which can be done in the first few months of the year. For example demo content on theme switch for an existing site (#38624<\/a>), lost widgets and menus on theme switch, a media widget (#32417<\/a>), and formatting options for the text widget (#35243<\/a>). Larger projects for the rest of the year are (quoted from her post):<\/p>\n\n\n\n After that, she writes the following:<\/p>\n\n\n\n \u00bbBy the end of 2017, we hope you\u2019ll be able to:<\/p> Or, shorter:<\/p>\n\n\n\npost_content<\/code> in an accessible and portable way, while additional HTML structure identifies the content blocks. This structure should be invisible to ensure the content is rendered well in situations that are not aware of the blocks (for example in feeds and old versions of the editor).<\/p>\n\n\n\n<!-- wp:image --><\/span>\n<figure<\/span>><\/span>\n <img<\/span> src<\/span>=\"\/\"<\/span>><\/span>\n <figcaption<\/span>><\/span>A picture is worth a thousand words<\/figcaption<\/span>><\/span>\n<\/figure<\/span>><\/span>\n<!-- \/wp --><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\nEditor meeting from January 19<\/h3>\n\n\n\n
data-<\/code> attributes.<\/li>div<\/code>s or similar.<\/li><\/ul>\n\n\n\nCustomization in 2017<\/h3>\n\n\n\n
\n