-
Notifications
You must be signed in to change notification settings - Fork 0
Home
The public web site is a jekyll blog stored in the thelastpickle.github.io git hub project.
Information about creating content is provided below, you may also want to know about Templates.
The jekyll website has great documentation.
Create drafts in the _/drafts folder using the name format the-post-title.md when using markdown.
Drafts are not included when the site is built, to include them run jekyll serve --drafts or jekyll build --drafts.
See Working With Drafts for more information.
Blog posts are created in the _/posts folder using the name form YEAR-MONTH-DAY-title.md when using markdown. For example 2011-12-31-new-years-eve-is-awesome.md. Note: The format of the name is important as jekyll extracts the post date from the name.
All files that have YAML Front Matter will be parsed by the engine. Typically we want to include the following variables at a minimum:
---
layout: post
title: "Deletes and Tombstones"
category: Cassandra
tags: list, of, tags
---
Where:
-
layouttells jekyll which template in the_layoutsfolder to use. -
titleis the title of the page and made available as thepage.titlevariable in the tempalte. -
categorytells the site where the page should exist, see below. -
tagsis a list of tags, we don't use them for much yet but please tag Cassandra centric tags with "cassandra".
See Writing Posts for more information.
We use categories to drive the site layout:
-
blogcategory pages are placed in/blog/in the site. -
speakingcategory pages are placed in/speaking/in the site and included in the Speaking index.
All posts in _posts\ in the repo are included in the blog index.
Place a markdown file in the root directory, or any top level directory that does not start with _. It will be processed by the jekyll engine if the file contains the YAML Front Matter. We will normally want to use a different layout for static pages.
Alternatively a static HTML file may be placed in the same locations.
We have two workflows.
Use the Collaborative Workflow when you have a post that is being worked on for a long time potentially by more than one person.
- Create the post in
_drafts/(above) and merge into the master branch, you can do this without getting someone else to complete the pull request. - Let others know.
- Accept pull requests into the draft post.
- Move the post into
_posts/and set the date in the file name (above)
The collaborative workflow can be used to stub out ideas for a post.
Use the quick workflow when you have written a complete post and are just looking for edits.
- Create the posts in the
_posts/folder in your own fork / branch. - Submit a pull request to the
masterbranch. - Make edits as post of the merge process.
- Merge the pull request in the
masterbranch, but sure to check the date in the file name.