Welcome to ManageWP.org

Register to share, discuss and vote for the best WordPress stories every day, find new ideas and inspiration for your business and network with other members of the WordPress community. Join the #1 WordPress news community!

×

6 min read Phpbits Studio
Community | make.wordpress.org | 9 days ago

What’s new in Gutenberg? (9th August)

Here are the updates for WordPress Gutenberg Editor 3.5.0 (9th August).

What’s new in Gutenberg? (9th August)

Community | make.wordpress.org | 9 days ago

Another update has sailed! This one comes after WordPress 4.9.8 release with the “try the new editor” notice, which has increased the number of installs from 15k to more than 120k in a few days. This is an important milestone as we broaden the testing horizons. We’d like to take a moment to thank everyone that has tested and given feedback through the various channels. Likewise, huge thanks to everyone that has helped answer questions, addressed forum feedback, triaged new issues, fixed bugs, and generally jumped in to contribute.
Back to the release, this one includes several fixes, polish, and cleaner interactions around the writing flow. On the developer side, there’s been work around refining and adding to the pool of APIs and documentation.
3.5
Add an edit button to embed blocks to modify the source.
Improve margin collapse within column blocks.
De-emphasize inline tokens within the inserter for a better user experience.
Polish focus and active styles around buttons and inputs.
Polish styles for checkbox component, update usages of toggle to checkbox where appropriate. Update documentation.
Improve pre-publish panel styling and textual copy.
Prevent duplicate

3 min read David McCan
Community | make.wordpress.org | 19 days ago

What’s new in Gutenberg? (30th July)

At this point in development I'd expect only fixes, but features are still being added. This release adds an inline block API, a modal component, exposes more developer options for mobile, and of course a slew of fixes.

What’s new in Gutenberg? (30th July)

Community | make.wordpress.org | 19 days ago

Today’s release is timed to coincide with the upcoming WordPress 4.9.8 release, and includes a multitude of improvements when converting existing content to blocks. The Inline Block API has also landed in this release, allowing images to be inserted into any rich text area. You can even put an image into another image’s caption!
3.4
Add the Inline Blocks API.
Rename Shared Blocks to Reusable Blocks.
Add a Modal component.
Add a REST API Search controller.
Add a warning in the classic editor when attempting to edit a post that contains blocks.
Add ability for themes to configure font sizes.
Add RTL CSS to all packages.
Add an edit button to embed blocks.
Remove all wp.api usage from the editor package.
Add error handling for file block drag-and-drop.
Add registerBlockStyleVariation, for registering block style variations.
Add a border between panels in the block sidebar.
Add a editor.PostFeaturedImage.imageSize filter for the Featured Image.
Create a video block when dropping a video on an insertion point.
Expose a custom class name hook for mobile.
Add a React Native entrypoint for mobile.
Only disable wpautop on the main classic editor instance.
Retain the id attribute

7 min read David McCan
Community | make.wordpress.org | Jul. 6, 2018

What’s New in Gutenberg? (6th July)

Gutenberg 3.2 is the minimum viable product release in terms of features. Block style variants, an in-line images and blocks API, a file block, and converting columns to parent and child blocks are some of the new features. From this point forward the team will focus on bugs, enhancements, compatibility, and stability.

What’s New in Gutenberg? (6th July)

Community | make.wordpress.org | Jul. 6, 2018

This release generally completes our MVP feature set for the editor by adding inline images, block style variations, and a new columns approach. Switching focus to bugs, enhancements, compatibility, and API stability from now on. Worth noting that there’s people working on some more individual blocks (a few widgets and playlist) to be included when ready. The most significant addition is block style variations. This will allow registration of alternate styles (based on class names) for any block, with automated real thumbnails and live previews built in to the block transformation tool. We have added them to the Quote, Button, and Separator blocks for illustration. The public API will be exposed in a future release.
3.2
Add block styles variations to the Block API.
Add support for Inline Images and Inline Blocks API.
Convert Columns to a set of parent and child blocks, including a wrapper element and more reliable front-end presentation.
Allow registering new block categories.
Add support for locking Inner Block areas.
Add File Block for uploading and listing documents, with drag and drop support.
All Updates
Introduce Modal component to expand the extensibility suite of UI components.

