Learning Gutenberg: What is Gutenberg, Anyway?

Gutenberg is an update of the WordPress WYSIWYG editorial manager.

WordPress has generally been that solitary WYSIWYG field, (the mass of substance) that spares the whole substance of the post to the post_content section in the wp_posts database table. Gutenberg doesn’t change this: it spares all the post substance to the post_content table to be recovere by calling the_content() in our PHP layouts.

No doubt about it Gutenberg is only an update. it’s a tragedy to call Gutenberg only an overhaul of the manager! It is far beyond that!

Gutenberg presents a totally better approach for considering content in WordPress. It not just gives engineers a local method to deal with substance in lumps (we'll really be alluding to them as squares, which is their official name), it empowers end-clients to make rich, powerful page formats with WordPress out of the container. Without Gutenberg, this would almost certainly require a store of outsider modules (read: shortcode regurgitation and server strain) as is at present the case with what will be known as the WordPress "Great" editorial manager.

For the motivations behind this article and our learning, know this: Gutenberg does not change how WordPress capacities at its exceptionally center. It is 99% a change to the editorial manager's UI. Hitting "Distribute" still spares substance to post_content—there's only much greater chance to create the client experience of composing and altering content.

Beware!

While the Gutenberg project is far enough along that there will not be any major infrastructural changes, we must remember that Gutenberg is brand new software in active development and anything could happen. Why not be on the front lines? This is exciting stuff.

The WordPress community has already begun to take up the task of creating tools, tutorials, case studies, courses, and community-contributed resources.

That being said, you may search a question that hasn’t been asked before. At some point, you will probably find yourself reading the Gutenberg source code for documentation, and you may find the existing documentation to be out of date. You may test out an example from a two-week-old tutorial only to find it uses a deprecated API method.

If you do come across something you feel is not as it should be, research and report the issue on GitHub, ask about it in the #core-editor channel of the WordPress Slack, or alert the author of the aforementioned out-of-date blog post. And if it’s documentation that’s a problem, you can always fix it yourself!