themespectre/linen

A Starter Theme for Ghost

Linen - A Starter Theme for Ghost

Demo

http://linen.themespectre.com/

Get started making great Ghost themes with Linen!

This is a starter theme for Ghost, and is not intended to be used as-is on any site or blog.

Linen is a sensible collection of default styles and templates that can be mixed, matched, removed or refactored to create a unique Ghost theme.

Linen is created and maintained by Theme Spectre

Installation

Prerequisites

1. Node.js
2. Sass (libsass)
3. Grunt

Setup

Clone (or fork) this repository into your /content/themes/ folder in Ghost.

Run npm install in the linen directory to install grunt modules.

Run grunt to build the Sass files, or grunt watch when you are ready to start themeing.

Build

To build a .zip file of your theme for distribution, run:

grunt bundle --name=yourthemename

The build folder will contain the necessary theme files, and the dist folder will contain a .zip file of your theme that you can distribute and use in other Ghost instances.

Thanks To:

• Themble & Eddie Machado for the Bones framework
• HTML5 Boilerplate
• Mono Social Icon Font
• Ghost and Casper

linen's Issues

Upgrading to support 0.4 features

Just thought I'd drop in and post a link to theme developer guide to what changed in Ghost 0.4.

I'm trying to encourage as many theme devs as possible to upgrade to use the {{asset}} helper in particular. Please use this instead of {{@blog.url}} for assets to ensure the url is correct & includes the cache-busting query-param.

Thanks 👍

Question: Live Reloading & Workflow

Hello! I'm really loving this project. It's making creating a Ghost theme really easy for me. I just have one question though:

What is your typical/ideal workflow for creating a theme using this tool? Currently I'm running 'grunt watch' on this inside the theme folder to compile my stylesheets while also running 'npm start' to watch for theme file changes and update the development ghost environment. This is working fine, but I have to manually refresh the page each time to see changes.

Is there a better workflow for this type of work than running two seperate watchers? Is there a way to have live-reloading available?