Read the blog post or checkout the demo for more information.
There are three ways to install this boilerplate. Composer is by far the easiest to maintain.
A prerequisite for using this method is that you have Composer installed in your system.
Begin by creating a composer.json in the root of Magento, and ensure it has the following:
{
"repositories": [
{
"type": "vcs",
"url": "https://github.com/magento-hackathon/magento-composer-installer"
}
],
"require": {
"magento-hackathon/magento-composer-installer": "*",
"webcomm/magento-boilerplate": "2.0.x-dev"
},
"extra": {
"magento-root-dir": "./",
"magento-deploystrategy": "copy"
},
"config": {
"preferred-install": "dist"
}
}
Finish by installing Composer dependencies and a couple of optional enhancements:
cd your-project/
composer install
# If you wish to autoload composer files
cp vendor/webcomm/magento-boilerplate/index.php .
# If you wish to automatically set *.dev domains to developer mode
cp vendor/webcomm/magento-boilerplate/.htaccess .
# If you wish to run your own theme, replace "mytheme" with the name of your theme
cp -Rf vendor/webcomm/magento-boilerplate/app/design/frontend/boilerplate app/design/frontend/mytheme
cp -Rf vendor/webcomm/magento-boilerplate/skin/frontend/boilerplate skin/frontend/mythemeNow you should have a new folder
vendor/webcomm/magento-boilerplatewith our repository and new symbolic links in Magento. You can update to each new version withcomposer update.
Firstly, clone our repo down to a folder:
git clone [email protected]:webcomm/magento-boilerplate.git your-projectSecondly, copy in a supported Magento version over the top of the reop:
wget http://www.magentocommerce.com/downloads/assets/1.8.1.0/magento-1.8.1.0.tar.gz
tar -zxvf magento-1.8.1.0.tar.gz
mv -f magento/* your-project/You may update to each new version with
git pull.
- Download Magento from http://www.magentocommerce.com/download.
- Download our repo from https://github.com/webcomm/magento-boilerplate/archive/master.zip.
Merge the folders, and you're good to go.
Developing in our boilerplate theme is rather easy. There are basically two general possibilities:
- Copy or rename the boilerplate theme and start editing it.
- Build a new "child" theme under the
boilerplatepackage and only edit the things you need to edit.
The second approach has the advantage that updating the boilerplate theme is quite easy. You would just replace the files under boilerplate/default with the new ones and check if you need to copy some changes to the files you edited. Updating the theme with the first approach is a nightmare. The advantage of the first approach is that you can still build custom child themes like mytheme/xmas. Anyway, this is also still possible with the second approach by using Aoe_DesignFallback.
To begin, you should either copy our theme or rename our theme to something useful by doing:
cp -Rf app/design/frontend/boilerplate app/design/frontend/mytheme
cp -Rf skin/frontend/boilerplate skin/frontend/mythemeOnce you've copied or renamed the theme, you will need to add it to the bottom of the .gitignore file:
!/app/design/frontend/mytheme
!/skin/frontend/mythemeFrom here, you'll want to install the site and enable the theme through Magento's design configuration. Firstly, install your site like any other Magento installation. There's plenty of guides out there on that. Then, visit System > Configuration > Design > Package and change the package from default to whatever you named your theme (such as mytheme).
To begin, you should create a new folder with your new theme name (e.g. mytheme) under app/design/frontend/boilerplate/mytheme and skin/frontend/boilerplate/mytheme.
From here, you'll want to install the site and enable the theme through Magento's design configuration. Firstly, install your site like any other Magento installation. There's plenty of guides out there on that. Then, visit System > Configuration > Design and change the package from default to boilerplate. Additionally, change the translations, templates, skin, layout and default to whatever you named your theme (such as mytheme).
The process we like to stick with when developing is have our dependencies managed for us, and use a task runner to compile them into CSS / JavaScript files which are served to the user. You don't have to do this, however it's a great way to save time down the track, even if there's a bit of a learning curve to begin with.
The first thing to do this is install Bower and gulp.js (both are NodeJS applications).
To install Bower dependencies (not included in the theme becuase they're simply not required for everybody), you'll need to use Bower.
cd skin/frontend/mytheme/default
bower installOnce you have gulp.js installed globally, open up your terminal and change directory into your theme and execute gulp:
cd skin/frontend/mytheme/default
npm install
gulpThat's it. From now on, your changes you make to LESS files will automatically compile into CSS, and the same with JavaScript. Refresh your page to see changes!
This theme does not ship with all Bootstrap CSS and JavaScript. The reason is, most sites don't need all the components and therefore you're bloating a site by providing more than required. We're including only the files required to get this boilerplate theme running.
To add new Bootstrap styles, simply open up less/style.less. From there, you may directly import Bootstrap files, or your own files which in turn import Bootstrap's. For example, add the following into less/style.less:
@import "media.less"; /* Relative to less/style.less */Then, in less/media.less:
/* In less/media.less */
@import "../bower_components/bootstrap/less/media.less"; /* Relative to less/media.less */
.media {
/* Your custom overrides go below the call to Bootstrap's styles */
}You may choose to import more than just Bootstrap's LESS / CSS files. Feel free to import anything this way, it's good practice.
To add new JavaScript files, open up gulpfile.js. gulp.js is seperated into a number of tasks. One of them is the js task. Inside it, you'll see a bunch of JavaScript files listed out. If you require more Bootstrap files (or indeed any JavaScript files), simply add them to the list.
// ...
.src([
'bower_components/jquery/jquery.js',
'bower_components/bootstrap/js/transition.js',
'bower_components/bootstrap/js/collapse.js',
'bower_components/bootstrap/js/carousel.js',
'bower_components/bootstrap/js/dropdown.js',
'bower_components/bootstrap/js/modal.js',
// Add new files here
'js/script.js'
])
// ...- Notify isn't working? - check you are not running
gulpon a headless (command-line only) server, such as a remote webserver or Vagrant box. Windows may need modification of yourgulpfile.jsandpackage.jsonfiles to work properly.
Feel free to edit any of the files under dist/css and dist/js if you'd like to manually develop your site. There's no harm in doing this, if you don't want to use gulp.js in the future. Keep in mind that, if you decide to compile with gulp.js that you will lose your manual changes.
The git repo for this project can be found at http://github.com/webcomm/magento-boilerplate, and a demo can be found at http://magentoboilerplate.webcomm.com.au.
We feel that we've done a pretty decent job at creating a great starter theme for developing up a Magento site. We chose Twitter Bootstrap 3 not because we want all sites to look like Bootstrap, we hate that too. Bootstrap creates a great foundation of reusable components which you can use to create something truly unique.
The reason Boilerplate themes exist is so you can spend less time on getting ready to start productive work by removing the repetitive first steps. We've taken care of the boring, so you may focus on the unique.
If you like our work, we're not after your money, but rather, we'd love to see a pull request, or even an issue, on your vision for how this can be improved! At the end of the day, if we can all create something truly useful to a lot of people, everybody wins and we can all go home earlier.