assemble/assemble-boilerplate-bootstrap

Build Bootstrap with Assemble instead of Jekyll.

boilerplate-bootstrap

Build Bootstrap with Assemble instead of Jekyll.

See it live →

• Converts the liquid templates to Handlebars
• Builds the HTML from templates using Assemble.
• Swaps out some Bootstrap content with metadata from _config.yml.

Quickstart

You must have NPM, Bower and Grunt installed globally before you begin.

1. Download this project

Do one of the following:

• download this project
• git clone git://github.com/assemble/boilerplate-bootstrap.git
• bower install boilerplate-bootstrap

2. Next, install Bootstrap and dependencies

Next, cd into the project run the following in the command line:

npm i && git clone git://github.com/twbs/bootstrap.git "vendor/bootstrap" && cd vendor/bootstrap && npm i

3. Customize _config.yml

Optionally update the metadata and config defaults to how you want them for your project.

4. Last, build.

You may now run grunt to build the project.

The "assemble" task

If you haven't used Assemble before, please visit http://assemble.io/docs to learn how to customize the task.

Overview

In the project's Gruntfile, the example assemble task is pre-loaded with paths and options to build the project successfully:

assemble: {
  options: {
    flatten: true,
    assets: '<%= site.assets %>',

    // Metadata
    site: '<%= site %>',

    // Templates
    partials: '<%= site.includes %>',
    layoutdir: '<%= site.layouts %>',
    layout: '<%= site.layout %>',
  },
  docs: {
    src: ['templates/*.hbs'],
    dest: '<%= site.dest %>/'
  }
}

Take a look at _config.yml to see some of the metadata and config data is defined.

Author

Jon Schlinkert

• github/jonschlinkert
• twitter/jonschlinkert

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality.

Release History

• 2013-12-22 v0.2.6 Updated dependencies, Bootstrap paths. A number of updates to gruntfile and config. Adds _config.yml to project root, to make project metadata more customizable from the start.
• 2013-08-03 v0.2.0 Refactored to be awesome.
• 2013-07-16 v0.1.0 First commit.

assemble-boilerplate-bootstrap's Issues

npm package mispelled, publish fix for issue #5 to npm

Publish fix for issue #5 to npm. On npm the package is incorrectly named.

Currently:

https://npmjs.org/package/assemble-bootstap

Should be:

https://npmjs.org/package/assemble-bootstrap

The package.json is still showing an incorrect name.

"Looking for Bootstrap..." link is broken

Some code blocks do not render correctly.

There seems to be a consistent issue around the rendering of some code blocks.

Some code blocks are not colored correctly

---

http://assemble.github.io/boilerplate-bootstrap/javascript.html#scrollspy-usage

http://getbootstrap.com/javascript/#scrollspy-usage

Other code blocks are just plain wacky

---

http://assemble.github.io/boilerplate-bootstrap/javascript.html#scrollspy-usage

http://getbootstrap.com/javascript/#scrollspy-usage

Project name differs from name in package.json

In package.json:

