This Gutenberg 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/ release includes several bug fixes and focuses on improving the performance of the block 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. editor, particularly when editing large posts. It will line up with WordPress 5.0.1 and can be first tested as a plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. version 4.7.

The goal of Gutenberg is to simplify the creation of rich pages and posts in WordPress by replacing old custom HTML 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., CSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., and shortcodes with native Blocks. The Gutenberg plugin is currently the main focus for the testing group and Gutenberg is the new editing experience in WordPress.

To help test, please download gutenberg.zip from the releases page or use the button above, install/activate the plugin, and try testing any of the items listed below. You can also see other options for getting setup for testing in the handbook.

Currently, you should be testing with WordPress 5.0 stable alongside the Gutenberg 4.7 plugin. This is because 5.1-alpha trunk is currently undergoing some cleanup (normally, testing with trunk is fine).

All testing is welcome even if it’s just one or two items!

1. Create a very long post with thousands of words. (12480)
2. Open a very long post and begin typing to add new content. (12386, 12460, 12521, 12547)
3. Create a large post with many different types of blocks. (12384, 12510)
4. Add an image to the Media & Text block and try to resize the image. (12619)
5. Add an image by selecting one from the media library, click undo, and make sure the placeholder shows properly at that point. (12567)
6. Copy and paste content from one block to another. Switch to Code Editor mode. (12543)
7. Insert several images into a classic block and make sure they are inserted into the correct location where the cursor was positioned. (10509)
8. Try tabbing through blocks and check to see if it works as expected even after pressing Ctrl + backtick twice to jump to the top toolbar and back to the content area. (12390)
9. Create, delete, add, then trash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. a reusable block. After it is trashed checked to see that a “Deleted or unavailable” message appears in its place in the editor. (12345)
10. Copy content from a word processing app and confirm no spaces are collapsed unexpectedly. (12166)
11. Edit a paragraph as HTML. Remove a space and insert a line break (use ENTER). Edit visually. You should see a space where you inserted the line break. Edit the content. Edit as HTML. The line break should be replaced by a space. (12166)
12. Disable a core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. block, try pasting content that will trigger that block, expect it to. (11057)
13. Install ACF and make sure hidden meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes stay hidden. (12628)
14. Install a plugin which uses TinyMCE in a textarea in a meta box area, such as Memberlite Elements or Meta Box (and can you think of any others we can test?), then create a post using that content and make sure it saves. (12568)
15. For more, see issues in the 4.7 milestone.

If you find a new bug, please file it in gutenberg on GitHub. Thank you!

Block developers: make sure to be aware of deprecations.

Please join us in #core-test on WordPress Slack any time if you have questions about testing!

#4-7, #call-for-testing, #gutenberg