New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amend docs about assets #2067

Merged
merged 2 commits into from Feb 24, 2014

Conversation

Projects
None yet
4 participants
@troyswanson
Member

troyswanson commented Feb 18, 2014

Seeks to make more clear the behavior of asset files, specifically around the output destination. I'm actually not happy with the wording that I came up with, but I think it's worth it to have something like this in here.

Ref #2063

@mattr-

View changes

site/docs/assets.md Outdated
@@ -19,6 +19,11 @@ or `.coffee`) and start the file with two lines of triple dashes, like this:
font-size: 1.2em
{% endhighlight %}
Jekyll treats these files the same a regular page, in that the output file
will be placed in the same directory that it came from. For instance, if you
have a file named `/css/styles.scss`, Jekyll will process it and put it in

This comment has been minimized.

@mattr-

mattr- Feb 20, 2014

Member

have a file named /css/styles.scss

might want to add "in your site's source folder" just to remove the ambiguity.

@mattr-

This comment has been minimized.

Member

mattr- commented Feb 20, 2014

one minor detail and then we're good to go.

@parkr parkr added this to the 2.0 milestone Feb 20, 2014

@parkr parkr added the Documentation label Feb 20, 2014

@troyswanson

This comment has been minimized.

Member

troyswanson commented Feb 20, 2014

Thanks for the suggestion, @mattr-. Pushed!

@parkr parkr merged commit 8282424 into jekyll:master Feb 24, 2014

1 check failed

default The Travis CI build could not complete due to an error
Details

parkr added a commit that referenced this pull request Feb 24, 2014

@jekyll jekyll 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.