W3C home > Mailing lists > Public > public-webplatform@w3.org > July 2013

Re: CSS edits workflow

From: Renoir B. <renoirb@gmail.com>
Date: Tue, 16 Jul 2013 14:16:51 -0400
Message-ID: <CAEWz3DCp9SEv922X21cb8hhYDh03kZ3athM7NvMSjK3bXSZ2fw@mail.gmail.com>
To: WebPlatform Community <public-webplatform@w3.org>
I have an other suggestion.

There is also Cloud9 IDE <https://c9.io/> that could be used as an online
editor.

It would require a project in github representing all assets, and static
html views, views could be shortened using some roughdraft.js attributes.

If you tell me a typical view or two, I can create a proof of concept of
the idea.

Regards.

*Renoir Boulanger*
Frontend & software developer

*renoir*boulanger.com/#is <https://renoirboulanger.com/#is> <-- vient
d'Ítre refait!
~


On 16 July 2013 01:12, Renoir B. <renoirb@gmail.com> wrote:

> Oops, I effectively forgot to see the CC to the list :/
>
> My suggestion would be to create:
>
>    1. One static HTML document per application and per view from each of
>    them
>    2. Editor capability within the browser
>    3. Find a way to write back modifications to the project file
>
> My questions:
>
>    1. Do the site has any Preprocessor documents?
>    2. Is there a lot of CSS files per application?
>    3. Is there a way to build the CSS files from preprocessors (if there
>    is any?)
>    4. Do dabblet can have more than one document? or Do you see a way to
>
> Solution paths:
>
>    1. Use jsfiddle (it has preprocessor capabilities)
>    2. Use dabblet+less
>    3. Create grunt tasks to concatenate, minify, lint (i.e. recess),
>     files from a gist (or more) (dabblet ?)
>
> This is things I have on top of my head for now.
>
> Hope it is helpful
>
>
> *Renoir Boulanger*
> Frontend & software developer
>
> *renoir*boulanger.com/#is <https://renoirboulanger.com/#is> <-- vient
> d'Ítre refait!
> ~
>
>>
>>
Received on Tuesday, 16 July 2013 21:27:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:52 UTC