Support for using SASS

It would great to support SASS and SCSS for all CSS. I think it's possible that this could be done in a unobtrusive way - such as providing this option as a filter for the textarea within a page edit view.

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    Christopher Haupt

    Good idea. We've played with different kinds of filtering in early versions of Webvanta. While those experiments are no longer in the product, it is doable if there is demand for such a feature again. The biggest challenge isn't the filtering so much, but making the UI to control it at a particular granularity simple.

    For instance, once area it might be applied would be on a snippet or page (or page region) level, so you'd want certain selections based on type of the item. Another might be through WebvantaScript tags that provide a filtering feature for a particular area.

    With something like SASS, I'd imagine you'd want that on for the entire region, page, or snippet, though. Would it be interesting if it was a global setting for CSS pages/files or would be necessary to set on a file by file basis?

  • 0
    Avatar
    Paul du Coudray

    "I'd imagine you'd want that on for the entire region, page, or snippet, though"

    Yes, I don't see the direct need to change filtering for an area within a page, since that area could be extracted into a new stylesheet if desired.

    "Would it be interesting if it was a global setting for CSS pages/files or would be necessary to set on a file by file basis"

    Personally, I would use a global setting if there were one, but I think it would suffice to just have it page by page... maybe even dictated by something as simple as page name extension (.css or .sass), since it's possible that someone would want to port an existing web project to webvanta and then override with future .sass stylesheets. Or maybe they've worked out a print.css or buttons.css and don't feel like converting it yet.

    As far as syntax goes, I prefer sass over scss, but I would think that because designers could switch to scss without converting any existing stylesheets that some designers would be happy to have immediate access to use of variables. This might be interesting to introduce someday with the additional SmartThemes features because of what a designer can do to setup a template that allows for making quick global updates during the design phase.

Please sign in to leave a comment.
Powered by Zendesk