/cocoa-hugo-theme

Configurable, responsive blogging theme for Hugo. Demo: http://themes.gohugo.io/theme/cocoa/

Primary LanguageCSSMIT LicenseMIT

Cocoa

A consistent and responsive Hugo theme with clean typography. The primary typefaces are Open Sans, Raleway, and Ubuntu Mono.

Demo

Features

* Responsive
* Suited for blogging and personal webpages
* Disqus support
* Built-in 404 page
* Syntax highlighting (by @andy4thehuynh)
* Gravatar/static profile image (by @remeh)
* RSS feed and icon (by @mvrilo)
* Optimized SVG icons (by @robinst)
* Cache busting
* Google Analytics
* Piwik

Most features are optional and can be individually enabled/disabled in your config.toml.

Screenshots

Switch between languages

Table of Contents

Quick start

From the root of your Hugo site, clone the theme into themes/cocoa by running:

# Clone theme into the themes/cocoa directory
$ git clone https://github.com/nishanths/cocoa-hugo-theme.git themes/cocoa

# Generate site files into the public directory
$ hugo -t cocoa

# Or, serve your site and visit localhost:1313 in your browser
$ hugo -t cocoa --watch serve

Usage

config.toml

Please see the sample config.toml. Note that if you already use cocoa but have updated to Hugo 0.18, you must lowercase every params of your existing config.toml (like in the sample).

Creating posts

Posts should generally go under a content/blog directory. Typically you would run:

hugo new blog/your-new-post.md

For posts to appear on your site, you may need draft = false in the post's front matter or use the --buildDrafts option when building.

Creating fixed pages

Fixed pages such as an About page should preferably go under content/fixed or be present at the root of the content directory.

hugo new fixed/about.md

Development

This theme is built and improved upon by open source contributions. Pull requests, bug fixes, and new features are welcome!

If you're contributing CSS changes, please see the README at dev/.

Changelog

See Changelog in the wiki.

License

Licensed under the MIT License. See the LICENSE file for more details.