-
Notifications
You must be signed in to change notification settings - Fork 11
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
Storybook: cleaning up component organization and adding a table of contents for each component section #133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Scotchester
approved these changes
Feb 1, 2022
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's too much here to do a line-by-line code review, but I reviewed the results of this PR throughout my collaboration with @stephiescastle on it. Let's go 1.0!!
…de within an expanded group
…utton and Icons. Requires @babel/preset-react
…locks. Adding a few component overview docs pages and some form components updating FormInputLabel template adding placeholder for components overview docs finishing up forms docs adding search component docs tweaks to tailwind docs in storybook adding storybook info to introduction
…ting order in preview.js fixing HeroMedia story height in docs view, adds a couple more utility classes to override story height, similar to sbdocs-preview-full-width
… fixes docs view for carousels, tweaks HeroMedia to use the same method to set story height in docs view
Tweak intro and use story names with spaces on Themes page using single story hoisting for components that only have one story Very rough first pass at Components overview reorganizing some storybook docs, and updating other docs to match, adding viewports to storybook that match our tailwind breakpoints (like we have in www-frontend) fixing theme choices for stories that have full width canvas in docs adding some examples to component docs, fixing fancybox caption to strip html improvements to BlockImage documentation and stories Update Components overview Add links to example components in Components overview
…ents. Also adding addon-links to link to other stories from the react components adding custom inline rendering in DocsPages using custom react components. Also adding addon-links to link to other stories from the react components, adding TOC to base components overview page. adding custom doc component to all overview pages
showing all baselink stories on docs page
improvements to react doc blocks components Add block component descriptions, story max-width 1082, etc. setting a max-width on sbdocs-content so full width canvas doc blocks have some kind of boundary, but still a wider than the design system's max-width to allow for demonstrating how the design system's max-width works fixing height on story doc blocks in react components, removing now unnecessary canvasClass values on some doc blocks, adjustments to BlockIframeEmbed story for consistency with BlockVideoEmbed, adding a placeholder div for react doc blocks that hide the story canvas (BlockIframeEmbed) cleaning up overview docs pages, cleaning up comparison between blocks and base components, adding more docs about page layout adjusting max-width of docs divs to a more readable width, changing width of BlockImageGallery story block
updating one more instance of ArticleCarousel in the docs
144980f
to
b777605
Compare
Confirmed that everything still looks good after the rebase. Mergin' time! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
minor
Contains new features or enhancements
storybook
This issue relates to Storybook.js
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Description
This PR further refines the Storybook documentation of Explorer 1 and also includes a few bug fixes that were discovered while writing the docs. Fixes #119
.BaseCarouselCards
)ArticleCarousel
andArticleCarouselItem
have been renamed toBlockArticleCarousel
andBlockArticleCarouselItem
RoboticsDetailFactCards
andRoboticsDetailFactCardsItem
have been renamed toBlockFactCards
andBlockFactCardsItem
BlockArticleCarousel
,BlockFactCards
andHeroes
FormTextInput
and also added aFormTextArea
component with similar features (optional label, placeholder, and "required" boolean)spaceBetween
value at each breakpoint in/src/js/vendors/_swiperOptions.js
. Previously, the behavior was inconsistent as it was dependent on the initial viewport when loading the page.inlineStories: false
inparameters.docs
forces the stories in the DocsPage to load in an iframe, which solved the issue we were having with swiper carousels not initializing correctly on docs pages.Migration Guide
A change has been made to the
BaseCarouselCards
template, which affectsBlockArticleCarousel
andBlockFactCards
templates as well. The navigation div,<div class="swiper-navigation lg:block">
, should changelg:block
toxl:block
. This ensures the navigation arrows only appear when the space between each card is 56px (i.e. the 1280px breakpoint).Instructions to test
Tested in the following environments/browsers:
Operating System
Browser