Skip to content

Releases: usebedrock/bedrock

1.4.0

11 Jan 22:15
Compare
Choose a tag to compare
  • Allow the user to set custom namespaces for components (fixes #186)

1.3.0

11 Jan 09:35
Compare
Choose a tag to compare
  • Added marked and moment.js as dependencies, please run npm install to download these dependencies
  • Added a markdown example to the base repository

Bug fixes

28 Sep 13:20
Compare
Choose a tag to compare
  • Several small bug fixes
  • Better defaults for styleguide

Bedrock 1.2.1

30 Aug 09:46
Compare
Choose a tag to compare

Important: to continue using bedrock upgrade, please update your bedrock command line to the newest version. Run npm install -g bedrock-cli to do so.

screen shot 2017-08-30 at 11 58 19
The tree now has a selected state and a count of the page states

  • We use PugJS (the successor to Jade) for templates now
    • To migrate older projects, run bedrock upgrade. This will check the Bedrock version, if it is below 1.2.0, it will automatically migrate templates to pug.
    • Older projects will sometimes need updating of the way content is rendered. The difference between the version of Jade that we used and Pug is mostly on the interpolation syntax. On the wiki we will document examples to help with migration. The gist of it is that you don't use #{} anymore but directly write javascript in the brackets.
    • There is an automatic migration for some common parts of Bedrock (e.g. common patterns in master templates, the mixin for SVG icons)
  • The tree and page states feature has been updated to include a selected state
  • The tree feature has been updated to now show how many states a page has
  • We fixed some bugs when it comes to remembering the state of the tree.
    • Important here is that your project should be named in package.json i.e. the name field needs to be different for every project.
    • Within package.json there is a new entry called bedrockVersion that denotes the version of bedrock used.
  • Work has been done on #165 (Optionality). It is now possible to set styleguide to false. This is untested so far.

Bugfixes

08 Aug 14:31
Compare
Choose a tag to compare

This release groups some recent bugfixes.

  • Allow vertical resize of components in styleguide
  • Fixes #148 Templates named index.jade cause problems
  • Add package-lock.json file (new NPM feature)
  • Make styleguide more resistent to project specific CSS
  • Fix #171 issue with icon fonts - Improve icon fonts overview page

1.1

07 Jun 21:16
Compare
Choose a tag to compare
1.1

A feature release!

Page states

We have implemented a feature to display page states. Simply make templates in a format like this:

  • base-page.jade for the "base page"
  • base-page--state.jade for the "base page" in "state"
  • base-page--state2.jade for the "base page" in "state2"

The states will show up in a separate menu:

screen shot 2017-06-01 at 14 47 36

Improved icon documentation

We have improved the ways you can document icons. You can now add sub folders to the SVG icons directory. Every folder will generate its own section within the styleguide.

For example:

screen shot 2017-06-01 at 14 40 31

Dark mode

Set ui.dark to true in bedrock.config.js to enable dark mode.

1.0.7

22 May 07:21
Compare
Choose a tag to compare
  • Fix bugs related to the tree
    • Tree names couldn't be repeated, now they can
  • Options change: rename generateIconsFromSource to generateIconFont

1.0.6

07 Mar 16:21
Compare
Choose a tag to compare
  • Better error logging for missing images
  • Add example array loop and object loop in default Bedrock template
  • Minor bugfixes
    • Make sure you can use +icon mixin in documentation pages
    • Fix #115 prototype navigation in Microsoft Edge

1.0.5

21 Feb 18:24
Compare
Choose a tag to compare
  • Add a meta tag that prevents search engines from indexing prototypes

1.0.4

21 Feb 16:14
Compare
Choose a tag to compare
  • Fix bug with components where you couldn't use space based indentation within a component
  • Default location of colors file changed. In line with possible ITCSS strategy - but the user can still set it where they want in config.