{
  "name": "assemble-bootstap",

Should be:

{
  "name": "assemble-bootstrap",

bootstrap is missing an r.

link to see it live gets a File not found

http://assemble.github.io/boilerplate-bootstrap/

File not found

The site configured at this address does not contain the requested file.

If this is your site, make sure that the filename case matches the URL.
For root URLs (like http://example.com/) you must provide an index.html file.

Read the full documentation for more information about using GitHub Pages.

Less error when running `grunt`

I followed the instructions in the readme and I get the folllowing error during the less build:

Running "less:site" (less) task
>> FileError: 'mixins/hide-text.less' wasn't found in theme/utils/mixins.less on line 5, column 1:
>> 4 // Utilities
>> 5 @import "mixins/hide-text.less";
>> 6 @import "mixins/opacity.less";
Warning: Error compiling theme/site.less Use --force to continue.

Aborted due to warnings.

convert to boilerplate

When assemble adds swig or liquid-node as an engine we can probably rename this to boilerplate-bootstrap. until then it's a bit of a stretch to call it a boilerplate

build bootstrap's examples

Some liquid tags are not being converted properly

Currently in footer.hbs:

{{#is slug "customize"}}
    {{ assets }}/js/less.js"></script>
  {{/is}}
<script src="{{ assets }}/js/jszip.js"></script>
<script src="{{ assets }}/js/uglify.js"></script>
<script src="{{ assets }}/js/filesaver.js"></script>
<script src="{{ assets }}/js/raw-files.js"></script>
<script src="{{ assets }}/js/customizer.js"></script>

Should be this:

{{#is slug "customize"}}
<script src="{{ assets }}/js/less.js"></script>
<script src="{{ assets }}/js/jszip.js"></script>
<script src="{{ assets }}/js/uglify.js"></script>
<script src="{{ assets }}/js/filesaver.js"></script>
<script src="{{ assets }}/js/raw-files.js"></script>
<script src="{{ assets }}/js/customizer.js"></script>
{{/is}}

Currently in default.hbs

            <ul class="nav bs-sidenav">
              {{#is slug "getting-started" }}  {{> nav-getting-started }}
              {{/is}}
              {{#is slug "css" }}  {{> nav-css }}
              {{/is}}
              {{#is slug "components" }}  {{> nav-components }}
              {{/is}}
              {{#is slug "js" }}  {{> nav-javascript }}
              {{/is}}
              {{#is slug "customize" }}  {{> nav-customize }}
              {{/is}}


            </ul>

Could be this:

            <ul class="nav bs-sidenav">
              {{#is slug "getting-started" }}
                {{> nav-getting-started }}
              {{/is}}
              {{#is slug "css" }}
                {{> nav-css }}
              {{/is}}
              {{#is slug "components" }}
                {{> nav-components }}
              {{/is}}
              {{#is slug "js" }}
                {{> nav-javascript }}
              {{/is}}
              {{#is slug "customize" }}
                {{> nav-customize }}
              {{/is}}
            </ul>

Fatal error: >> Please run "bower install" before continuing.

Prompt always ask to install bower before running grunt command.

git clone git://github.com/assemble/boilerplate-bootstrap.git
Cloning into 'boilerplate-bootstrap'...
remote: Counting objects: 838, done.
remote: Total 838 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (838/838), 2.88 MiB | 471.00 KiB/s, done.
Resolving deltas: 100% (319/319), done.
Checking connectivity... done.
MacBook-Pro-de-fernando:blog2015 fernandomonteiro$ npm install
MacBook-Pro-de-fernando:blog2015 fernandomonteiro$ grunt
Fatal error: >> Please run "bower install" before continuing.
MacBook-Pro-de-fernando:blog2015 fernandomonteiro$ bower install
MacBook-Pro-de-fernando:blog2015 fernandomonteiro$ grunt
Fatal error: >> Please run "bower install" before continuing.

npm publish the latest version

npmjs.org currently has 0.2.2 listed. Could you please publish the latest fixes to npm?

refactor to use assemble-liquid

I've wanted to do this ever since @sirlantis created assemble-liquid, I just haven't had a moment to do it. This is my reminder (or for anyone who might feel the urge to do a pr! :-)

I think the liquid version will be awesome, but for anyone who relies on handlebars we might want to just put the existing code/build on another branch

Heads-up: Bootstrap now uses a new assets folder for docs.

A relatively new change in Bootstrap 3. Document assets are now stored in

.../_gh_pages/docs-assets/css
.../_gh_pages/docs-assets/ico
.../_gh_pages/docs-assets/js

Therefore we will need to adjust the Grunt process to reflect this.

Install issues

Of the three methods in Quickstart/First I've only been able to get the middle to work. Downloading the zip and running the initial npm i is fine, but the bower install possibly ceases at

bower js-prettify#~1.4.0     ENOTFOUND Package js-prettify not found

After that there's no vendor/bootstrap to cd into. Running `bower install boilerplate-bootstrap`` doesn't work, bower can't find anything with that name.

Apologies if some or all of the above is down to my ignorance, it's seem like it should be straight forward though.

Toby

'repo-templates' is not in the npm registry.

I have tried to install your

https://github.com/assemble/boilerplate-h5bp
and when I do

npm install
inside the the download files, it throws errors,

than I thought about trying,

https://github.com/assemble/boilerplate-bootstrap
and tried to install using:
npm i && git clone git://github.com/twbs/bootstrap.git "vendor/bootstrap" && cd vendor/bootstrap && npm i
it fails again,

than I did some research and I see your repo is no longer available
missing repo: https://github.com/assemble/repo-templates

also you can see error on online travic-ci log for:

https://travis-ci.org/assemble/handlebars-helpers

you can see same error.

How I can fix this issue?

Grunt build weirdness?

This might be entirely intentional, I can't quite tell from your description?!

Having installed boilerplate-bootstrap I'm seeing some counter-intuitive behaviour when I build it - any changes I make in src/*.hbs are immediately lost/overwritten? It seems that I have to make changes in vendor/bootstrap/*.html and these are then moved into the *.hbs files, is that correct?

Trying to install via bower errors out

django-2:boilerplate-bootstrap brennannovak$ bower install boilerplate-bootstrap
bower boilerplate-bootstrap#*       not-cached git://github.com/assemble/boilerplate-bootstrap.git#*
bower boilerplate-bootstrap#*          resolve git://github.com/assemble/boilerplate-bootstrap.git#*
bower boilerplate-bootstrap#*          ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/assemble/boilerplate-bootstrap.git", exit code of #128

Additional error details:
fatal: unable to connect to github.com:
github.com[0: 192.30.252.128]: errno=Host is down