WordPress 5.0 Bebo

On December 6, 2018, the long-awaited WordPress 5.0 with the new editor Gutenberg was released.

Finally – WordPress 5.0 Bebo has been released from wordpress.org

On December 6, 2018, the long-awaited WordPress 5.0 with the new editor Gutenberg was released.

WordPres 5.0 is named after the Cuban jazz musician Bebo Valdés.

Gutenberg has been subject to a lot of anxiety and criticism from several origins.

The new editor suffered both delays and problems.

But Matt Mullenweg ‘put his foot down’ last month and decided a release date today.

WordPress 5.0 Gutenberg Blocks editor - a-support.dk
WordPress 5.0 Gutenberg Blocks editor. Ill.: wordpress.org

Gutenberg Blocks editor

Gutenberg introduces blocks.

Previously, your content resided inside one continous HTML file.

Shortcodes, custom post types, embeds, widgets etc. had to be added into that file separately.

All with their quirky interfaces and weird behavior.

Now, you can build your content much like  a LEGO set: blocks that you pull all from one box, with a standardized and straightforward set of instructions.

The blocks concept, lets you determine what every part of your content is.

And you can define their specifications per block.

For instance, you can turn a single line of text into a quote by changing its block type.

With that change, it gets a new set of options that you can specify.

You can change the type of quote, its placement, text decoration and more.

This goes for all blocks:

  • Paragraphs
  • Lists
  • Quotes
  • Headings
  • Code
  • Images
  • Galleries
  • Shortcodes
  • Columns
  • Buttons
  • Widgets

According to wordpress.org, Gutenberg is just the first step on the way to a completely new way of editing and creating content on any WordPress website.

Possibly Gutenberg may be more than enough to get used to for a lot of users.

The new editor’s blocks consist of a variety of specific widgets / editors.

Blocks can be inserted and moved around in a post and on a page in WordPress.

Blocks are specific and discrete content containers.

In the ‘old’ editor all content on any page or post consisted of one sequence of codes.

With blocks, all content is split up and can be changed and moved individually.

You can effortlessly insert an image block prior to a text block and then move the image down below the text block, etc.

In the classic editor, it could be quite challenging to left- or right-align an image with
a paragraph’s  text wrapped around it.

So far, the new Blocks approach solves many of the challenges the previous editor offered.

Instead of the classic editor’s blank canvas, in Gutenberg content is broken up into a series of individual blocks that are independent from the content as a whole.

You can now edit the HTML of just one block without affecting other blocks.

Still unresolved issues

Gutenberg is not yet free of various bugs and errors.

The image in a Cover-block creates a horizontal scrollbar in full width display.

 A few days after the initial release of WordPress 5.0 wordpress.org released version 5.01 containing some 15 bug fixes.

WordPress 5.0 Twenty Nineteen theme - a-support.dk
WordPress 5.0 Twenty Nineteen theme. Ill.: wordpress.org

Twenty Nineteen Theme – Built for Gutenberg

The default theme Twenty Nineteen in WordPress 5.0 was made with Gutenberg in mind.

It is anice and well-functioning theme.

The theme uses system fonts, which makes load times better.

Twenty Nineteen is fully compatible with the Gutenberg editor.

It includes front-end and back-end styles to provide a true WYSIWYG (What You See Is What You Get) experience.

It also supports the Wide and Full image alignment options. 

What about existing content?

Content not created in the new editor is placed in a Classic block.

This block mimics the old editor and provides users a choice to migrate it into blocks.

But migrating content into blocks is not required and most content will not be affected by updating to WordPress 5.0.

What about the ‘old’ editor?

If you for any reasondon’t want to work with Gutenberg, you can continue with the ‘old’ (classic) editor.

It just requires that you install the classic editor as a plugin available in the WordPress plugins repository.

This way you can continue using the classic editor  and continue using any plugins that expand the classic editor.

Leave a Reply