A boilerplate for Jekyll using the Cardinal LESS framework.
The following instructions will help you get up and running, so that you can start using this project from your local machine.
This project depends on some software that must already be installed on your machine before proceeding.
Git (Mac users should already have this)
Ruby (Mac users should already have this)
After installing Git and Ruby, you can install Bundler by running the following command(s)*:
gem install bundler
*Mac users may need to use sudo gem install bundler
instead.
NodeJS (Use the installer)
After installing Git, Ruby, and Node, you can install Bower by running the following command(s)*:
npm install -g bower
*Mac users may need to use sudo npm install -g bower
instead.
Once you have the above tools installed, you can clone this repository to your local machine, where you will be making your changes.
cd path/to/your/projects/folder
mkdir newproject.com && cd newproject.com
git clone https://github.com/cbracco/jekyll-cardinal.git .
git remote set-url origin [email protected]:your-username/newproject.com.git
bundle
npm install
bower install
gulp
*This project uses BrowserSync and xip.io to automatically refresh your web browser on save, and to synchronize file changes and basic browser interactions (scrolling, clicking) across multiple devices. After running gulp
in the terminal, you will see an “External URL” (e.g. http://192.168.1.114.xip.io:9999) that you can use for your various devices. Simply navigate to this URL in the browser of another device connected to your network, and watch your changes and interactions happen across multiple devices at the same time!
If you are running Windows on your machine, and you’ve run into problems with the above, then you might find these guides useful:
After running gulp
, you should have a development server environment running on your local machine, and you can begin working.
To publish a production-ready version of your project, run the following command(s):
gulp publish
This task will delete any existing builds, build a production-ready version with your latest changes, and spin up a local server for you to test.
Navigate to http://127.0.0.1.xip.io:9998 in your browser to view your local production build.
Right now, a simple rsync deploy task is included so you can upload a production build to the server of your choice. You will want to modify the Gulp configuration to reflect your real server credentials.
To deploy your project via rsync, run the following command(s):
gulp deploy
Issues are logged and tracked in using GitHub’s Issues feature in this repo.