Bootstrap/docs/_plugins/bridge.rb

require 'yaml'

module Bridge
  class Generator < Jekyll::Generator
    def generate(site)
      path = File.join(site.source, "../grunt/configBridge.json")
      site.data["configBridge"] = YAML.load_file(path)
    end
  end
end
Use a Jekyll plugin instead of the `copy:configBridge` grunt task 2014-11-05 18:35:13 +01:00			`require 'yaml'`

			`module Bridge`
			`class Generator < Jekyll::Generator`
			`def generate(site)`
$David\ Beitey$ Specify configBridge as relative path to source This adjusts the load path for the ``configBridge.json`` file from one that's relative to the user running the command (eg ``jekyll serve``), to one that's relative to the ``source`` configuration setting for Jekyll. The result is that the user can now have a (customised) ``_config.yml`` for Jekyll anywhere on her filesystem and point to Bootstrap's ``docs`` directory to use as the ``source``. Previously, in order to customise it, the original ``_config.yml`` needed to be modified inside (a forked) Bootstrap, and the ``jekyll`` command could only be run at the root of the Bootstrap package as the original file path to ``configBridge.json`` was only valid there. The existing behaviour is not affected. 2015-09-08 14:36:00 +10:00			`path = File.join(site.source, "../grunt/configBridge.json")`
			`site.data["configBridge"] = YAML.load_file(path)`
Use a Jekyll plugin instead of the `copy:configBridge` grunt task 2014-11-05 18:35:13 +01:00			`end`
			`end`
Add missing end of file newlines. [ci skip] 2015-09-08 08:16:07 +03:00			`end`