Skip to content

Commit c8e5494

Browse files
Update docs/explanation/rendering-options.md
Co-authored-by: Joe Fusco <[email protected]>
1 parent 70669b3 commit c8e5494

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/explanation/rendering-options.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Considering those limitations, it's clear that rendering raw HTML Content is not
3636

3737
### 2. Rendering Block Editor (Gutenberg) Content
3838
#### Overview
39-
WordPress Block Editor (Gutenberg) stores content as HTML with special comments and structured JSON properties in the comments representing blocks, offering more flexibility for headless implementations. However exposing them in a Headless enviroment is tricky. Thats why with the help of the [wp-graphql-content-blocks](https://github.com/wpengine/wp-graphql-content-blocks) plugin, you can query (Gutenberg) Blocks as data using graphql.
39+
WordPress Block Editor (Gutenberg) stores content as HTML with special comments and structured JSON properties in the comments representing blocks, offering more flexibility for headless implementations. However exposing them in a Headless enviroment is tricky. That's why with the help of the [wp-graphql-content-blocks](https://github.com/wpengine/wp-graphql-content-blocks) plugin, you can query (Gutenberg) Blocks as data using graphql.
4040

4141
This gives you more controls and ability to manipulate or enhance specific content elements or blocks compared to the previous approach. Here is how to do it:
4242

0 commit comments

Comments
 (0)