Typo (and Jasper) are great themes. Things are well-built, and Typo is typographically tuned. However, they're not "safe" Jekyll themes. When hosting your Jekyll site on GitHub Pages, GitHub runs the site with the
--safe switch. Jasper and Typo have Jekyll plugins, which are not supported by GitHub Pages. So you need to build the site either locally or using Continuous Integration (such as Travis CI) and host it on GitHub.
Pure Typo is an attempt to ease this process. There's no need to build the site locally and push it to GitHub or use Continuous Integration—it all just works!
Besides, Jasper and Typo have limitations such as, the site would have to be single-author. If not, the site has to be bent a little to get it to play nice with multiple authors. Pure Typo has none of those limitations. Of course, some things aren't even close to being as beautiful as Jasper, but hey, choices and trade-offs.
Pure Typo theme includes
- Author page (New 07.02.2015)
- Tag page(s) (New 07.02.2015)
- 404 page (New 07.02.2015)
- Toggleable sliding sidebar (New 07.02.2015)
- Related posts view (New 30.10.2015)
- Tag description(s) (New 30.10.2015)
- Code Syntax Highlight (New 24.11.2015)
- Rss updated to Jekyll 3.0 (New 06.04.2016)
- Google Analytics tracking
- Author's profile with picture
- Disqus comments (not Ghost standard)
How to use it
Important: For security reasons, Github doesn't allow plugins (under _plugins/) when deploying with Github Pages. This means:
1) that we need to generate your site locally (more details below) and push the resulting HTML to a Github repository;
2) built the site with travis-ci (with goodies from jekyll-travis) automatically pushing the generated _site/ files to your gh-pages branch. This later approach is the one I am currently using to generate the live demo.
For option 1) simply clone this repository (master branch), and then run
jekyll serve inside the directory. Upload the resulting _site/ contents to your repository (master branch if uploading as your personal page (username.github.io) or gh-pages branch if uploading as a project page (as for the demo).
For option 2) you will need to set up travis-ci for your personal fork. Briefly all you need then is to change your details in _config.yml so that you can push to your github repo. You will also need to generate a secure key to add to your .travis.yml (you can find more info on how to do it in that file). Also make sure you read the documentation from jekyll-travis. This approach has clear advantages in that you simply push changes to your files and all the html files are generated for you. Also you get to know if everything is still fine with your site builds. Don't hesitate to contact me if you still have any issues (see below about issue tracking).
As discussed here, in order to properly generate author pages you need to rename the field categories in the front matter of every post to match that of your username as defined in the _config.yml file. This probably means that with a bit of hacking you could in principle generate multiple author blogs. Check this link for more on working with multiple authors...
Issues and contributing
This install builds well with Ruby v2.1.1 and Jekyll v3.0.0. If you run into any problems please log them on the issue tracker.
Feel free pull-request your patches and fixes.
Many thanks to Fábio Madeira the Ghost team for all the design work that allows to make this clone possible. Also many thanks to all contributors, that help keeping the Jasper project alive and updated.
Copyright & License
Copyright (C) 2015 - Released under the MIT License.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.