jekyll_post_files 1.0.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: e186f35615449ee1e71d05eedd8ca90a4d44b446
+  data.tar.gz: 3b9bb202ea17ce86cf6a0602308dc7dd7ef7027d
+SHA512:
+  metadata.gz: 7895c34af3d092028e50282bd65724c134852e266fcf382d53776857611910497637aa58880cf77c21d50d0cf941815ed301b0008d0a9acf568b1e8f43f803b9
+  data.tar.gz: 4411b830897828d25758788bba82588da11e5d97079c94a367140ea45da93ce5fee135132caf99915c77d5ebe379f2afb139a4f3af1018673f1b55123c86b59e

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in jekyll-post-files.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016 Nicolas Hoizey
+
+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.

data/README.md

@@ -0,0 +1,195 @@
+# jekyll_post_files
+
+[![Gem Version](https://badge.fury.io/rb/jekyll_post_files.svg)](https://badge.fury.io/rb/jekyll_post_files)
+
+## Easing the management of images (and other files) attached to Markdown posts
+
+### The pain of Jekyll's recommended posts assets management
+
+Jekyll's natural way to deal with static files attached to posts, like images or PDFs, is to put them all in a global `assets/` (or `downloads/`) folder at the site root. Read "[Including images and resources](https://jekyllrb.com/docs/posts/#including-images-and-resources)" in Jekyll's documentation.
+
+You can of course put files in subfolders of `assets/`, but it will be really cumbersome to manage posts' Markdown files in `_posts/` or a subfolder, and images elsewhere, and then use the good hierarchy in all Markdown image tags.
+
+Imagine you have these files:
+
+```
+_posts/
+  2016-06/
+    2016-06-09-so-long-cloudflare-and-thanks-for-all-the-fissh.md
+…
+assets/
+  2016-06-09-cloudflare/
+    cloudflare-architecture.png
+    performance-report-sample.pdf
+```
+
+To use the image and PDF files in the post's Markdown, you will have to write this:
+
+```markdown
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
+tempor incididunt ut labore et dolore magna aliqua.
+
+![Cloudflare architecture](/assets/2016-06-09-cloudflare/cloudflare-architecture.png)
+
+Ut enim ad minim veniam,
+quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
+consequat.
+
+Here is [an example of performance report](/assets/2016-06-09-cloudflare/performance-report-sample.pdf).
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
+tempor incididunt ut labore et dolore magna aliqua.
+```
+
+Painful to write.
+
+Imagine you want to change the post's publication date, or one of the file names?
+
+Painful to update.
+
+What if you want to put new WIP Markdown files in `_drafts/`, and the attached assets somewhere in a way they won't be copied to the destination `_site/` folder next time you build the site? You can't put the files in the `assets/` folder, so when you will publish the draft, you will have to change the assets location in the Markdown file.
+
+Painful, and prone to errors.
+
+And what about previewing the content while editing? If you use an editor like [MacDown](http://macdown.uranusjr.com/) with live preview, how will it find the actual path to the images? What means `/assets/…` for the editor?
+
+Painful to preview.
+
+### There must be another way
+
+What if instead, you could have the files stored like that:
+
+```
+_posts/
+  2016-06-09-cloudflare/
+    2016-06-09-so-long-cloudflare-and-thanks-for-all-the-fissh.md
+    cloudflare-architecture.png
+    performance-report-sample.pdf
+```
+
+And if you could write your Markdown like this:
+
+```markdown
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
+tempor incididunt ut labore et dolore magna aliqua.
+
+![Cloudflare architecture](cloudflare-architecture.png)
+
+Ut enim ad minim veniam,
+quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
+consequat.
+
+Here is [an example of performance report](performance-report-sample.pdf).
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod
+tempor incididunt ut labore et dolore magna aliqua.
+```
+
+Much easier!
+
+- Easy to store, everything is in one single folder.
+- Easy to write, no path to add to file links
+- Easy to update
+- Easy to move from `_drafts/` to `_posts/`, without anything to change in the Mardown content
+- Easy to edit in any editor with live preview
+
+### Not every assets need this
+
+[Some Jekyll users will try to convince you](http://stackoverflow.com/a/10366173/717195) it's a bad idea, because it means the asset is tightly linked to the post.
+
+In my own experience, 95% of assets, at least, are used in one single post. And this is pretty common to find such requests from users of other static generators, like [Hugo](https://github.com/spf13/hugo/issues/147) ([fixed in May 2015](https://github.com/spf13/hugo/issues/147#issuecomment-104067783)), [Nikola](https://github.com/getnikola/nikola/issues/2266) ([already there, but not obvious or user friendly](https://github.com/getnikola/nikola/issues/2266#issuecomment-189211387)), [Octopress](http://stackoverflow.com/questions/17052468/insert-local-image-into-a-blog-post-with-octopress), etc.
+
+But it's true this might not be ideal for all assets (the remaining 5%), so you can of course continue using full assets paths with `/assets/…` to have a few assets shared by several posts.
+
+## How does it work?
+
+This plugin takes any file that is in posts folders, and copy them to the folder in which the post HTML page will be created.
+
+Let's say you have these files:
+
+```
+_posts/
+  2016-06-09-cloudflare/
+    2016-06-09-so-long-cloudflare-and-thanks-for-all-the-fissh.md
+    cloudflare-architecture.png
+    performance-report-sample.pdf
+```
+
+And your Jekyll settings for permalinks are these:
+
+```yaml
+# Permalinks
+permalink: /:year/:month/:day/:title/
+```
+
+Jekyll with this plugin will generate the site content like this:
+
+```
+2016/
+  06/
+    09/
+      so-long-cloudflare-and-thanks-for-all-the-fissh/
+        index.html
+        cloudflare-logo.png
+        performance-report-sample.pdf
+```
+
+If you change your Jekyll settings for permalinks like these:
+
+```yaml
+# Permalinks
+permalink: /:year/:month/:day/:title.html
+```
+
+Jekyll with this plugin will generate the site content like this:
+
+```
+2016/
+  06/
+    09/
+      so-long-cloudflare-and-thanks-for-all-the-fissh.html
+      cloudflare-logo.png
+      performance-report-sample.pdf
+```
+
+Handy, isn't it?
+
+## Installation
+
+Add this line to your `Gemfile`:
+
+```ruby
+gem 'jekyll_post_files'
+```
+
+Execute this:
+
+```shell
+$ bundle
+```
+
+And add this line to your `_config.yml`:
+
+```yaml
+gems:
+  - jekyll_post_files
+```
+
+## Usage
+
+You don't have anything to do.
+
+Just put the images (and PDFs, etc.) in the same folder as your Markdown files, and use the standard Markdown image syntax, without any path.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at [https://github.com/nhoizey/jekyll-post-files](https://github.com/nhoizey/jekyll_post_files)
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+
+## Thanks
+
+Inspired by [this old Gist](https://gist.github.com/kevinoid/3131752) by [@kevinoid](https://github.com/kevinoid/).
+

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "jekyll_post_files"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/jekyll_post_files.gemspec

@@ -0,0 +1,22 @@
+# coding: utf-8
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'jekyll_post_files/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = "jekyll_post_files"
+  spec.version       = JekyllPostFiles::VERSION
+  spec.authors       = ["Nicolas Hoizey"]
+  spec.email         = ["nicolas@hoizey.com"]
+
+  spec.summary       = %q{In Jekyll, copy static files from the _posts to the _site folder.}
+  spec.description   = %q{When using Jekyll, this plugin copies all static files that are in the source _posts subfolder of a Markdown post to the destination subfolder in _site.}
+  spec.homepage      = "https://github.com/nhoizey/jekyll_post_files"
+  spec.license       = "MIT"
+
+  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.12"
+  spec.add_development_dependency "rake", "~> 10.0"
+end

data/lib/jekyll_post_files.rb

@@ -0,0 +1,60 @@
+require "jekyll_post_files/version"
+require "jekyll"
+
+module Jekyll
+
+  class PostFile < StaticFile
+
+    # Initialize a new PostFile.
+    #
+    # site - The Site.
+    # base - The String path to the <source>.
+    # dir - The String path of the source directory of the file (rel <source>).
+    # name - The String filename of the file.
+    def initialize(site, base, dir, name, dest)
+      super(site, base, dir, name)
+      @name = name
+      @dest = dest
+    end
+
+    # Obtain destination path.
+    #
+    # dest - The String path to the destination dir.
+    #
+    # Returns destination file path.
+    def destination(dest)
+      File.join(@dest, @name)
+    end
+  end
+
+  class PostFileGenerator < Generator
+
+    # Copy the files from post's folder.
+    #
+    # post - A Post which may have associated content.
+    def copy_post_files(post)
+
+      postpath = post.path
+      postdir = File.dirname(postpath)
+      destdir = File.dirname(post.destination(""))
+
+      site = post.site
+      sitesrcdir = site.source
+      contents = Dir.glob(File.join(postdir, '**', '*')) do |filepath|
+        if filepath != postpath
+          filedir, filename = File.split(filepath[sitesrcdir.length..-1])
+          site.static_files <<
+            PostFile.new(site, sitesrcdir, filedir, filename, destdir)
+        end
+      end
+    end
+
+    # Generate content by copying files associated with each post.
+    def generate(site)
+      site.posts.docs.each do |post|
+        copy_post_files(post)
+      end
+    end
+  end
+
+end

data/lib/jekyll_post_files/version.rb

@@ -0,0 +1,3 @@
+module JekyllPostFiles
+  VERSION = "1.0.5"
+end

metadata

@@ -0,0 +1,83 @@
+--- !ruby/object:Gem::Specification
+name: jekyll_post_files
+version: !ruby/object:Gem::Version
+  version: 1.0.5
+platform: ruby
+authors:
+- Nicolas Hoizey
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2016-06-29 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.12'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.12'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+description: When using Jekyll, this plugin copies all static files that are in the
+  source _posts subfolder of a Markdown post to the destination subfolder in _site.
+email:
+- nicolas@hoizey.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- jekyll_post_files.gemspec
+- lib/jekyll_post_files.rb
+- lib/jekyll_post_files/version.rb
+homepage: https://github.com/nhoizey/jekyll_post_files
+licenses:
+- MIT
+metadata: {}
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.6.4
+signing_key: 
+specification_version: 4
+summary: In Jekyll, copy static files from the _posts to the _site folder.
+test_files: []