Yet another jekyll theme.
CSS HTML JavaScript
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
_data
_includes
_layouts
_posts
_sass
css
js
.gitignore
404.md
README.md
_config.yml
about.md
favicon.ico
favicon.png
feed.xml
index.html
robots.txt
sharer.png
sitemap.xml

README.md

Jekyll-Read Theme

A jekyll theme built on top of default jekyll theme and inspired by Read WordPress theme.

Features:

  • Responsive Layout
  • Sitemap
  • Atom feed
  • Mailchimp Newsletter subscription
  • Disqus Commenting
  • Google Analytics
  • Scheme.org Formatting
  • Featured image for posts
  • Minimal configuration

Installing

  • Download zip from the latest release.
  • Change values in _config.yml as required. This file is commented wherever required.
  • Create a file named CNAME and your domain (example.com) as its only line if you have your own domain.
  • Change the value of the url variable to your blog's URL (eg: http://githubusername.github.io).
  • Uncomment and add a value to disqus variable if you want to have disqus commenting enabled.
  • Uncomment and add values to ga_id and ga_domain to add Google Analytics.
  • Add a Mailchimp Newsletter form submission URL to mailchimp to add a newsletter subscription form.
  • There's a file projects.yml in _data directory by default. You can add title and url values to it to add a Project submenu in the top navigation. Delete this file to remove the submenu.
  • Replace favicon.ico, favicon.png and sharer.png with your own images.
  • Create new posts in the _posts directory. If a cover variable is present in the front matter as shown in the 2015-12-06-an-example-post file, it will be used as a cover image for that post. Its value should be absolute URL to the image.
  • Now install jekyll and jekyll-paginate gems to test the site locally.
  • Run jekyll serve -w in the theme's directory to run the server and goto http://127.0.0.1:4000 to check the changes.
  • If everything works well, push your changes to github.