What's the problem?

I have successfully customized my storybook with addon-themes and created the dark style for div with a .docs-story class.

I tried to style the "show code" button on the docs tab without luck via CSS in preview-head.html.

The problem is that there is no unique CSS class to scope (only dynamically generated classes):

<div class="css-11xgcgt">
<button c

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

🚀 Feature

We should validate docs/blog/pages frontmatter against a Joi schema:

• prevent the user to use bad frontmatter
• display friendly error messages when this happens
• allow unknown frontmatter (user can assign additional metadata to each doc)
• unit-test this validation logic
• try to use the frontmatter TS types in the theme?

Some initial work has been done in https://gith

Bug Report

Current behavior

I think there's a mismatch of environment variables being read by babel (JSX config) and Styleguidist, causing some issues deeper down.

(I've noticed this was raised before but was closed)

• build.js sets the env to be production here: https://github.com/styleguidist/react-styleguidist/blob/master/src/s

Currently, the width of the logo is fixed at calc(100% / 6) so that the nav links are flush with the search bar:

Unfortunately, this leads to cut-offs in some translations with longer words in the nav bar:

<img width="127

After renaming some functions, I noticed that the documentation website contained some broken links. E.g. {@link Foo} wasn't linked because Foo got renamed and instead, the website contained the literal text "{@ link Foo}".

I searched for an option to a) get all invalid symbols and b) a way to fail the build if it contains invalid symbols so this doesn't happen again.

The `--listInvalidS