-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Sass files not available by default #752
Comments
I am new to minima and I am having this problem as well - any short term workaround? |
The README instructions you're referring to is for the unreleased Minima 3.0. To view instructions for v2.5.x, change the repository branch / tree accordingly. |
This issue has been automatically marked as stale because it has not been commented on for at least two months. The resources of the Jekyll team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial. This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions. |
The section Customizing templates instructs to simply create an
assets/css/style.scss
file and, optionally,_sass/minima/custom-styles.scss
&custom-variables.scss
. However, the build fails without the remaining Sass files since they are referenced instyle.scss
.Example 1
After adding
assets/css/style.scss
and populating it with the following in accordance with Customizing templates:The build failed with the following error:
Log file: Example 1.txt
Example 2
After adding the skins to
_sass/minima/skins
, the build still failed with the following error:Log file: Example 2.txt
Of course, manually adding the Sass source files resolves this issue, but this overrides the "defaults" and the files should be available without having to manually include them, so that the site stays "in sync with upstream changes released in future versions".
The text was updated successfully, but these errors were encountered: