Skip to content

Consider only Updating Documentation on Release #6514

@salcode

Description

@salcode

Currently, the Gutenberg Documentation Website is updated from master every 15 minutes. source

While I understand the motivation in keeping the documentation as up-to-date as possible, it can be confusing when the behavior of the latest release varies from master.

My Experience

Working with the latest release v2.7.0 and following the documentation on Introducing Attributes and Editable Fields - Attributes, I was attempting to use RichText.Content. Unfortunately, RichText.Content was introduced since the latest release and only exists in master.

Suggestion

Clearly, I'm biased based on my experience but in my opinion, it would be preferable to freeze the documentation on the Gutenberg Documentation Website between releases.

Thanks for your consideration and for all of the great work being poured into this new editing experience.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions