-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve the docs for V5 launch #5820
Conversation
This pull request is automatically deployed with Now. |
d91c074
to
fdc055f
Compare
fdc055f
to
1e6650b
Compare
Codecov Report
@@ Coverage Diff @@
## next #5820 +/- ##
=======================================
Coverage 34.91% 34.91%
=======================================
Files 648 648
Lines 9496 9496
Branches 1377 1377
=======================================
Hits 3316 3316
Misses 5563 5563
Partials 617 617 Continue to review full report at Codecov.
|
1e6650b
to
9d7c28d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look great!
@@ -28,7 +28,7 @@ | |||
"common-tags": "^1.8.0", | |||
"gatsby": "^1.9.279", | |||
"gatsby-link": "^1.6.45", | |||
"gatsby-plugin-sharp": "^2.0.12", | |||
"gatsby-plugin-sharp": "^1.6.48", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ndelangen why downgrade?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some issues, I think the gatsby-plugin-sharp v2 is for gatsby v2
> We're trying to make storybook more zero-config over time, **help to hook into the config of generators is very welcome**. | ||
|
||
<details> | ||
<summary>This is what the config for storybook looks like when using CRA in dev-mode:</summary> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we put this in our docs? Can we just link to a file that won't get out of date every time somebody makes an change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no single file that has this info, it's all merged from multiple presets.
I think it's valuable for people who want to customize to quickly see what we're shipping with to most users.
|
||
```js | ||
{ | ||
mode: 'development', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicated??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, didn't know a good way of having a SSOT for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments above
@ndelangen Outside the scope of this PR but we should publish the |
# Conflicts: # docs/src/pages/basics/guide-mithril/index.md
I agree with the out of scope part I'm not sure publishing these components as a library is worth our time. I mean maybe. I think the docs should be more pure about 'content' and not about styling. |
@shilman Good to merge? |
# Conflicts: # docs/src/pages/configurations/theming/index.md
@shilman can we please merge this, do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great job 🚀
Adding redirects as documentation before I merge, although finally they will be applied to the frontpage directory not here |
Issue: docs are lagging behind implementation
What I did
Bringing the docs up to date