Documentation - DocsPage - Add additional explanation of how to replace DocsPage

Is your feature request related to a problem? Please describe. I would like to override the docsPage with my own documentation. The current DocsPage documentation details how to override the docsPage with null but does not suggest how one might replace it with something else (specifically MDX docs). However, there is a recipe for this elsewhere.

Describe the solution you’d like Ideally, the Replacing DocsPage section would be reorganized by the three options given (null, MDX, custom component), and snippets would be given for each.

Describe alternatives you’ve considered As an alternative, it would still be helpful to link to the recipe.

Are you able to assist bring the feature to reality? I can reorganize the section and write the snippets for MDX. I don’t know about the custom component part, so I wouldn’t be able to write that part without some help.

Additional context Add any other context or screenshots about the feature request here.

[jonniebigodes]

@novellac closing this issue as the documentation was already updated by a recent pull request that was pushed by me. Feel free to ping me here if the documentation can be improved in any other way and we’ll go from there. Sounds good?

Stay safe!

[shilman]

@sethbro Sounds like maybe some kind of yarn/npm hoisting issue. @storybook/addon-essentials is just a macro that adds an un-configured @storybook/addon-docs