2 min read Donna Cavalier
Development | make.wordpress.org | May. 23, 2018

WordPress 5.0 Development Cycle - When Gutenberg Will Appear...

Ok, we don't have an exact date, but at least we know it won't be until after...

WordPress 5.0 Development Cycle - When Gutenberg Will Appear...

Development | make.wordpress.org | May. 23, 2018

Goals (To be posted) | Dev Chat Agendas | Dev Chat Summaries | Dev Notes | Field Guide (To be posted) | All Posts Tagged 5.0 WordPress 5.0 will be the first “major” release of 2018, including the new editor, codenamed “Gutenberg”.
Release Schedule
November 15, 2017
Trunk is open for business. (Post-4.9)
TBD
5.0 Kickoff meeting.
TBD
Last chance to merge feature projects.
TBD
Beta 1 and feature project merge deadline.
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only bug fixes and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point, and can be picked up for commit again at the start of WordPress 5.1.
TBD
Beta 2.
TBD
Beta 3.
TBD
Beta 4.
TBD
Release candidate and soft string freeze.
TBD
Final release candidate if needed and hard string freeze.
TBD
Dry run for release of WordPress 5.0 and 24 hour code freeze.
TBD
Target date for release of WordPress 5.0.
Contributing
To get involved in WordPress core development, head on over to Trac and pick a 5.0 ticket. Need help? Check out the Core Contributor Handbook. Get your patches done and submitted as

8 min read David McCan
Community | make.wordpress.org | Jun. 6, 2018

What’s new in Gutenberg? (5th June)

Update number 30, or version 3, has lots of improvements and fixes. Included in the update are child blocks and the option for themes to declare support for block styles.

What’s new in Gutenberg? (5th June)

Community | make.wordpress.org | Jun. 6, 2018

This release marks the 30th update to the editor plugin. The highlights are broken down below. Block Library
Arguably, one of the key pieces of the new editor UI is the block library or inserter. Unifying the way users can insert content has been one of the main objectives of the whole project. It has gone through multiple iterations and testing; balancing clarity, usability, flexibility, and extensibility. This release offers the result of some very fruitful collaborations between designers and developers.
Notably, tabs are being removed; blocks have bigger surface areas; and plugins can supply a distinct color for the block icon background. This seeks to allow the inserter to better scale while retaining visual clarity. The other addition to the inserter is related to the new concept of child blocks explained below.
Child Blocks
The editor has had support for nesting blocks since around the beginning of this year. With 3.0, a block author can now also register a block as being a child of another block by declaring parent: [ 'block-name' ]. This now causes a few changes in the interface: the root inserter won’t show child blocks unless the user is within the context of the right

6 min read Asphalt Themes
Community | make.wordpress.org | May. 4, 2018

What’s new in Gutenberg? (May the 4th)

This release has many refinements and improves the capabilities of the Block and Plugin APIs. It also adds a new “spacer” block for generating visual space. The color palette component has been improved to be based on classes instead of inline styles (for registered colors) and includes some important accessibility improvements (like naming the color). Thank you to everyone involved!

What’s new in Gutenberg? (May the 4th)

Community | make.wordpress.org | May. 4, 2018

Things are going well on the road towards completing the first phase of the editor project. Most of the work is centered around polish, getting things ready for merge, and tightening existing APIs. CloudupBlogLoginAboutBlogFaqTermsPrivacy
This release has many refinements and improves the capabilities of the Block and Plugin APIs. It also adds a new “spacer” block for generating visual space. The color palette component has been improved to be based on classes instead of inline styles (for registered colors) and includes some important accessibility improvements (like naming the color). Thank you to everyone involved!
2.8
Add a pasting schema in raw content handling. It simplifies whitelisting and reduces the amount of filters run. Should improve reliability, clarity, markdown conversion, and usage in blocks.
Add “Spacer” block to create empty areas.
Expand public InnerBlocks API with support for template configuration and allowedBlocks logic.
ColorPalette improvements:
Implement mechanism to use classes for configured colors instead of inline styles. Use it in Button block as well.
Use color name in ColorPalette aria-label for making color selection more accessible.

Community | make.wordpress.org | Apr. 9, 2018

Important Changes in Theme Review Process

Great news for theme developers worldwide! The theme review team introduces a simplified review process with the purpose of reducing the wait time before a theme goes live!

Important Changes in Theme Review Process

Community | make.wordpress.org | Apr. 9, 2018

We all know that queue time is around 3 months. We have quite a small numbers of active theme reviewers at the moment, and even when a ticket is being reviewed, the review process itself can take pretty long to complete. The change is based on moving burden from reviewer’s shoulder to theme author’s and making theme authors more responsible. From today, reviewers can check mainly following issues to pass the review.
Security
Licensing
Malicious or egregious stuff
Content Creation
Although these are the points to pass the theme review, theme authors are expected to follow the guidelines (required and recommended) like how it is going currently.
Moderators will spot check the themes after it is set live. If theme authors are found intentionally not following the guideline, Moderators will ask theme authors to fix the critical issues. In the case of not abiding the guidelines, theme could be on temporary or permanent suspension.

4 min read Ahmad Awais
Community | make.wordpress.org | Apr. 5, 2018

What’s new in Gutenberg 2.6? (5th April)

And as we all know it Gutenberg keeps improving. The new version brings drag and dropable blocks. Yay!!!

What’s new in Gutenberg 2.6? (5th April)

Community | make.wordpress.org | Apr. 5, 2018

This release introduces drag and drop capabilities for sorting blocks, various refinements to the block visual interface (including a label with block type identifier) and extensibility APIs, plus a lot of bug fixes. Thanks to everyone who contributed for all the ongoing efforts! CloudupBlogLoginAboutBlogFaqTermsPrivacy
2.6
Add drag and drop functionality to reorder blocks (in addition to arrow movers).
Improve side UI around nested groups and introduce a block name label on hover.
Focus the block inspector automatically when a block is selected.
Allow extending auto-completers via filters — this also exposes the "user" auto-complete to all RichText component instances, making it much easier to leverage for external blocks.
Use debounced search request in user auto-complete mechanism improving the experience of mentioning in sites with more than 100 users.
Other changes
Use custom serializer for texturize compatibility. This removes dependency on react-dom/server and integrates better with wptexturize expectations.
Group advanced block settings (class name and anchor) in a panel.
Move Post Types Data Fetching to the core-data module.
Refactor DocumentOutline to use the

6 min read David McCan
Community | make.wordpress.org | Apr. 19, 2018

What’s new in Gutenberg? (18th April)

Gutenberg 2.7 includes a ton of fixes and improvements. We are on the path for release now as the number of blockers are being whittled down.

What’s new in Gutenberg? (18th April)

Community | make.wordpress.org | Apr. 19, 2018

This release introduces a number of visual refinements around block controls (hover areas, link modal, Classic block), a new block for pagination, and pushes much of the Plugin API out of its experimental stage. Thank you to all the contributors for their efforts, and welcome to the new faces seen throughout the release cycle! CloudupBlogLoginAboutBlogFaqTermsPrivacy
2.7
Add pagination block (handles page breaks core functionality).
Add left/right block hover areas for displaying contextual block tools. This aims to reduce the visual UI and make it more aware of intention when hovering around blocks.
Improve emulated caret positioning in writing flow, which places caret at the right position when clicking below the editor.
Several updates to link insertion interface:
Restore the “Open in new window” setting.
Remove the Unlink button. Instead, links can be removed by toggling off the Link button in the formatting toolbar.
Move link settings to the left.
Update suggested links dropdown design.
Allow UI to expand to fit long URLs when not in editing mode.
Rework Classic block visual display to show old style toolbar. This aims to help clarify when you have content being displayed

Community | make.wordpress.org | Dec. 28, 2016

Matt Mullenweg Announces Supporting the Future of WP-CLI

Great news! The website and code are all coming in under the WordPress.org umbrella and financial support is also involved.

2 min read Omaar Osmaan
Development | make.wordpress.org | Apr. 23, 2017

WordPress Target Browser Coverage - Ending support for IE 8, 9, and 10

WordPress officially ending support for Internet Explorer versions 8, 9, and 10, starting with WordPress 4.8.

WordPress Target Browser Coverage - Ending support for IE 8, 9, and 10

Development | make.wordpress.org | Apr. 23, 2017

