Getting Started

By on

Requirements

Almace Scaffolding has exactly the same requirements as Jekyll. For more info please refer to Installation - Jekyll.

Quick Start

  1. Fork or clone the repo.
  2. Install dependencies with Ruby gem bundler and Node.js package manager npm.
  3. Run grunt init to initialize your project.
  4. Run grunt serve to fire up a local server.
  5. Edit and customize your site.
  6. Change Git remote to your own repo.
  7. Push and deploy.

So in short for geeks:

$ git clone https://github.com/sparanoid/almace-scaffolding my-site
$ cd my-site
$ bundle install && yarn install
$ grunt init
$ grunt serve
# ...editing
$ git remote set-url origin https://github.com/sparanoid/my-site.git
$ git push -u origin master
# ...publishing
$ grunt && grunt deploy:rsync --env=prod

Download

Go to the GitHub repository for downloads, bug reports, and feature requests.

Transfer from Jekyll

You can simply copy all posts from your old Jekyll setup into _app/_posts, you can also transfer your custom pages into _app/_pages/.

Upgrading

It will be easy if you’re a casual blogger and keep every core and template file untouched. You can use the following command to update Almace Scaffolding core files:

$ grunt amsf-update

It checks the latest Almace Scaffolding build from GitHub and updates core files automatically. Please keep in mind that if you changed some of the AMSF core files this action will override the changes you made. So it’s recommended to keep your project under version control, you will always be able to compare changes for Almace Scaffolding.

Using Beta Release

By default, when you run amsf-update you will get updated files from release branch. However, I’m continuously working on Almace Scaffolding, so there may have testing branches you can try and give me feedback if you’re interested. You can check the AMSF GitHub repository for available branches, and it’s very easy to switch:

$ grunt amsf-update --branch=feat/service-worker

The branch master is the one which is always available to check out and also has the latest changes:

$ grunt amsf-update --branch=master

If you messed up with the testing branch, don’t worry, you can just run a normal update to revert them back:

$ grunt amsf-update