Tag Archives: core-editor

Joen A. 10:12 am on March 14, 2017
Tags: core-editor   

This week’s editor meeting agenda for March 14th

This week’s chat is happening tomorrow, Wednesday March 14 19:00 UTC. Note, daylight saving time has kicked in in parts of the world, but not all, so be sure to follow the time link to see what it converts to in your location.

The agenda is:

  • The technical prototypes are in the home stretch. Any observations on recent developments? Hopefully we can start work on plugins very soon.
  • Day to day work happens in GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ mostly. Lots of tickets since last time. Any you’d like to discuss?
  • Anything else?

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🍒

Ahmad Awais 4:25 pm on March 9, 2017
Tags: core-editor   

🎯 Core Editor Meeting Notes 2017-03-08

The GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ project has been going great. Lots of activity, Slack fun meetings, GitHub issues are filled with discussion, you’ll love to read. Here’s the meeting summary for this week’s editor team meeting (agenda here) in #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. States

There was a good deal of discussion around the states of a block in general. General consensus led to the following decisions/suggestions (Mockups should be further improved to include five states mentioned below):

  1. Normal
  2. Hover
  3. Editing
  4. Selected block
  5. Selected content within the block

There’s more:

  • Empty State (optional for some, but important for extension flexibility)
  • Ticket for fail-states, like broken hyperlinks and images that didn’t upload, block-parse errors. Even warnings if you try to publish with placeholders.

Moreover, following discussion took place:

  • Text Selection: Selecting text, whether by mouse or via keyboard nav, should invoke controls.
  • Embeds: Include embed in tech requirements, as well as the neutral state.
  • Ticket: What happens to block controls when you page down a draft, when do they show up? On select, on arrow keys, on PgDn? We will discuss further in a ticket.
  • Testing: @karmatosed is offering to test things at upcoming WordCamps. Let her know your ideas in #core-editor.
  • Link Boundary Feature: Everyone loves the link boundary feature. Some accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues that are solvable.

That’s about it, happy hacking!

Joen A. 10:51 am on March 7, 2017
Tags: core-editor   

This week’s editor meeting agenda for March 8th

This week’s chat is happening today, Wednesday March 8 19:00 UTC.

The agenda is:

Feel free to leave a comment and we can add to the agenda!

See you in the #core-editor channel in Slack! 🦄

Joen A. 10:53 am on February 28, 2017
Tags: core-editor   

This week’s editor meeting agenda for March 1st

This week’s chat is happening  Wednesday February 29 19:00 UTC.

The agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🌈

Joen A. 12:02 pm on February 22, 2017
Tags: core-editor   

This week’s editor meeting agenda for February 22

This week’s chat is happening today, Wednesday February 22 19:00 UTC.

The agenda is:

  • The UI prototype received a number of updates based on feedback from the week before, let’s discuss.
  • Mockups were updated, and collected on Github, thoughts?
  • Some more thoughts on <IE11+ support and how to proceed.
  • Anything else?

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🚀

Joen A. 10:35 am on February 15, 2017
Tags: core-editor   

This week’s editor meeting agenda for February 15

This week’s chat is happening today, Wednesday February 15 19:00 UTC.

This weeks agenda is:

Feel free to leave a comment and we can discuss anything people want.

See you in the #core-editor channel in Slack! 🚀

Joen A. 12:34 pm on February 8, 2017
Tags: core-editor   

Agenda for February 8 Editor Chat

In past mockups we sketched out how inserting blocks in a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based editor might work. For the #core-editor chat today, let’s talk about a couple more ingredients: block controls, and changing block types.

It could work like this — click a block to surface block level controls, select text to surface inline controls:

Click the block type indicator to switch to a different, compatible, block:

For the chat, let’s talk about this approach. Questions, comments, ideas? Feel free to bring them up, you can start with commenting here.

Let’s also discuss this wonderful post by Reid Peifer about the editor content creation. What are the best pieces we can learn from?

It all goes down today, Wednesday, 8 February 2017, 19:00 CET! 🎉

Joen A. 8:48 am on January 25, 2017
Tags: core-editor   

What Are Little Blocks Made Of?

At the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. of the 2017 editor focus is the is idea of introducing blocks (or sections) which help “make it easy what today might take shortcodes, custom HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., or ‘mystery meat’ embed discovery”. How do we do that?

Let’s start with paragraphs as blocks/sections. If we count a paragraph as a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. or section you can manipulate, here’s how that could look:

You can still type type type but you create blocks along the way. When you mean to insert content that isn’t text, click the plus (or perhaps as a power-user feature, type / on a newline, SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.-style?), to invoke the insert menu:

Click an item to insert it, or pick it using arrow keys.

One of the interactions we need to figure out here, is what happens when you press Enter, as you’re writing. Over chat in the past week it was suggested we might want to tweak the default behavior so that Enter inserts just a single linebreak, and a new paragraph is created with two linebreaks. (The pertinent bits of the chat starts here, or you can read this summary).

Let’s discuss these mockups, data structure, linebreaks and lots more in Wednesdays editor chat, Wednesday January 25th 19:00 CET! And please keep the feedback coming, here and in #core-editor Slack, the feedback already given has been amazing.

The next immediate goal is to start building prototypes. It’ll be a blast! 🚀

Joen A. 2:48 pm on January 11, 2017
Tags: core-editor   

What makes a great editor?

The editor will be a big focus in 2017, so let’s chat about what makes a great editor. Perhaps it’s good to look at what’s there, and compare that with the goals we mean to achieve:

The editor will endeavour to create a new page and post building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., or “mystery meat” embed discovery.

Here’s what the editor looks like today, with everything enabled:

editor screenshot

Obviously not all of that is ever shown to users, but a lot of it is. Even then, it’s not immediately obvious just how many things you can actually embed right out of the box in WordPress, which is what mystery meat embed discovery refers to.

And so when looking at how to improve the editor to both improve but also surface the wealth of features already there, we’ll need to add new UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.. To balance that out in an already busy configuration, we need to find a way to also reduce and revisit existing UI, so we don’t end up with something overwhelmingly complex. That could mean combining where we can, minimizing where we can, deprioritizing in places, and freeing up space as much space as we can.

There are many ways to get there. Since WordPress accomodates a lot of workflows, it’ll be a fun challenge to improve things for as many as we can, so we’ll need to discuss and research.

To kick things off, let’s discuss editor improvements! What’s on your wishlist for an improved editor?

Feel free to share here, and please also join us in #core-editor. We’re holding weekly meetings in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., Wednesdays at 19:00 CET. The next one is today, Wednesday January 11th 19:00 CET. Join in the fun!