A starting point for MeteorJS applications. Includes iron-router, Bootstrap 3, Font Awesome, LESS and more.
- Included Packages
- Installation
- File Structure
- Bootstrap and Less
- SEO
- Favicons and Touch Icons
- Seed Data
- Collections:
- Router:
- Authentication
- Seed Data
- Less
- Misc:
- Clone this repo to
<yourapp>
git clone https://github.com/Differential/meteor-boilerplate.git <yourapp>
- Remove
.git
cd <yourapp> && rm -rf .git
- Start coding!
We have a common file structure we use across all of our Meteor apps. Client-only files are stored in the client
directory, server-only files are stored in the server
directory, and shared files are stored in the both
directory. The private
and public
directories are for either private or public assets.
The majority of Bootstrap can be customized with LESS variables. If you look in client/stylesheets/base/lib/bootstrap/variables.import.less
you will see a slew of configuration variables that can be tweaked to drastically change the look and feel of your site without having to write a single line of CSS.
However we should avoid modifying the core Bootstrap Less files (in case we want to update them later), and should instead override the variables in our own LESS files.
For example, to change the color of all primary buttons and links, simply add a @brand-primary
variable to stylesheets/base/variables.import.less
:
// variables.import.less
@brand-primary: #DC681D;
If you'd like to override a feature of Bootstrap that can't be modified using variables, simply create a new file in the client/stylesheets/components
directory named after the corresponding Bootstrap component (eg. buttons
in this case), and make your changes there.
// buttons.import.less
.btn {
text-transform: uppercase;
}
After your file is ready, you need to import it into client/stylesheets/base/global.less
. So, you would add in this statement:
@import '@{components}/buttons.import.less';
The reason that this is done is to avoid any issues when the LESS files are compiled into CSS. That way, if one component relies on another or you want a certain order for your components, you can avoid any issues.
You can use the dburles:factory and anti:fake packages to generate fake collection data for testing your UI. See server/seeds.js
for an example:
Meteor.startup(function() {
Factory.define('item', Items, {
name: function() { return Fake.sentence(); },
rating: function() { return _.random(1, 5); }
});
if (Items.find({}).count() === 0) {
_(10).times(function(n) {
Factory.create('item');
});
}
});