Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

support public_root configuration to help organization static files #474

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
4 participants

The idea is that any file or folder inside of the specific public_root folder will get copied to the root of the generated site. I wasn't sure how files with yaml headers should be treated...I decided to not apply this logic to them. Can't decide which way is more consistent with what a user would expect

Instead of having your site look like:

index.html
resume.pdf
assets
images
unicorns.jpg
assets
css
main.css

You can put all the static and non-yaml files you want under the public_root => '/public':

index.html
public
resume.pdf
assets
images
unicorns.jpg
assets
css
main.css

Karl Seguin added some commits Jan 20, 2012

Karl Seguin added support for public_root config which copies files/folders from …
…the specific path into the root of the site
f42ea52
Karl Seguin fixed documentation and removed unecessary site being passed to stati…
…c_file constructor
4fa4ecf
Contributor

mojombo commented Jan 21, 2012

I'm not sure I understand why this is useful. You can already put static files in any directory structure you want and they'll be copied over without modification. Why would you want a bunch of files copied from a subdirectory into the root?

Basically: to preserve existing links while keeping my root clean.

There are a bunch of links which already point to http://openmymind.net/mongodb.pdf (Google, ...) I certainly don't want to break those links, but I'd also like my jekyll project to be tidier than having 20 files in the root.

I imagine a lot of people who migrate from rails (which kinda does the same thing with its public folder), who didn't have the foresight to put things in a subfolder (/public/files) would have the same mess.

Contributor

mojombo commented Jan 28, 2012

Is this really a big enough problem to warrant complicating the docs and code? I'd wager the number of people migrating to Jekyll from Rails would be rather low.

Your call (obviously). I won't cry more than once if you reject it!

Owner

parkr commented Feb 7, 2013

Closing for stagnancy and because @mojombo didn't seem too enthusiastic about the idea.

@parkr parkr closed this Feb 7, 2013

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.