-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[create-block] Split documentation into two sections #43718
Conversation
Size Change: +70 B (0%) Total Size: 1.24 MB
ℹ️ View Unchanged
|
@@ -24,6 +24,8 @@ _(requires `node` version `14.0.0` or above, and `npm` version `6.14.4` or above | |||
|
|||
It creates a WordPress plugin that you need to [install manually](https://wordpress.org/support/article/managing-plugins/#manual-plugin-installation). | |||
|
|||
[Watch a video introduction to create-block on Learn.wordpress.org](https://learn.wordpress.org/tutorial/using-the-create-block-tool/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great idea 👍🏻
Cool, this is looking great. I will take another look tomorrow 👍🏻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent addition ❤️
It would be great to document how to add more documentation pages for packages based on this PR. There is more packages that would benefit from similar restructuring. The document that covers contributions to the documentation has even a section about adding new documents:
What?
The intention of the PR is to separate the documentation for create-block into two sections. The first section is on usage and is the default documentation seen when landing on the page. The second is meant to be a child section and focuses on External Templating which is a much different use case. By splitting these out, we increase readability and allow to user to choose what content they need.
In order to facilitate this, I needed to modify the
docgen
tool to allow for packages to contain their owntoc.json
file that is then ingested when generating the mainmanifest.json
file.