1.14

New feature: it is possible to add a source attribute to the YAML front matter of a component, which will result in a “tag” being displayed next to the component. This is useful to distinguish, for example, official framework components from custom ones.

Screenshot:

1.12.1

• This is a maintenance version of Bedrock. As noted in a blog post in December, Bedrock now requires node 10.X to run. We intend to keep up with Node versions for security reasons.

1.11.0

• Merged #280 which introduces a change to how you run Bedrock. In the previous incarnation, we required gulp to be installed globally. Leveraging the power of npm scripts, this is not necessary anymore. Yay! In practice this does mean that the command to run Bedrock changes from gulp to npm start. The command to create a build changes to npm run build.

1.10

1.10 is the biggest Bedrock release in months! We are excited about the following changes:

• We've worked on something new that we call Bedrock bases. We are providing a base for Bootstrap 4 and Material Design. Read the blog post for an introduction
• We reworked the way we treat Bedrock's internal CSS. We only provide the barely necessary CSS to make Bedrock function in core; this is the CSS for the tree collapsing and showing the page tree. As a Bedrock author you are supposed to do your own styling to make your style guides look good. This allows you to style a styleguide exactly the way you want without clashing CSS. But given the Bedrock bases (see above), you also have an easy way to not have to do this work.
• We reworked the way documentation works, treating color and typography documentation as regular component documentation. Look no further than the Bedrock bases for an example of how this works e.g. Material's typography, colors and icons.
• You have always been able to categorize components by their folder prefix (e.g. c-) but the way this works has been clarified together with recent documentation updates (see configuration)
• You have always been able to determine the order of categories in the styleguide (e.g. put custom components last) but the way this works has been clarified together with recent documentation updates (see configuration)
• For the adventurous - it is now possible to loop through documentation categories yourself - you don't depend on Bedrock's setup. You can mirror templates from core to content to start building your own style guide without breaking Bedrock's internals. This is kind of niche functionality which we have not used ourselves so far, and will likely improve upon when we use it in real projects.

1.9

• Make icon font output path configurable. Set a path in icons.iconFontPath in bedrock.config.js to determine where the CSS for your icon font should land.
• Improvements to the display of page states. We now “humanize” the names
• Improvements to the display of <title>s in the style guide. We now show the components name in each browser tab instead of just “Styleguide”.
• Update to latest gulp-sass with better support for CSS grid.
• Deprecate the dark UI config setting (ui.dark) in preparation of a Bedrock version where the styling of the styleguide is separated from Bedrock

1.8.0

• The selectors for icon fonts and svg icons are now configurable via the bedrock.config.js. For more information see issue #190 . Fixed in PR #198 .

1.7.1

• New feature: Added basic support for multiple languages. Read the documentation on the Bedrock website.

1.6

• Address a security vulnerability related to FontCustom (icon font generation)
• Remove some references to Bootstrap as Bedrock is CSS framework-neutral out of the box
• Minor improvements

1.5

• Set node requirement to 8.3 using .nvmrc
• Several small improvements to default templates
• Several small bug fixes

1.4.1

• Fixes #182