To start you own blog, simply git clone the repository on github.
git clone https://github.com/drvy/minimal-block.git
Once cloned, edit the
_config.yml file at the root of the repository.
To add your own posts, add a file to the _posts directory. The file name has to follow the following structure.
The post doesn't have to be writen in markdown but it's recomended. Notice that the URL of the post will contain the “Hello-world” part so the title of the file must be URL friendly.
Things to change in
This file contains the configuration of your blog. By default, it looks like this:
# General name: Minimal-Block description: "Minimalistic, friendly, responsive." url: http://localhost:4000 markdown: redcarpet highlighter: pygments paginate: 5 permalink: /:title # Social share and comments. disqus-id: yourusername twitter: yourusername github: yourusername google: +yourusername # RSS feed rss-feed-limit: 10 rss-show-full: "yes"
You will need to change
github. All others are optional. Here is what the variables mean.
|name||The name of your jekyll site. The title.|
|description||Basic description. Sub-title.|
|url||Where will be the jekyll site. The main URL without the endind / (slash).|
|markdown||The preffered markdown parser to use.|
|highlighter||The syntax-highlighter to use. If not set, `highlights.css` will not be included.|
|paginate||How much posts to show per page.|
|permalink||The friendly urls of the post. `none` is the jekyll default.|
|disqus-id||The disqus ID. If not set, comments will not be shown.|
|Your twitter username (used while sharing).|
|github||Your github username.|
|Youre google+ username.|
|rss-feed-limit||How much entries to display in the feed.xml (rss).|
|rss-show-full||The show the full post or to put only the excerpt (yes | no).|
Checkout the Jekyllrb wiki for documentation on writing posts. This theme makes use of static sharing buttons and they use a few tags that you should include in your posts. An example of a post header:
--- layout: post title: "minimal-block - A minimalistic responsive Jekyll theme" date: 2015-01-25 00:00:00 categories: jekyll, themes tags: jekyll, theme, minimal shortUrl: http://goo.gl/JhfZT9 ---
Most of these variables are just the default ones but the last two (
shortUrl) are used by the theme when sharing via the social buttons in the end of every post.
tags will be converted into hashtags when sharing on Twitter and if you supply a
shortUrl, it will be used instead of the full url. This is useful if you are using goo.gl since they provide statistics for each short link and that way you can see how many people are sharing your post.
Pages and other files.
Each page has its own directory in the root folder of the theme. In each directory there is an index.html representing the contents of the page. Take a look at the default ones (about and contact) to see the structure.
Another file to know about is the
footer.html as it has the copyright notice and credits. This file is located in the
_includes folder. You can remove the credits if you want but I would love you if you give me some credit in the HTML source.
404 file is located in the root folder and it contains the exactly same structure as a page.
The MIT License (MIT)
Copyright (c) 2015 Dragomir V Yordanov 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.