Skip to content

Jekyll Multisites allows granular control over sharing codebases, plugins, files & assets across multiple Jekyll builds.

Notifications You must be signed in to change notification settings

Designaroni/jekyll-multisites

Folders and files

NameName
Last commit message
Last commit date

Latest commit

dfbc4cf · Feb 7, 2017

History

5 Commits
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017
Feb 7, 2017

Repository files navigation

jekyll-multisites

Jekyll Multisites allows granular control over sharing codebases, plugins, files & assets across multiple Jekyll builds.

Purpose

The purpose of jekyll-multisites is to demonstrate the capabilities of Jekyll as a tool for sharing assets across multiple builds. HTML, CSS, JavaScript, image assets, plugins & gems can be shared as the source files for a system of websites.

Usage

To spin up the example sites first download the git repository: $ git clone git@github.com:Designaroni/jekyll-multisites.git

Running the sites individually

To build & serve either site run one of the following commands from the repository

$ bundle exec jekyll serve --config _config_site_one.yml
$ bundle exec jekyll serve --config _config_site_two.yml

Inspiration

Inspiration for this project came out of a need to share modular web components across a system of sites, Branding assets, shared call to action banners, modules of custom html, css & javscript & shared vendor assets.

Default Application Structure

... I'll get there don't worry, in the mean time shoot me a message on twitter @designaroni

About

Jekyll Multisites allows granular control over sharing codebases, plugins, files & assets across multiple Jekyll builds.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published