diff --git a/docs/explanations/architecture/full-site-editing-templates.md b/docs/explanations/architecture/full-site-editing-templates.md
index 10f1ac3d537ad8..dac115ef92ce8a 100644
--- a/docs/explanations/architecture/full-site-editing-templates.md
+++ b/docs/explanations/architecture/full-site-editing-templates.md
@@ -2,13 +2,15 @@
## Template and template part flows
-> This is the documentation for the current implementation of the block-based templates and template parts themes. This is part of the Full Site Editing project. These features are still experimental in the plugin. “Experimental” means this is just an early implementation that is subject to potential drastic and breaking changes in iterations based on feedback from users, contributors, and theme authors.
+
+This is the documentation for the current implementation of the block templates and template parts themes. This is part of the Full Site Editing project. These features are still experimental in the plugin. “Experimental” means this is just an early implementation that is subject to potential drastic and breaking changes in iterations based on feedback from users, contributors, and theme authors.
+
-This document will explain the internals of how templates and templates parts are rendered in the frontend and edited in the backend. For an introduction about block-based themes and Full site editing templates, refer to the [block-based themes documentation](/docs/how-to-guides/themes/block-based-themes.md).
+This document will explain the internals of how templates and templates parts are rendered in the frontend and edited in the backend. For an introduction about block themes and Full site editing templates, refer to the [block theme documentation](/docs/how-to-guides/themes/block-theme-overview.md).
## Storage
-Just like the regular templates, the block-based templates live initially as files in the theme folder but the main difference is that the user can edit these templates in the UI in the Site Editor.
+Just like the regular templates, the block templates live initially as files in the theme folder but the main difference is that the user can edit these templates in the UI in the Site Editor.
When a user edits a template (or template-part), the initial theme template file is kept as is but a forked version of the template is saved to the `wp_template` custom post type (or `wp_template_part` for template parts).
@@ -30,11 +32,11 @@ The synchronization is important for two different flows:
- When editing the template and template parts, the site editor frontend fetches the edited and available templates through the REST API. This means that for all `GET` API requests performed to the `wp-templates` and `wp-template-parts` endpoint synchronization is required.
- When rendering a template (sometimes referred to as "resolving a template"): this is the algorithm that WordPress follows to traverse the template hierarchy and find the right template to render for the current page being loaded.
-- When exporting a block-based theme, we need to export all its templates back as files. The synchronization is required to simplify the operation and only export the CPT templates.
+- When exporting a block theme, we need to export all its templates back as files. The synchronization is required to simplify the operation and only export the CPT templates.
## Switching themes
-Since block-based themes make use of templates that can refer to each other and that can be saved to a custom post type, it becomes possible to mix templates and template parts from different themes. For example:
+Since block themes make use of templates that can refer to each other and that can be saved to a custom post type, it becomes possible to mix templates and template parts from different themes. For example:
- A user might like the "header" template part of theme A and would like to use it in theme B.
- A user might like the "contact" template from theme A and would like to use it in theme B.
diff --git a/docs/getting-started/faq.md b/docs/getting-started/faq.md
index 5a685ce6053b7a..87ac239e031906 100644
--- a/docs/getting-started/faq.md
+++ b/docs/getting-started/faq.md
@@ -320,7 +320,7 @@ Blocks are able to provide base structural CSS styles, and themes can add styles
Other features, like the new _wide_ and _full-wide_ alignment options, are simply CSS classes applied to blocks that offer this alignment. We are looking at how a theme can opt in to this feature, for example using `add_theme_support`.
-This is currently a work in progress and we recommend reviewing the [block based theme documentation](/docs/how-to-guides/block-based-theme/README.md) to learn more.
+This is currently a work in progress and we recommend reviewing the [block based theme documentation](/docs/how-to-guides/themes/block-theme-overview.md) to learn more.
## What are block variations? Are they the same as block styles?
diff --git a/docs/getting-started/full-site-editing.md b/docs/getting-started/full-site-editing.md
index 8cde8e3fabcc14..62bfb4ac96bbca 100644
--- a/docs/getting-started/full-site-editing.md
+++ b/docs/getting-started/full-site-editing.md
@@ -1,10 +1,10 @@
# Full Site Editing
-At the highest level, the vision of Full Site Editing is to provide a collection of features that bring the familiar experience and extendability of blocks to all parts of your site rather than just post and pages. You can think of Full Site Editing as the umbrella project name for various sub-projects within Gutenberg that make this vision possible. Projects under Full Site Editing (FSE) include the Site Editor, Global Styles, numerous Site/Post/Page specific blocks, Query block, Navigation block, Templates, and block themes.
+At the highest level, the vision of Full Site Editing is to provide a collection of features that bring the familiar experience and extendability of blocks to all parts of your site rather than just post and pages. You can think of Full Site Editing as the umbrella project name for various sub-projects within Gutenberg that make this vision possible. Projects under Full Site Editing (FSE) include the Site Editor, Global Styles, numerous Site/Post/Page specific blocks, Query block, Navigation block, Templates, and block themes.
-There are other projects, like the Navigation Editor and Widget Editor, that are meant to specifically help classic themes begin adapting more to the block framework and to act as a stepping stone of sorts to Full Site Editing. These are separate projects from Full Site Editing though but are worth being aware of as they ultimately help the cause of getting more people adjusted to using blocks in more places.
-
-**Jump in:**
+There are other projects, like the Navigation Editor and Widget Editor, that are meant to specifically help classic themes begin adapting more to the block framework and to act as a stepping stone of sorts to Full Site Editing. These are separate projects from Full Site Editing though but are worth being aware of as they ultimately help the cause of getting more people adjusted to using blocks in more places.
+
+**Jump in:**
The best way to learn something is start playing with it. So jump in by installing the Gutenberg plugin from the plugins directory and activating a block theme on a test site. We recommend the [TT1 Blocks theme](https://wordpress.org/themes/tt1-blocks/), it is listed in the theme diretory and our development reference theme. You can find other themes in the directory using the [full-site-editing feature tag](https://wordpress.org/themes/tags/full-site-editing/).
@@ -12,19 +12,19 @@ The best way to learn something is start playing with it. So jump in by installi
An ongoing [FSE Outreach program](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/) is in place with calls for testing and is a great way to get involved and learn about the new features.
-- Join in on [WordPress Slack](https://make.wordpress.org/chat/) at [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
+- Join in on [WordPress Slack](https://make.wordpress.org/chat/) at [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
- Participate in the [Calls for Testing](https://make.wordpress.org/test/tag/fse-testing-call/) by testing and giving feedback.
- See detailed [How to Test FSE instructions](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/how-to-test-fse/) to get setup to test FSE features.
## Block Themes
-If you are using the Gutenberg plugin you can run, test, and develop block themes. Block themes are themes built using templates composed using blocks. See [block theme overview](/docs/how-to-guides/themes/block-based-themes.md) for additional details.
+If you are using the Gutenberg plugin you can run, test, and develop block themes. Block themes are themes built using templates composed using blocks. See [block theme overview](/docs/how-to-guides/themes/block-theme-overview.md) for additional details.
-- See the [Create a Block Theme](/docs/how-to-guides/block-theme/README.md) tutorial for a walk-through of the pieces of a block theme.
+- See the [Create a Block Theme](/docs/how-to-guides/themes/create-block-theme.md) tutorial for a walk-through of the pieces of a block theme.
- For examples, see the [WordPress/theme-experiments](https://github.com/WordPress/theme-experiments/) repository with several block themes there including the source for the above mentioned TT1 Blocks.
-- Use the `empty-theme.php` script from theme-experiments repo to generate a start block theme, it will prompt you with a few questions and create a theme.
+- Use the `empty-theme.php` script from theme-experiments repo to generate a starter block theme, it will prompt you with a few questions and create a theme.
```
❯ git clone https://github.com/WordPress/theme-experiments
@@ -43,10 +43,10 @@ You can then copy the generated directory to your `wp-content/themes` directory
### Template and Template Parts
-See the [architecture document on templates](docs/explanations/architecture/full-site-editing-templates.md) for an explanation on the internals of how templates and templates parts are rendered in the frontend and edited in the backend.
+See the [architecture document on templates](/docs/explanations/architecture/full-site-editing-templates.md) for an explanation on the internals of how templates and templates parts are rendered in the frontend and edited in the backend.
### theme.json
Instead of the proliferation of theme support flags or alternative methods, a new `theme.json` file is being used to define theme settings. **NOTE:** This feature is still experimental and changing, so the interim file name is `experimental-theme.json`
-See [documentation for theme.json](https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-json/).
+See [documentation for theme.json](/docs/how-to-guides/themes/theme-json.md).
diff --git a/docs/getting-started/glossary.md b/docs/getting-started/glossary.md
index 02327c0eb36e01..6518868b098564 100644
--- a/docs/getting-started/glossary.md
+++ b/docs/getting-started/glossary.md
@@ -11,7 +11,7 @@
The abstract term used to describe units of markup that, composed together, form the content or layout of a webpage. The idea combines concepts of what in WordPress today we achieve with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.
Block Based Theme
-A theme built in block forward way that allows Full Site Editing to work. The core of a block-based theme are its block templates and block template parts. To date, block-based theme templates have been HTML files of block markup that map to templates from the standard WordPress template hierarchy.
+A theme built in block forward way that allows Full Site Editing to work. The core of a block theme are its block templates and block template parts. To date, block theme templates have been HTML files of block markup that map to templates from the standard WordPress template hierarchy.
Block categories
These are not a WordPress taxonomy, but instead used internally to sort blocks in the Block Library.
diff --git a/docs/how-to-guides/themes/README.md b/docs/how-to-guides/themes/README.md
index 26609e7cf3f980..b92293a5f00a17 100644
--- a/docs/how-to-guides/themes/README.md
+++ b/docs/how-to-guides/themes/README.md
@@ -1,5 +1,10 @@
-# Theming for the Block Editor
+# Themes
-The new editor provides a number of options for theme designers and developers, including theme-defined color settings, font size control, and much more.
+The block editor provides a number of options for theme designers and developers, including theme-defined color settings, font size control, and much more.
-In this section, you'll learn about the ways that themes can customize the editor.
+**Contents**
+
+- [Block Theme Overview](/docs/how-to-guides/themes/block-theme-overview.md)
+- [Create a Block Theme](/docs/how-to-guides/themes/create-block-theme.md)
+- [Global Settings (theme.json)](/docs/how-to-guides/themes/theme-json.md)
+- [Theme Support](/docs/how-to-guides/themes/theme-support.md)
diff --git a/docs/how-to-guides/themes/block-based-themes.md b/docs/how-to-guides/themes/block-theme-overview.md
similarity index 76%
rename from docs/how-to-guides/themes/block-based-themes.md
rename to docs/how-to-guides/themes/block-theme-overview.md
index 6eb8608b0e02fe..9098cb76930eaa 100644
--- a/docs/how-to-guides/themes/block-based-themes.md
+++ b/docs/how-to-guides/themes/block-theme-overview.md
@@ -1,18 +1,18 @@
-# Block-based Themes (Experimental)
+# Block Theme
-> This is the documentation for the current implementation of block-based themes, also known as Full Site Editing or Block Content Areas. These features are still experimental in the plugin. “Experimental” means this is just an early implementation that is subject to potential drastic and breaking changes in iterations based on feedback from users, contributors and theme authors.
+
+These features are still experimental in the plugin. “Experimental” means this is just an early implementation that is subject to potential drastic and breaking changes in iterations based on feedback from users, contributors and theme authors.
-> Documentation has been shared early to surface what’s being worked on and invite feedback from those experimenting with the APIs. You can provide feedback in the weekly #core-editor chats where the latest progress of this effort will be shared and discussed, or async via Github issues.
-
-**Note:** To use these features, activate a theme that includes a `block-templates/index.html` file. This will signal to the block editor that the theme should use full-site editing features.
+Documentation is shared early to surface what’s being worked on and invite feedback from those experimenting with the APIs. You can provide feedback in the weekly #core-editor chats, or #fse-outreach-experiment channels, or async via Github issues.
+
-## What is a block-based theme?
+## What is a block theme?
-A block-based theme is a WordPress theme with templates entirely composed of blocks so that in addition to the post content of the different post types (pages, posts, ...), the block editor can also be used to edit all areas of the site: headers, footers, sidebars, etc.
+A block theme is a WordPress theme with templates entirely composed of blocks so that in addition to the post content of the different post types (pages, posts, ...), the block editor can also be used to edit all areas of the site: headers, footers, sidebars, etc.
-## What is the structure of a block-based theme?
+## What is the structure of a block theme?
-A very simple block-based theme is structured like so:
+A very simple block theme is structured like so:
```
theme
@@ -96,7 +96,7 @@ Note that it won't take precedence over any of your theme's templates with highe
## Theme Blocks
-Some blocks have been made specifically for block-based themes. For example, you'll most likely use the **Site Title** block in your site's header while your **single** block template will most likely include a **Post Title** and a **Post Content** block.
+Some blocks have been made specifically for block themes. For example, you'll most likely use the **Site Title** block in your site's header while your **single** block template will most likely include a **Post Title** and a **Post Content** block.
As we're still early in the process, the number of blocks specifically dedicated to these block templates is relatively small but more will be added as we move forward with the project. As of Gutenberg 8.5, the following blocks are currently available:
@@ -137,4 +137,4 @@ remove_theme_support( 'block-templates' );
## Resources
- [Full Site Editing](https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing) label.
-- [Theme Experiments](https://github.com/WordPress/theme-experiments) repository, full of block-based theme examples created by the WordPress community.
+- [Theme Experiments](https://github.com/WordPress/theme-experiments) repository, full of block theme examples created by the WordPress community.
diff --git a/docs/how-to-guides/block-theme/README.md b/docs/how-to-guides/themes/create-block-theme.md
similarity index 90%
rename from docs/how-to-guides/block-theme/README.md
rename to docs/how-to-guides/themes/create-block-theme.md
index 92d89713ad653a..86797bc2424e0a 100644
--- a/docs/how-to-guides/block-theme/README.md
+++ b/docs/how-to-guides/themes/create-block-theme.md
@@ -10,10 +10,10 @@ This tutorial is up to date as of Gutenberg version 9.1.
## Table of Contents
-1. [What is needed to create a block-theme?](/docs/how-to-guides/block-theme/README.md#what-is-needed-to-create-a-block-theme)
-2. [Creating the theme](/docs/how-to-guides/block-theme/README.md#creating-the-theme)
-3. [Creating the templates and template parts](/docs/how-to-guides/block-theme/README.md#creating-the-templates-and-template-parts)
-4. [experimental-theme.json - Global styles](/docs/how-to-guides/block-theme/README.md#experimental-theme-json-global-styles)
+1. [What is needed to create a block-theme?](#what-is-needed-to-create-a-block-theme)
+2. [Creating the theme](#creating-the-theme)
+3. [Creating the templates and template parts](#creating-the-templates-and-template-parts)
+4. [experimental-theme.json - Global styles](#experimental-theme-json-global-styles)
## What is needed to create a block theme?
@@ -21,7 +21,7 @@ To use a block theme you need to use the Gutenberg plugin.
A block theme is built using HTML templates and template parts. Templates are the main files used in the [template hierarchy](https://developer.wordpress.org/themes/basics/template-hierarchy/), for example index, single or archive. Templates can optionally include structural template parts, for example a header, footer or sidebar.
-Each template or template part contains the [block grammar](https://developer.wordpress.org/block-editor/principles/key-concepts/#blocks), the HTML, for the selected blocks. The block HTML is generated in and exported from the **site editor**. It can also be added to the theme's HTML files manually.
+Each template or template part contains the [block grammar](/docs/explanations/architecture/key-concepts/), the HTML, for the selected blocks. The block HTML is generated in and exported from the **site editor**. It can also be added to the theme's HTML files manually.
### Required files and file structure
@@ -85,7 +85,7 @@ _You no longer need to add theme support for the title tag. It is already enable
https://developer.wordpress.org/themes/basics/theme-functions/#what-is-functions-php
-https://developer.wordpress.org/block-editor/developers/themes/theme-support/
+https://developer.wordpress.org/block-editor/how-to-guides/themes/theme-support/
```php
**These features are still experimental**. “Experimental” means this is an early implementation subject to drastic and breaking changes.
->
-> Documentation has been shared early to surface what’s being worked on and invite feedback from those experimenting with the APIs. Please, be welcomed to share yours in the weekly #core-editor chats as well as async via the Github issues and Pull Requests.
+
+These features are still experimental. “Experimental” means this is an early implementation subject to drastic and breaking changes.
+
+Documentation has been shared early to surface what’s being worked on and invite feedback from those experimenting with the APIs. Please share your feedback in the weekly #core-editor or #fse-outreach-experiment channels in Slack, or async in GitHub issues.
+
This is documentation for the current direction and work in progress about how themes can hook into the various sub-systems that the Block Editor provides.
@@ -58,7 +60,7 @@ There are some areas of styling that would benefit from having shared values tha
To address this need, we've started to experiment with CSS Custom Properties, aka CSS Variables, in some places:
-- **Presets**: [color palettes](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-color-palettes), [font sizes](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-font-sizes), or [gradients](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-gradient-presets) declared by the theme are converted to CSS Custom Properties and enqueued both the front-end and the editors.
+- **Presets**: [color palettes](/docs/how-to-guides/themes/theme-support.md#block-color-palettes), [font sizes](/docs/how-to-guides/themes/theme-support.md#block-font-sizes), or [gradients](/docs/how-to-guides/themes/theme-support.md#block-gradient-presets) declared by the theme are converted to CSS Custom Properties and enqueued both the front-end and the editors.
{% codetabs %}
{% Input %}
diff --git a/docs/how-to-guides/themes/theme-support.md b/docs/how-to-guides/themes/theme-support.md
index 404647d6004ae5..9f8f9baa9f3684 100644
--- a/docs/how-to-guides/themes/theme-support.md
+++ b/docs/how-to-guides/themes/theme-support.md
@@ -397,7 +397,7 @@ Using the Gutenberg plugin (version 8.3 or later), link color control is availab
add_theme_support('experimental-link-color');
```
-If a theme opts in, it should [define default link colors](https://developer.wordpress.org/block-editor/developers/themes/theme-json/#color-properties) in `experimental-theme.json` (or in its theme styles if no `experimental-theme.json` is present). For example:
+If a theme opts in, it should [define default link colors](/docs/how-to-guides/themes/theme-json.md#color-properties) in `experimental-theme.json` (or in its theme styles if no `experimental-theme.json` is present). For example:
```css
{
diff --git a/docs/manifest.json b/docs/manifest.json
index e1269a28328eee..de2f1851118fd7 100644
--- a/docs/manifest.json
+++ b/docs/manifest.json
@@ -294,33 +294,39 @@
"parent": "block-tutorial"
},
{
- "title": "Feature Flags",
- "slug": "feature-flags",
- "markdown_source": "../docs/how-to-guides/feature-flags.md",
- "parent": "how-to-guides"
- },
- {
- "title": "Theming for the Block Editor",
+ "title": "Themes",
"slug": "themes",
"markdown_source": "../docs/how-to-guides/themes/README.md",
"parent": "how-to-guides"
},
{
- "title": "Theme Support",
- "slug": "theme-support",
- "markdown_source": "../docs/how-to-guides/themes/theme-support.md",
+ "title": "Block Theme",
+ "slug": "block-theme-overview",
+ "markdown_source": "../docs/how-to-guides/themes/block-theme-overview.md",
"parent": "themes"
},
{
- "title": "Themes & Block Editor: experimental theme.json",
+ "title": "Create a block theme",
+ "slug": "create-block-theme",
+ "markdown_source": "../docs/how-to-guides/themes/create-block-theme.md",
+ "parent": "themes"
+ },
+ {
+ "title": "Global Settings (theme.json)",
"slug": "theme-json",
"markdown_source": "../docs/how-to-guides/themes/theme-json.md",
"parent": "themes"
},
{
- "title": "Create a block theme",
- "slug": "block-theme",
- "markdown_source": "../docs/how-to-guides/block-theme/README.md",
+ "title": "Theme Support",
+ "slug": "theme-support",
+ "markdown_source": "../docs/how-to-guides/themes/theme-support.md",
+ "parent": "themes"
+ },
+ {
+ "title": "Feature Flags",
+ "slug": "feature-flags",
+ "markdown_source": "../docs/how-to-guides/feature-flags.md",
"parent": "how-to-guides"
},
{
diff --git a/docs/reference-guides/block-api/block-supports.md b/docs/reference-guides/block-api/block-supports.md
index 97ee464b7fa1d3..ea746a856c1b8e 100644
--- a/docs/reference-guides/block-api/block-supports.md
+++ b/docs/reference-guides/block-api/block-supports.md
@@ -143,7 +143,7 @@ When the block declares support for `color.background`, the attributes definitio
When a user chooses from the list of preset background colors, the preset slug is stored in the `backgroundColor` attribute.
- Background color presets are sourced from the `editor-color-palette` [theme support](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-color-palettes).
+ Background color presets are sourced from the `editor-color-palette` [theme support](/docs/how-to-guides/themes/theme-support.md#block-color-palettes).
The block can apply a default preset background color by specifying its own attribute with a default e.g.:
@@ -157,7 +157,7 @@ When the block declares support for `color.background`, the attributes definitio
```
- `style`: attribute of `object` type with no default assigned.
-
+
When a custom background color is selected (i.e. using the custom color picker), the custom color value is stored in the `style.color.background` attribute.
The block can apply a default custom background color by specifying its own attribute with a default e.g.:
@@ -194,7 +194,7 @@ supports: {
}
```
-Duotone presets are sourced from `color.duotone` in [theme.json](https://developer.wordpress.org/block-editor/developers/themes/theme-json/).
+Duotone presets are sourced from `color.duotone` in [theme.json](/docs/how-to-guides/themes/theme-json.md).
When the block declares support for `color.duotone`, the attributes definition is extended to include the attribute `style`:
@@ -234,7 +234,7 @@ supports: {
}
```
-Gradient presets are sourced from `editor-gradient-presets` [theme support](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-gradient-presets).
+Gradient presets are sourced from `editor-gradient-presets` [theme support](/docs/how-to-guides/themes/theme-support.md#block-gradient-presets).
When the block declares support for `color.gradient`, the attributes definition is extended to include two new attributes: `gradient` and `style`:
@@ -244,7 +244,7 @@ When the block declares support for `color.gradient`, the attributes definition
When a user chooses from the list of preset gradients, the preset slug is stored in the `gradient` attribute.
The block can apply a default preset gradient by specifying its own attribute with a default e.g.:
-
+
```js
attributes: {
gradient: {
@@ -255,9 +255,9 @@ When the block declares support for `color.gradient`, the attributes definition
```
- `style`: attribute of `object` type with no default assigned.
-
+
When a custom gradient is selected (i.e. using the custom gradient picker), the custom gradient value is stored in the `style.color.gradient` attribute.
-
+
The block can apply a default custom gradient by specifying its own attribute with a default e.g.:
```js
@@ -296,15 +296,15 @@ supports: {
}
```
-Text color presets are sourced from the `editor-color-palette` [theme support](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-color-palettes).
-
+Text color presets are sourced from the `editor-color-palette` [theme support](/docs/how-to-guides/themes/theme-support.md#block-color-palettes).
+
When the block declares support for `color.text`, the attributes definition is extended to include two new attributes: `textColor` and `style`:
- `textColor`: attribute of `string` type with no default assigned.
When a user chooses from the list of preset text colors, the preset slug is stored in the `textColor` attribute.
-
+
The block can apply a default preset text color by specifying its own attribute with a default e.g.:
```js
@@ -317,9 +317,9 @@ When the block declares support for `color.text`, the attributes definition is e
```
- `style`: attribute of `object` type with no default assigned.
-
+
When a custom text color is selected (i.e. using the custom color picker), the custom color value is stored in the `style.color.text` attribute.
-
+
The block can apply a default custom text color by specifying its own attribute with a default e.g.:
```js
@@ -370,7 +370,7 @@ supports: {
This value signals that a block supports the font-size CSS style property. When it does, the block editor will show an UI control for the user to set its value.
-The values shown in this control are the ones declared by the theme via the `editor-font-sizes` [theme support](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#block-font-sizes), or the default ones if none is provided.
+The values shown in this control are the ones declared by the theme via the `editor-font-sizes` [theme support](/docs/how-to-guides/themes/theme-support.md#block-font-sizes), or the default ones if none is provided.
```js
supports: {
@@ -499,7 +499,7 @@ supports: {
- Subproperties:
- `padding`: type `boolean`, default value `false`
-This value signals that a block supports some of the CSS style properties related to spacing. When it does, the block editor will show UI controls for the user to set their values, if [the theme declares support](/docs/how-to-guides/themes/theme-support.md##cover-block-padding).
+This value signals that a block supports some of the CSS style properties related to spacing. When it does, the block editor will show UI controls for the user to set their values, if [the theme declares support](/docs/how-to-guides/themes/theme-support.md#cover-block-padding).
```js
supports: {
diff --git a/docs/toc.json b/docs/toc.json
index d49e7f6942eda9..d9f66b3d635550 100644
--- a/docs/toc.json
+++ b/docs/toc.json
@@ -129,14 +129,15 @@
}
]
},
- { "docs/how-to-guides/feature-flags.md": [] },
{
"docs/how-to-guides/themes/README.md": [
- { "docs/how-to-guides/themes/theme-support.md": [] },
- { "docs/how-to-guides/themes/theme-json.md": [] }
+ { "docs/how-to-guides/themes/block-theme-overview.md": [] },
+ { "docs/how-to-guides/themes/create-block-theme.md": [] },
+ { "docs/how-to-guides/themes/theme-json.md": [] },
+ { "docs/how-to-guides/themes/theme-support.md": [] }
]
},
- { "docs/how-to-guides/block-theme/README.md": [] },
+ { "docs/how-to-guides/feature-flags.md": [] },
{
"docs/how-to-guides/backward-compatibility/README.md": [
{
diff --git a/packages/block-editor/src/components/line-height-control/README.md b/packages/block-editor/src/components/line-height-control/README.md
index ca61544e9c541d..806d181e180b7a 100644
--- a/packages/block-editor/src/components/line-height-control/README.md
+++ b/packages/block-editor/src/components/line-height-control/README.md
@@ -4,7 +4,7 @@ The `LineHeightControl` component adds a lineHeight attribute to the core Paragr
-_Note:_ It is worth noting that the line height setting option is an opt-in feature. [Themes need to declare support for it](https://developer.wordpress.org/block-editor/developers/themes/theme-support/#supporting-custom-line-heights) before it'll be available.
+_Note:_ It is worth noting that the line height setting option is an opt-in feature. [Themes need to declare support for it](/docs/how-to-guides/themes/theme-support.md#supporting-custom-line-heights) before it'll be available.
## Table of contents