Feedback for /writing-docs/doc-blocks docs page

[storybook-bot]

👍	👎
0	8

[storybook-bot]

/docs/7.0/react/writing-docs/doc-blocks

👎	v7.0	react	ts

??????!!!!!!!!!!

[jonniebigodes]

Thanks for the feedback; if you could provide us with some context on your issue with the documentation, we'd appreciate it. Closing this for now until we get some clarification

[storybook-bot]

/docs/7.0/react/writing-docs/doc-blocks

👎	v7.0	react	ts

I keep seeing this @storybook/blocks import, but I have no idea what it is, it's not a package or something. There is no such a directory in my project and the app is just crashes.

[jonniebigodes]

The @storybook/blocks is a part of Storybook's packages that should have been installed into your project if you added Storybook to your application. They're tailored to help you document your components. See here for an abridged overview of how to use them with Storybook. I recommend you open up an issue here in the monorepo so that the maintainers are aware of the situation and either they or the community is able to help you solve it.

[storybook-bot]

/docs/7.0/react/writing-docs/doc-blocks

👎	v7.0	react	ts

Can't understand what @storybook/blocks is. I don't have such a directory in my project. @storybook/react 7.0.18

[jonniebigodes]

See the comment I posted above. To reiterate on it, the @storybook/blocks is a Storybook package that should have been installed when you added Storybook to the project. Commonly the npm packages are downloaded and placed inside the node_modules directory. And referenced in both your package.json and yarn.lock / package-lock.json files, containing not only the package name, version, and associated metadata (dependencies on a said package, checksums, etc.). If you don't see it listed in your project's development dependencies, you can try and add the package manually by running yarn add --dev @storybook/blocks or the equivalent for npm if you're not using yarn. If there are still issues with this, we recommend opening an issue here in the monorepo so that the maintainers are aware of this and either they or the community is willing to solve the issue.

[storybook-bot]

/docs/7.0/react/writing-docs/doc-blocks

👎	v7.0	react	ts

[storybook-bot]

/docs/7.0/react/writing-docs/doc-blocks

👎	v7.0	react	js

This is unclear. The API documentation and this needs some more explanation.

[storybook-bot]

/docs/7.5/react/writing-docs/doc-blocks

👎	v7.5	react	ts

Please provide detailes technical documentation for how these things work, not just examples of a single happy path. Really hard to figure out how to customize these things.

[jonniebigodes]

Thanks for reaching out to us with your feedback. We appreciate it 🙏 . So that you're aware, this is an introduction page highlighting the features and available Doc Blocks. We have them documented individually in the API section of the documentation with all the available Blocks, options, and examples on configuring them with either MDX or within a story.

Closing this until we can have better clarity and context on what's intended.

[storybook-bot]

/docs/7.6/writing-docs/doc-blocks

👎	v7.6	vue	js

This page is full of images of what the outcome should be, but I literally just want a code example of the current best practice for documenting individual props. The call out "Accepts parameters in the namespace parameters.docs.argTypes." is not sufficient.

[storybook-bot]

/docs/7.6/writing-docs/doc-blocks

👎	v7.6	angular	ts

Where is angular docs?