Open sugarenia opened 8 years ago
There's not an "official" way to do this, my initial thought was to use multiple config files for generating the different style guides. You might be able to do some trickery in the header erb for including the correct css but that seems a little gross. I would need to think about it more to see if it made sense to have some sort of configuration that can do this.
@jdcantrell Yes, multiple configs were our first idea as well, but we wanted to keep it as contained as possible, since it's essentially the same product.
Thanks for considering it, do let us know :)
Is there a clean, "official" way to have multiple styleguides on the same codebase?
Something like:
http://domain.com/public/styleguide
an index page with an intro and links to different sections, e.g. /backend, /marketing, /applicationhttp://domain.com/public/styleguide/backend
the backend index, showing only widgets from theapp/assets/stylesheets/backend
folder (CSS include is ONLYapp/assets/stylesheets/backend.scss
http://domain.com/public/styleguide/marketing
the marketing index, showing only widgets from theapp/assets/stylesheets/marketing folder
(CSS include is ONLYapp/assets/stylesheets/marketing.scss
)etc.
Any ideas?