Simplified fork of [Hacker](https://github.com/pages-themes/hacker)
Go to file
Ben Balter 0c80ff632d 💎 bump 2016-12-14 14:57:48 -05:00
_layouts append build revision to stylesheet path to break cache 2016-12-14 14:57:48 -05:00
_sass normalize stylesheet names 2016-12-13 11:23:24 -05:00
assets hard code theme name in stylesheet to avoid conflict 2016-12-13 15:25:38 -05:00
script Add release script 2016-12-14 13:04:11 -05:00
.gitignore Ignore compiled gems 2016-12-13 10:27:25 -05:00
.travis.yml add Travis config 2016-12-13 10:27:25 -05:00
CODE_OF_CONDUCT.md add Code of Conduct 2016-12-13 10:27:25 -05:00
CONTRIBUTING.md add contributing file 2016-12-13 10:27:25 -05:00
Gemfile normalize stylesheet names 2016-12-13 11:23:24 -05:00
LICENSE License under CC0 2016-12-14 11:04:12 -05:00
README.md add thumbnail to README 2016-12-14 12:28:39 -05:00
_config.yml hard code theme name in stylesheet to avoid conflict 2016-12-13 15:25:38 -05:00
another-page.md init 2016-10-06 19:01:49 -04:00
index.md $1 2016-11-07 10:35:51 -05:00
jekyll-theme-hacker.gemspec 💎 bump 2016-12-14 14:57:48 -05:00
thumbnail.png init 2016-10-06 19:01:49 -04:00

README.md

The Hacker theme

Build Status Gem Version

Hacker is a Jekyll theme for GitHub Pages. You can preview the theme to see what it looks like, or even use it today.

Thumbnail of hacker

Usage

To use the Hacker theme:

  1. Add the following to your site's _config.yml:

    theme: jekyll-theme-hacker
    
  2. Optionally, if you'd like to preview your site on your computer, add the following to your site's Gemfile:

    gem "github-pages", group: :jekyll_plugins
    

Customizing

Configuration variables

Hacker will respect the following variables, if set in your site's _config.yml:

title: [The title of your site]
description: [A short description of your site's purpose]

Additionally, you may choose to set the following optional variables:

show_downloads: ["true" or "false" to indicate whether to provide a download URL]
google_analytics: [Your Google Analytics tracking ID]

Stylesheet

If you'd like to add your own custom styles:

  1. Create a file called /assets/css/style.css in your site
  2. Add the following content to the top of the file, exactly as shown:
    ---
    ---
    
    @import "{{ site.theme }}";
    
  3. Add any custom CSS (or Sass, including imports) you'd like immediately after the @import line

Layouts

If you'd like to change the theme's HTML layout:

  1. Copy the original template from the theme's repository
    (Pro-tip: click "raw" to make copying easier)
  2. Create a file called /_layouts/default.html in your site
  3. Paste the default layout content copied in the first step
  4. Customize the layout as you'd like

Roadmap

See the open issues for a list of proposed features (and known issues).

Project philosophy

The Hacker theme is intended to make it quick and easy for GitHub Pages users to create their first (or 100th) website. The theme should meet the vast majority of users' needs out of the box, erring on the side of simplicity rather than flexibility, and provide users the opportunity to opt-in to additional complexity if they have specific needs or wish to further customize their experience (such as adding custom CSS or modifying the default layout). It should also look great, but that goes without saying.

Contributing

Interested in contributing to Hacker? We'd love your help. Hacker is an open source project, built one contribution at a time by users like you. See the CONTRIBUTING file for instructions on how to contribute.

Previewing the theme locally

If you'd like to preview the theme locally (for example, in the process of proposing a change):

  1. Clone down the theme's repository (git clone https://github.com/pages-themes/hacker)
  2. cd into the theme's directory
  3. Run script/bootstrap to install the necessary dependencies
  4. Run bundle exec jekyll serve to start the preview server
  5. Visit localhost:4000 in your browser to preview the theme

Running tests

The theme contains a minimal test suite, to ensure a site with the theme would build successfully. To run the tests, simply run script/cibuild. You'll need to run script/bootstrap one before the test script will work.