Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

The "coolblue" template from styleshout.com - modified for bloggart

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 static
Octocat-spinner-32 README.rst
Octocat-spinner-32 base.html
Octocat-spinner-32 listing.html
Octocat-spinner-32 post.html
Octocat-spinner-32 post_meta.html
README.rst

styleshout.com's coolblue template for bloggart

Description

This is the coolblue template from styleshout.com, modified for bloggart. It relies on the "default" template in bloggart and overrides a few templates here and there.

As the original coolblue template was distributed under CC Attribution, this project should also fall under it too.

Usage

  1. At the root of your bloggart clone, run:

    $ git submodule add git://github.com/rctay/bloggart-theme-coolblue.git themes/coolblue
    

    This theme tracks the rc/master branch in my bloggart fork very closely, and the branches here corresponds to branches there. Therefore, if your bloggart setup uses my branches, you should specify the branch to the git submodule add command. For example:

    $ git submodule add -b rc/master git://github.com/rctay/bloggart-theme-coolblue.git themes/coolblue
    
  2. Modify your config.py:

    diff --git a/config.py b/config.py
    index dab53cb..b0d4e27 100644
    --- a/config.py
    +++ b/config.py
    @@ -15,7 +15,7 @@ host = 'localhost:8080'
    
     # Selects the theme to use. Theme names correspond to directories under
     # the 'themes' directory, containing templates and static content.
    -theme = 'default'
    +theme = 'coolblue'
    
     # Defines the URL organization to use for blog postings. Valid substitutions:
     #   slug - the identifier for the post, derived from the title
    
  3. If you've already posted posts in your previous theme, you will have to regenerate them for the coolblue theme to take effect.

Something went wrong with that request. Please try again.