Skip to content

Commit f62f336

Browse files
mkazntwb
authored andcommitted
Docs: Taking a stab at updating FAQ (#12486)
## Description The FAQ appears to be originally written in 2017 when the project was a bit younger. I've taken a stab at updating with more current information and what we now know. I also included a link to Matt's own FAQ around Gutenberg and WordPress 5.0, which likely has more recent information and questions. Fixes #8535 ## Types of changes Documentation update.
1 parent 5565c56 commit f62f336

File tree

1 file changed

+11
-11
lines changed
  • docs/designers-developers

1 file changed

+11
-11
lines changed

docs/designers-developers/faq.md

+11-11
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Frequently Asked Questions
22

3+
This initial set of questions were created when the Gutenberg project was relatively new, for a more recent set of questions, please see Matt's November 2018 post [WordPress 5.0: A Gutenberg FAQ](https://ma.tt/2018/11/a-gutenberg-faq/).
4+
35
## What is Gutenberg?
46

57
“Gutenberg” is the name of the project to create a new editor experience for WordPress. The goal is to create a new post and page editing experience that makes it easy for anyone to create rich post layouts. This was the kickoff goal:
@@ -12,16 +14,14 @@ Key takeaways include the following points:
1214
- By embracing blocks as an interaction paradigm, we can unify multiple different interfaces into one. Instead of learning how to write shortcodes and custom HTML, or pasting URLs to embed media, there's a common, reliable flow for inserting any kind of content.
1315
- “Mystery meat” refers to hidden features in software, features that you have to discover. WordPress already supports a large number of blocks and 30+ embeds, so let's surface them.
1416

15-
Gutenberg is being developed on [GitHub](https://github.com/WordPress/gutenberg) under the WordPress organization, and you can try [a beta version today—it's available in the plugin repository](https://wordpress.org/plugins/gutenberg/). It's important to keep in mind that Gutenberg is not yet fully functional, feature complete, or production ready. But we'd love your help to make that a reality.
17+
Gutenberg is being developed on [GitHub](https://github.com/WordPress/gutenberg) under the WordPress organization, and you can use it today[available in the plugin repository](https://wordpress.org/plugins/gutenberg/).
1618

1719
## When will Gutenberg be merged into WordPress?
1820

19-
We are hoping that Gutenberg will be sufficiently polished, tested, iterated, and proven enough to be [merged into WordPress 5.0](https://ma.tt/2017/06/4-8-and-whats-coming/), with an estimated release date of 2018.
21+
Gutenberg will be merged into WordPress 5.0, and will be released at the end of 2018, or early 2019. Please follow [WordPress.org News](https://wordpress.org/news/) for the latest information.
2022

2123
The editor focus started in early 2017 with the first three months spent designing, planning, prototyping, and testing prototypes, to help us inform how to approach this project. The actual plugin, which you can install from the repository, was launched during WordCamp Europe in June.
2224

23-
There is still plenty of work to do, but we are moving fast. New updates tend to be released on a weekly basis. Please help us by giving feedback, surfacing issues, testing, or even contributing, so we can be ready in time for WordPress 5.0.
24-
2525
## What are “blocks” and why are we using them?
2626

2727
The current WordPress editor is an open text window—it’s always been a wonderful blank canvas for writing, but when it comes to building posts and pages with images, multimedia, embedded content from social media, polls, and other elements, it required a mix of different approaches that were not always intuitive:
@@ -273,9 +273,7 @@ Indeed. There are multiple ways in which custom post types can leverage Gutenber
273273

274274
## Will there be columns?
275275

276-
Our primary goal is on a solid block foundation before exploring column support.
277-
278-
*See:* [Issue #219](https://github.com/WordPress/gutenberg/issues/219)
276+
Yes, a columns block is available in Gutenberg.
279277

280278
## Will there be nested blocks?
281279

@@ -285,7 +283,7 @@ See also [Issue #428](https://github.com/WordPress/gutenberg/issues/428)
285283

286284
## Will drag and drop be used for rearranging blocks?
287285

288-
A key value for Gutenberg has been to see drag and drop as an _additive enhancement_. When explicit actions (_click_ or _tab_ + _space_) exist can we add drag and drop as an enhancement on top of it. So yes, we expect drag and drop to be part of Gutenberg, even if it isn't today.
286+
Yes, you can drag and drop blocks to rearrange their order.
289287

290288
## Can themes _style_ blocks?
291289

@@ -322,9 +320,10 @@ We realize it's a big change. We also think there will be many new opportunities
322320

323321
## Will I be able to opt out of Gutenberg for my site?
324322

325-
We are looking at ways to make Gutenberg configurable for many use cases, including disabling different aspects (like blocks, panels, etc.).
323+
There is a “Classic” block, which is virtually the same as the current editor, except in block form.
324+
325+
There is also the [Classic Editor Plugin](https://wordpress.org/plugins/classic-editor/) which restores the previous editor, see the plugin for more information. The WordPress Core team has committed to supporting the Classic Editor Plugin [until December 2021](https://make.wordpress.org/core/2018/11/07/classic-editor-plugin-support-window/).
326326

327-
There is also be a “Classic” block, which is virtually the same as the current editor, except in block form. There’s also likely to be a very popular plugin in the repository to replace Gutenberg with the classic editor.
328327

329328
## How will custom TinyMCE buttons work in Gutenberg?
330329

@@ -366,7 +365,8 @@ var blocks = wp.blocks.parse( postContent );
366365
In PHP:
367366

368367
```php
369-
$blocks = gutenberg_parse_blocks( $post_content );
368+
$blocks = gutenberg_parse_blocks( $post_content ); // plugin
369+
$blocks = parse_blocks( $post_content ); // WordPress 5.0
370370
```
371371

372372
## Why should I start using this once released?

0 commit comments

Comments
 (0)