Skip to content

Conversation

@Sidnioulz
Copy link
Member

@Sidnioulz Sidnioulz commented Oct 22, 2025

What I did

Renamed storybook-addons where needed to accompany changes to addon-kit on storybookjs/addon-kit#85

Checklist for Contributors

Testing

N/A

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>

Summary by CodeRabbit

  • Documentation
    • Updated addon metadata guidance to use the correct keyword "storybook-addon" (singular) instead of "storybook-addons" in addon integration catalog documentation and examples.

@Sidnioulz Sidnioulz requested a review from shilman October 22, 2025 13:18
@Sidnioulz Sidnioulz added documentation ci:docs Run the CI jobs for documentation checks only. labels Oct 22, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 22, 2025

📝 Walkthrough

Walkthrough

The pull request updates addon documentation to standardize the required keyword from "storybook-addons" (plural) to "storybook-addon" (singular) in integration catalog metadata guidance and addon writing examples.

Changes

Cohort / File(s) Summary
Addon documentation keyword updates
docs/addons/integration-catalog.mdx, docs/addons/writing-addons.mdx
Updated required keyword in addon metadata guidance from "storybook-addons" to "storybook-addon"; revised examples in metadata tables and package.json snippets to use singular form.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch sidnioulz/fix-addons-doc-keywords

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/addons/integration-catalog.mdx (1)

27-27: Improve the clarity of the guidance text.

The phrasing "You must add the storybook-addon as the first keyword" reads awkwardly with the article "the" before the code element. Consider removing it for better clarity.

-We rely on metadata to organize your addon in the catalog. You must add the <code>storybook-addon</code> as the first keyword, followed by your addon's category. Additional keywords will be used in search and as tags.
+We rely on metadata to organize your addon in the catalog. You must add <code>storybook-addon</code> as the first keyword, followed by your addon's category. Additional keywords will be used in search and as tags.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a0e3884 and 2a0b1f0.

📒 Files selected for processing (2)
  • docs/addons/integration-catalog.mdx (2 hunks)
  • docs/addons/writing-addons.mdx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
docs/**

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Update documentation under docs/ for significant changes, including migration guides for breaking changes

Files:

  • docs/addons/writing-addons.mdx
  • docs/addons/integration-catalog.mdx
🪛 LanguageTool
docs/addons/integration-catalog.mdx

[grammar] ~27-~27: Ensure spelling is correct
Context: ...a We rely on metadata to organize your addon in the catalog. You must add the ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Core Unit Tests, windows-latest
🔇 Additional comments (4)
docs/addons/integration-catalog.mdx (2)

34-34: Keyword standardization in metadata example looks good.

The keywords example correctly reflects the new singular storybook-addon keyword requirement. This aligns with the catalog metadata guidance and will help users follow the correct convention.


72-72: Package.json example correctly updated.

The example now properly demonstrates the use of the singular storybook-addon keyword, ensuring users copying this example will follow the new standard from the start.

docs/addons/writing-addons.mdx (2)

218-218: Keywords example correctly standardized.

The Integration Catalog Metadata example now shows the singular storybook-addon keyword, ensuring consistency with the integration-catalog.mdx guidance. Developers using this as a reference will implement the correct keyword format.


226-226: Explanatory text correctly references the singular keyword.

The updated guidance properly explains the role of the storybook-addon keyword in catalog discoverability, helping developers understand why this standardized keyword is important.

Copy link
Contributor

@jonniebigodes jonniebigodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sidnioulz thanks for taking the time to put together this pull request and adjust the documentation. Appreciate it 🙏 !

I've checked, and everything is good on my end.

I'll get this once the addon kit pr is merged. Sounds good?

Have a great day.

Stay safe

@nx-cloud
Copy link

nx-cloud bot commented Oct 22, 2025

View your CI Pipeline Execution ↗ for commit 5fd5036

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 44s View ↗

☁️ Nx Cloud last updated this comment at 2025-10-27 15:39:20 UTC

@shilman shilman added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 22, 2025
@Sidnioulz
Copy link
Member Author

@Sidnioulz thanks for taking the time to put together this pull request and adjust the documentation. Appreciate it 🙏 !

I've checked, and everything is good on my end.

I'll get this once the addon kit pr is merged. Sounds good?

Have a great day.

Stay safe

Sounds like a plan, cheers!

@jonniebigodes jonniebigodes merged commit 03f6307 into next Oct 27, 2025
10 checks passed
@jonniebigodes jonniebigodes deleted the sidnioulz/fix-addons-doc-keywords branch October 27, 2025 15:25
yannbf pushed a commit that referenced this pull request Oct 28, 2025
…eywords

Docs: Fix up references to old storybook-addons keyword
(cherry picked from commit 03f6307)
@github-actions github-actions bot mentioned this pull request Oct 28, 2025
8 tasks
@github-actions github-actions bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Oct 28, 2025
@ndelangen ndelangen removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:docs Run the CI jobs for documentation checks only. documentation patch:done Patch/release PRs already cherry-picked to main/release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants