Block Card: Remove storybook for internal BlockCard component#68556
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Hi @t-hamano, According to this comment internal components should not be exposed in Storybook as they are not intended for use by WordPress extenders. Given that BlockCard is an internal component,This PR removes Storybook documentation to align with this direction. Please review it at your convenience. Thank You! |
Co-authored-by: Infinite-Null <ankitkumarshah@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Related to: #67165
What?
Removes Storybook documentation for the internal BlockCard component.
Why?
According to recent discussions, internal components that are not intended for public use should not be exposed in Storybook. This keeps our Storybook documentation focused on components that are actually useful for WordPress extenders and makes the documentation more maintainable.
Testing Instructions
npm run storybook:devhttp://localhost:50240/