Previously, we discussed the new editor and browser support within WordPress core. Following up on those conversations, we are officially ending support for Internet Explorer versions 8, 9, and 10, starting with WordPress 4.8. Microsoft officially discontinued supporting these browsers in January 2016, and attempting to continue supporting them ourselves has gotten to the point where it’s holding back development. I realize that folks still running these browsers are probably stuck with them because of something out of their control, like being at a library or something. Depending on how you count it, those browsers combined are either around 3% or under 1% of total users, but either way they’ve fallen below the threshold where it’s helpful for WordPress to continue testing and developing against. (The numbers surprised me, as did how low IE market share overall has gone.)
Of course, wp-admin should still work in these older browsers, but with fewer capabilities, and we will no longer be testing new features and enhancements in these browsers. For example, the next versions of TinyMCE – currently targeted at WordPress 4.8 – will not support older IE browsers.

Community | make.wordpress.org | May. 18, 2018

WordPress logos on cakes

My vote for headline of the year so far! The Foundation added a special note specifically to bakers in advance of the 15th anniversary parties.

WordPress logos on cakes

Community | make.wordpress.org | May. 18, 2018

As hundreds of people plan their WordPress 15th anniversary parties, the community team is fielding more and more requests for special letters granting bakeries permission to frost the WordPress logo onto cakes and other delicious baked goods. A line specifying permission has been added to the WordPress Trademark Policy to help ease the concerns of bakeries around misuse of the WordPress logo, and to make it easier for our volunteers to get yummy, WordPress-y cake/cookies/cupcakes/babka/dorayaki/etc.
If you’re arguing with your baker and this addition to the TM policy page does not resolve their concerns, please email support@wordcamp.org, and we’ll try to help.

5 min read Ahmad Awais
Community | make.wordpress.org | Jan. 25, 2018

What’s new in Gutenberg2.1? (25th January)

OK OK, another #Gutenberg release. This time with a lot of fixes and refactorization of features + code.

What’s new in Gutenberg2.1? (25th January)

Community | make.wordpress.org | Jan. 25, 2018

This release iterates further on some design and writing flow details — lighter up/down movers, engaging the UI-less focus mode more often, etc. It also brings many extensibility API improvements, exposing internal editor state through selectors, enhancements to the meta-box handling, and implements the "Copy All" button as if it was a plugin as an example of how to leverage native hooks. 2.1
Iterate on the design of up/down arrows and how focus is managed. This seeks to further reduce the visual and cognitive weight of the up/down movers.
Show immediate visual feedback when dragging and dropping images into the editor. (Expands on the previous release work.)
Expose state through data module using selectors. This is an important piece of the extensibility puzzle.
New button outline and focus styles.
Show original block icon after converting to reusable block. Also hides the generic reusable block from inserters. This moves data logic out of the inserter.
Introduce a migration function for block versioning.
Add HTML handler to dropzone. Allows drag and dropping images from other web pages directly.
Trigger typing mode when ENTER or BACKSPACE are pressed. This improves

2 min read Ahmad Awais
Community | make.wordpress.org | Oct. 10, 2017

What’s new in Gutenberg 1.4? (October 10th)

Gutenberg continues to improve. Version 1.4 is now out — you can change the HTML of an individual block now.

What’s new in Gutenberg 1.4? (October 10th)

Community | make.wordpress.org | Oct. 10, 2017

With this release Gutenberg allows you to make edits and tweaks to the HTML of individual blocks, without having to hunt for the relevant code in the full document view. Redesigned the header area of the editor for clarity—groups content actions in the left, and post action in the right.
Group block settings (delete, inspector, edit HTML) on an ellipsis button.
Added new reusable Dropdown component.
Show frequently used blocks in the inserter shortcuts (at the bottom of the post).
Other changes
Offer option for the button block to clear content.
Refactor block toolbar component in preparation for some iterations (docked toolbar, for example).
Allow partial URLs in link input.
Avoid using state for tracking arrow key navigation in WritingFlow to prevent re-renders.
Improve mobile header after design cleanup.
Add focusReturn for Dropdown component.
Updated Audio block markup to use figure element.
Removed transition on multi-select affecting the perception of speed of the interaction.
Show Gallery block description even if there are no images.
Persist custom class names.
Merge initialization actions into a single action.
Fix scroll position when reordering blocks.
Fix case where

8 min read Ashar Irfan
Community | make.wordpress.org | Oct. 24, 2017

A New Themes Experience in the Customizer

New themes experience in Customizer in WordPress 4.9 will enhance theme browsing, and customizing experience.

A New Themes Experience in the Customizer

Community | make.wordpress.org | Oct. 24, 2017

WordPress 4.9 introduces a new experience for discovering, installing, and previewing themes in the customizer. Building on efforts during WordPress 4.7 development, this project prioritizes user flow, extensibility, and performance improvements. A theme is the most fundamental aspect of customizing a site. This project seeks to unify the theme-browsing and theme-customization experiences by introducing a comprehensive theme browser and installer directly in the customizer.
The new flow seamlessly integrates theme management into the customization experience by bringing a new theme browsing framework into the customization interface along with the ability to install and live-preview a theme in a single click.
The new theme browser is designed for extensibility. Third-party theme directories are encouraged to integrate with the core experience via plugins. Because the new browser is built on the core customize API, extending it is similar to extending any other part of the customization experience. As with every aspect of the customizer, this project approaches extensibiity modularly and in terms of both user and developer experience. The end of this post includes a technical overview

Community | make.wordpress.org | Oct. 17, 2017

Research Before You Sell Out - Make.WordPress.org

Here Mika is sharing kind of words of wisdom about selling out Plugin specially. As we have seen recently deal gone wrong, and hundreds of thousand users become vulnerable because new owner has evil intention, this post was very necessary.

Research Before You Sell Out - Make.WordPress.org

Community | make.wordpress.org | Oct. 17, 2017

Are you thinking of selling your plugin? Did someone offer you money to put a link to their sites in your readme or wp-admin settings page? STOP. THINK. BE CAUTIOUS.
I’m sure most of you are aware of the recent bad behaviour that’s gone on with regards to unscrupulous people purchasing plugins and using them to leverage malware, spam, and backdoors. While we would never tell you that it’s wrong to sell the plugins (they’re yours after all), we do want to help you recognize the warning signs of a bad-faith purchase.
Above all, if anything in the process makes you nervous and feel like something is wrong, call the deal off. You can email us at plugins@wordpress.org and we can help vet the buyer for you.
But remember this: The primary reason people want to buy ‘popular’ plugins is to use it to spam.
Signs To Watch Out For
Here are some basic red-flags:
You get an unsolicited email that reads like a generic form
The offer includes different prices based on how many people use the plugin (i.e. $500 for every 1000 users)
The amount offered seems to be rather high ($50,000 USD for a plugin)
The offer comes from a company who claims to be purchasing a ‘suite’

24 min read Donna Cavalier
Tutorials | make.wordpress.org | Apr. 25, 2018

WordPress Jargon Glossary

Sort of an odd collection of chosen words that they are defining, but useful to beginners in any case.

WordPress Jargon Glossary

Tutorials | make.wordpress.org | Apr. 25, 2018

downloadable PDF as a resource for you. .htaccess
.htaccess is a configuration file for use on web servers running the Apache Web Server software. When a .htaccess file is placed in a directory that is in turn ‘loaded via the Apache Web Server’, then the .htaccess file is detected and executed by the Apache Web Server software.
a11y
Accessibility (https://a11yproject.com/). A11y is an acronym for accessibility. The 11 represents the 11 letters that were removed between the a and y to make accessibility shorter to write particularly on social media.
Apache
Apache is the most widely used web server software. Developed and maintained by Apache Software Foundation. Apache is an Open Source software available for free.
API
An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
Atom
Free and Open Source text editor designed for code development- https://atom.io/.
Avatar
An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name.
Back-end developer

3 min read Asphalt Themes
Community | make.wordpress.org | Apr. 24, 2018

Gutenberg, REST API, and you

As you may know, Gutenberg uses the WordPress REST API as a bridge between the land of JavaScript and land of PHP. There were a whole host of conceptual challenges in translating WordPress internals to REST — and even more we still haven’t solved!

Gutenberg, REST API, and you

Community | make.wordpress.org | Apr. 24, 2018

Fancy yourself some challenging architectural puzzles? Have we got the ticket for you! As you may know, Gutenberg uses the WordPress REST API as a bridge between the land of JavaScript and land of PHP. There were a whole host of conceptual challenges in translating WordPress internals to REST — and even more we still haven’t solved!
We’d love your help Read through and comment on the issues linked below as you have time. Then, if you’re available, join the next REST API office hours for a rousing conversation: April 26, 2018 5:00:00 PM GMT
Category, tag, and taxonomy controls don’t respect the correct capabilities
A user should be able to set terms on a post if they have assign_terms, and can create new terms if they have assign_terms for a non-hierarchical taxonomy, or edit_terms for a hierarchical taxonomy. However, capabilities are evaluated at runtime which means we can’t use them declaratively in Gutenberg. It would be nice if there was some existing REST paradigm we could incorporate.
Support for automatically iterating paginated resources in core-data
Gutenberg has a new withSelect() JavaScript API to fetch data from the REST API. Problems

10 min read Asphalt Themes
Community | make.wordpress.org | Apr. 20, 2018

4.9.5 Feedback: leading a WordPress minor release

WordPress 4.9.5 was released a couple of weeks ago, at the scheduled time and without known issues. Below you will find some feedback and tips we wanted to share with you and we hope this will encourage others to get involved in such an adventure.

4.9.5 Feedback: leading a WordPress minor release

Community | make.wordpress.org | Apr. 20, 2018

WordPress 4.9.5 was released a couple of weeks ago, at the scheduled time and without known issues. We (@audrasjb and @danieltj) had the pleasure to co-lead this minor release of the CMS, with @sergey‘s invaluable help as deputy and @jbpaul17’s mentorship. For this release, we were two co-leaders, contributing to the core for a short time, and none of us had core committer status. Thank you all again for trusting us for this task.
Below you will find some feedback and tips we wanted to share with you and we hope this will encourage others to get involved in such an adventure.
To lead a WordPress release, you don’t have to be a core committer,
you have to deeply care about the WordPress open-source project.
Initially, we wondered how the two of us could claim to run a WordPress release without commit access.
In fact, there are many tasks that are not related to the commit action itself, but require a good knowledge of the ecosystem, the people and teams involved and how the release process works. Here are some examples of tasks to do:
Triage: sorting tickets and status update. This is a very time consuming task, because you have to dive into each ticket, read all the

3 min read Matt Cromwell
Community | make.wordpress.org | Mar. 29, 2018

All wp.org designers now can get access to Invision

Pretty great perk of being a volunteer designer for wordpress.org -- free InvisionApp access!

All wp.org designers now can get access to Invision

Community | make.wordpress.org | Mar. 29, 2018

As was posted a few weeks ago and covered in the weekly design meeting, @johnmaeda working with Invision, has arranged for us all to have access! This is really cool and a great opportunity for this community. I am sure I reflect everyone’s feelings in saying a big thank you to everyone that helped make this happen This is such an amazing thing for an open source project to have this kind of tool for everyone to use. Invision is a shared tool that can really help us all working on .org projects. It is a powerful prototyping system and you can learn more about it here.
To get access, first you must be a member of the design Trello board. You can join that board using this handy link. Once there, one of the board maintainers will give you access to the board. If you don’t find you are given it please ask on chat.wordpress.org, using Slack and in #design. New and existing members can then follow these steps to get access to wp.invisionapp.com:
Once in, go to the Trello section titled: “Invision access”.
Add a ‘new card’, make the title ‘Please give me access’.
Click into the new card you made, in the description add your name, wp.org username

3 min read David Bisset
Development | make.wordpress.org | Apr. 13, 2017

Matt Mullenweg: First Quarter Check On Core

Matt gives some of his thoughts, perceptions and feelings on of how things are going with core foci. Rest API admin will take some time I think.

Matt Mullenweg: First Quarter Check On Core

Development | make.wordpress.org | Apr. 13, 2017

Just wanted to give folks my perception and feelings on of how we’re doing thus far with the core foci: Writing: I’m really happy with the progress. It has had some slower weeks here and there the past few months, but by and large the technical prototypes we implemented have been successful and we’re ready to move into the next phase. We have a Chrome fix we have to get in the next minor release, and the link boundary improvements will be going into TinyMCE core and could be great for an interim +0.1 release.
Customization: Doing well. Remember: The plan is for the larger block-driven customization work to kick off in June. Prior to that, we’re focusing on widgets and other low-hanging fruit. Lack of developers slowed us down last few months, now doing better but could still use more help there. Media widgets + WYSIWYG on text widget seem simple but will have a big user impact.
REST API: There has been little to no perceivable progress on having any parts of wp-admin powered by the REST API.
Considering 4.8: The TinyMCE inline element / link boundaries, new media widgets, WYSIWYG in text widget, and perhaps something else small like the WordCamp / meetup dashboard

5 min read Ahmad Awais
Community | make.wordpress.org | Nov. 15, 2017

What’s New in Gutenberg 1.7? (15th November)

Gutenberg continues to improve one week after another. Check it out. Getting better with every new release.

What’s New in Gutenberg 1.7? (15th November)

Community | make.wordpress.org | Nov. 15, 2017

This next release includes several features and improvements on many levels. We are adding a way to switch between the header toolbar and toolbars attached to the block by opening the toggle menu at the top right and choosing the behaviour. There has been convincing arguments for both approaches so we want to make it easier to test both easily. Other notable features include the ability to transform multiple blocks of the same type into other blocks (like many images into a gallery). There are improvements to meta-boxes (dropping iframes), foundational work for nested blocks and global blocks, many design updates, and initial integration with JS hooks. Add toggle to switch between top-level toolbar and toolbars attached to each block. We have gotten great feedback on the benefits of both approaches and want to expand testing of each.
Ability to transform multiple-selected blocks at once — multiple images into a gallery, multiple paragraphs into lists.
Add @-mention autocomplete for users in a site.
Add data layer for reusable blocks and wp_blocks post type name.
Allow pasting standalone images and uploading them (also supports pasting base64 encoded images).
Allow block nesting

Development | make.wordpress.org | Dec. 6, 2016

WordPress 4.7 Field Guide for Developers

A collection of useful links to all the things shipping with WordPress 4.7. A must-read for all WordPress developers.

WordPress 4.7 Field Guide for Developers

Development | make.wordpress.org | Dec. 6, 2016

WordPress 4.7 is shaping up to be the best WordPress yet! Users will receive new and refined features that make it easier to “Make your site, YOUR site”, and developers will be able to take advantage of 173 enhancements and feature requests added. Let’s look at the many improvements coming in 4.7… RESTing, RESTing: 1, 2, 3
The foundation for RESTful APIs has been in core since 4.4, and 4.7 sees the addition of Content Endpoints after a healthy discussion. We’ve defined four success metrics as part of the merge discussion and you can help by building themes and plugins on top of the API, using the API in custom development projects, and utilizing the API for a feature project, core features, or patches. So, dive in, start playing around, and let us know what you build!
Hi everyone, it’s your friendly REST API team here with our second merge proposal for WordPress core. (WordPress 4.4 included the REST API Infrastructure, if you’d like to check out our previous merge proposal.) Even if you’re familiar with the REST API right now, we’ve made some changes to how the project is organised, so … Continue reading
It don’t mean

6 min read Ahmad Awais
Community | make.wordpress.org | May. 16, 2018

Preparing WordPress for a JavaScript Future Part #1: Build Step and Folder Reorganization

Omar from Yoast has done some really commendable work here to take the first step in making WordPress and JavaScript play well together. It needs all the help you can give. Get contributing!

Preparing WordPress for a JavaScript Future Part #1: Build Step and Folder Reorganization

Community | make.wordpress.org | May. 16, 2018

In the past couple of months, I have been working on a patch to make WordPress fit with modern modular JavaScript programming practices. We’ve figured out what the concerns are with regard to JS code organization in WordPress and how to be future compatible, so we can easily allow modern JS practices and inclusion of projects like Gutenberg in WordPress. This patch is the first big step towards an improved JavaScript development workflow for WordPress core and introduces the following major changes:
Introduces a required build step for WordPress develop. This means it will no longer be possible to run WordPress from the src directory, but I’ve taken multiple steps to make this transition acceptable and as smooth as possible, described below.
Fully backwards compatible reorganization of the JavaScript code in src. All JavaScript is placed under src/js and is organized in an improved directory structure that gives much more context and is future compatible. In production, everything is built back into its original location to ensure backwards compatibility.
Why?
Here’s an overview of the directory structure that comes with the patch and the idea behind it.
src/js