Skip to content
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

Exclude css from generated css (for a style guide page) #383

Closed
BurningDog opened this issue Nov 17, 2015 · 2 comments
Closed

Exclude css from generated css (for a style guide page) #383

BurningDog opened this issue Nov 17, 2015 · 2 comments

Comments

@BurningDog
Copy link

I've added a styleguide.html to my site, and have some css (in app/css/styleguide.scss) which I'd like to manually include in the style guide html (with a <link>) but not in my normal site's html. How can I exclude that scss file from being included in the generated app.css? I'm using node-sass, and have a main.scss file which explicitly imports each scss file I need for the generated app.css

My config/files.js sass config looks like:

    sass: {
      main: "app/css/main.{sass,scss}",
      compass: true
    }
@searls
Copy link
Member

searls commented Nov 17, 2015

I don't have a great answer to this off the top of my head (I see what you're saying but I'm struggling to visualize it). Anyone else have a moment to respond more intelligently?

@jasonkarns
Copy link
Member

Not a very helpful answer, but a thought experiment. Since a styleguide or
pattern library is generally meant to be a standalone page(s) with base css
(and even JS), would it make more sense if the styleguide were its own
lineman app? I realize this introduces its own complexities, so I don't
mean to dismiss the underlying issue with a sweeping "separate app"
response. But might be worth it. I think it would carry other benefits as
well, like the ability to make iterations on the guide/core styles
separately from the main app(s).

On Tue, Nov 17, 2015 at 10:52 AM, Justin Searls notifications@github.com
wrote:

I don't have a great answer to this off the top of my head (I see what
you're saying but I'm struggling to visualize it). Anyone else have a
moment to respond more intelligently?


Reply to this email directly or view it on GitHub
#383 (comment).

@davemo davemo closed this as completed Feb 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants