I did a last-minute lightning talk at Thursday’s Fronteers Belgium event where I gave an introduction about Bedrock.
Here are the slides. There is a video as well which I hope to post soon!
View What is Bedrock? on SlideShare.
The new Bedrock strategy is one to drive public adoption to the tool, so it becomes better. In order for this to happen, we need to remove as much friction as possible.
We’ve heard that some people have been experimenting with Bedrock, which we are very happy about.
Based on feedback we have received, we added the following to the documentation:
Are you struggling with something? E-mail us, comment on this post, just let us know, and we will add an explanation on how to achieve it.
Bedrock is almost turning 2 years old, and we have some news to share.
There is now a tutorial on getting started with Bedrock.
We want to drive the adoption of Bedrock by others so it can be improved. The goal of Bedrock is to build the ultimate static site generator, with a heavy focus on HTML prototyping.
One way you can support Bedrock is by simply ★’ing the Github project.
While the tool hasn’t had a lot of external adoption yet, we use it for almost all of our projects at Mono. We’ve found it extremely worthwhile and want to share it with the community.
Bedrock has an open source MIT license, and is based on modern coding standards, so you are effectively never locked in. Whatever you create can be transported to other systems. In fact, I made the first version of this new website in Bedrock and then moved it to WordPress when it was ready enough.
Some of our future plans include providing Bedrock “bases” that document certain frameworks, such as Bootstrap 4 or Google’s Material Design. This way can easily get started prototyping with a certain library.
Do you find value in Bedrock? Did you use it for a project? Let us know! You can e-mail us at firstname.lastname@example.org or just place a comment below. We welcome any feedback!
In Bedrock 1.3.0 we made a change where as a user, you can now access the category listing in the component styleguide. For example, if you prefix all your “Company X” components with
x-, you can list these as separate items in the styleguide. You can find more info in #186.
The newest version of Bedrock has been released! Check out the release notes on Github.
This summer we will be organising a Bedrock workshop afternoon where I will teach people how to use Bedrock.
If you are interested ping me on Twitter. Currently there are 2-3 people up for it, please join in! I will likely set up a Doodle to pinpoint a good date.
Follow @usebedrock to stay up to date.
The new 1.1 release is almost upon us. You can grab a pre-release here if you are interested.
I made some videos demonstrating the 3 coolest new features: icon documentation, dark mode and page states.
At the moment, upgrading a Bedrock install is a semi-manual process. We are working on automating this as much as possible.
If you are using an older version of Bedrock, it is best to use a combination of the upgrade command provided by the Bedrock command line interface and a diff tool that allows you to diff folders to upgrade your Bedrock install.
Personally I use DeltaWalker to compare my project’s folder to a standard Bedrock install.
You can use the Bedrock upgrade command contained in bedrock-cli to update every file in
This will update every file in
You will then need to manually transfer a few files, depending on how old your Bedrock install is.
These are the files you can transfer as-is:
There are some files that didn’t exist in older versions of Bedrock that need to be added:
Within bedrock.config.js you will probably need to set a path to where you use the colors feature. It is not possible to use Bedrock at the moment without using this feature.
You will also need to set whether you want to use icon fonts or SVG icons.
Then there is a tricky one – the
npm install you need to list these as
devDependencies. Within the logic of Bedrock, Bedrock’s code itself is a dependency and your application’s code is a
We changed some folder names to be able to provide better functionality.
The Bedrock upgrade tool does not help with this, this is a manual process.
In the beginning the folder for styleguide components was named
_components. So to upgrade your Bedrock to the latest install, that folder needs to be named
_ part of this logic is to disallow Bedrock from indexing Jade templates within
_components as pages that show up in the page index/page tree.
The same counts for the
_layouts and optional
Basically your tree has to look like this:
. ├── content │ ├── data │ ├── docs │ │ ├── overviews │ │ └── styleguide │ ├── icon-font-source ---> Optional if you use icon fonts │ ├── icons ---> Optional if you use svg icons │ ├── images │ ├── js │ ├── scss │ └── templates │ ├── _components │ └── _layouts │ └── _includes ---> Optional, depends on how you code your templates │ └── _mixins ---> Optional, depends on how you code your templates ├── core ├── discovery ├── js ├── scss │ ├── components │ └── vendor ├── tasks ├── templates │ ├── includes │ ├── layouts │ ├── mixins │ └── styleguide └── util
Note that within
core the includes, layouts and mixins folders do not use an underscore and within
content they do. So if you are globally replacing file references within the project be careful, because you will run into errors.
So, I hope this helps if you are running into problems upgrading Bedrock.
We are always available to help – just log an issue on Github and we wil try to help out.
A few days ago I tested an interesting alternative to Bedrock, called Fractal.
It’s more of a component style guide that can be added to any project than a prototyping tool, but there are a lot of similarities.
It builds on a lot of similar ideas as Bedrock, so me this is a validation that what we are doing here is right.