Streamline your writing in Jekyll with some commands.
Add this line to your application’s Gemfile:
gem 'jekyll-compose', group: [:jekyll_plugins]
And then execute:
After you have installed (see above), run
bundle exec jekyll help and you should see:
Listed in help you will see new commands available to you:
draft # Creates a new draft post with the given NAME
post # Creates a new post with the given NAME
publish # Moves a draft into the _posts directory and sets the date
unpublish # Moves a post back into the _drafts directory
page # Creates a new page with the given NAME
Create your new page using:
$ bundle exec jekyll page "My New Page"
Create your new post using:
$ bundle exec jekyll post "My New Post"
Create your new draft using:
$ bundle exec jekyll draft "My new draft"
Publish your draft using:
$ bundle exec jekyll publish _drafts/my-new-draft.md
# or specify a specific date on which to publish it
$ bundle exec jekyll publish _drafts/my-new-draft.md --date 2014-01-24
Unpublish your post using:
$ bundle exec jekyll unpublish _posts/2014-01-24-my-new-draft.md
To customize the default plugin configuration edit the
jekyll_compose section within your jekyll config file.
auto-open new drafts or posts in your editor
and make sure that you have
JEKYLL_EDITOR environment variable set.
For instance if you wish to open newly created Jekyll posts and drafts in Atom editor you can add the following line in your shell configuration:
The latter one will override default
Set default front matter for drafts and posts
If you wish to add default front matter to newly created posts or drafts, you can specify as many as you want under
post_default_front_matterconfig keys, for instance:
This will also auto add:
- The creation timestamp under the
- The title attribute under the
- Fork it ( http://github.com/jekyll/jekyll-compose/fork )
- Create your feature branch (
git checkout -b my-new-feature)
- Run the specs and our linter (
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request
Submitting a Pull Request based on an existing proposal
When submitting a pull request that uses code from an unmerged pull request, please be aware of the following:
- Changes proposed in the older pull request is still the original author’s property. Moving forward from where they left it
means that you’re a
- GitHub allows attributing credit to multiple authors However, pull requests in this project are automatically squashed and then merged onto the base branch. So, only authors and co-authors of the opening commit gets credit once the pull request gets merged.
- If the original pull request contained multiple commits, you may squash them into a single commit but ensure that you list any additional authors (and yourselves) as co-authors of that commit.
- Use appropriate keywords in your pull request post to link to the existing pull request or issue-ticket so that they’re automatically closed when your pull request gets merged.