-
Notifications
You must be signed in to change notification settings - Fork 120
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
Docs design refresh #626
Docs design refresh #626
Conversation
- Read/write localStorage value instead
- When provided, it auto-sets the localStorage value to the param's value - Use it for framework logos on homepage
- For each version & framework combo, add: `/docs/<version?>/<framework>/<path>` -> `/docs/<version?>/<path>` - Update static redirects to no longer point to URLs with framework
- Only filter content client-side - IfRenderer still available in MDX, for older content - Update CodeSnippets to account for client-side-only filtering
Co-authored-by: Kyle Gach <[email protected]>
✅ Deploy Preview for storybook-frontpage ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
* Move everything into RendererSelector * Remove old pill * Improve design of the content menu * Try not use as modal * Update RendererSelector.tsx * Fix styling * Update RendererSelector.tsx * Fix focus state on pills * Update RendererSelector.tsx * Tweaks - Prevent forwarding `isActive` to DOM - `React.FC` should only be used for components that accept `children` --------- Co-authored-by: Kyle Gach <[email protected]>
Co-authored-by: Shaun Lloyd <[email protected]>
03a46d7
to
c223f89
Compare
I wrote a list of issues found during QA here Heads up, the sitemap diffs no longer exist so wasn't able to QA that. |
- Consistent link styles for both - Block-level links - Slightly darker gray color - Blue, no underline on hover
QA feedback, round 1
@domyen — Thank you! Those diff links expire after 7 days, which is why they 404'd. I just re-generated them using the latest code, and would appreciate you checking them! The relevant portion (with new links) is quoted here:
|
Reviewed the sitemaps, it looks good to me! |
What was done
See corresponding content updates in storybookjs/storybook#24925
renderer
query param/docs/<version?>/<framework>/<path>
->/docs/<version?>/<path>
renderer
instead offramework
in codebaseindex.md
pages (linked headings)This mega-PR contains the following PRs:
How to test
Note
QA'ing the following steps is much more valuable than an in-depth code review, at this time
sitemap/sitemap-0.xml
(used for search engines)sitemap-all/sitemap-0.xml
(used by Algolia)argTypes
API referenceargTypes
API reference is a good one)The rest of these steps can only be tested with the corresponding content changes. I've made a special deploy preview for this purpose.
Most importantly, click every link you can, in content and the sidebar, on a variety of pages (top-level, e.g. Writing stories; mid-level, e.g. Args; and third-level, e.g. Configure TypeScript).
next
tochanges-from-docs-updates
)Rollout plan
Order matters!
components-marketing
updates across other sitesframework
facet from Algolia DocsSearch config and kick off a crawlframework:agnostic
across all sitesFootnotes
In Chrome, at least: Open DevTools → Application tab → Expand
Local storage
under the Storage heading in the left sidebar → Click on the URL for the deploy preview ↩ ↩2 ↩3 ↩4