Best practice for managing CSS files?

Hi,

We're trying to get a site rolling with Bricolage, and we
are stumped at
a seemingly easy to solve problem: namely, how do you mange
CSS files
under bricolage?

We naively thought that you could simply use a CSS story
type, but the
URI scheme got to be a problem: for example, we didn't want
CSS files
that looked like /css/foo/index.css or /css/foo/foo.css. But
if you
don't include the slug in the URI category, Bricolage thinks
that
difference css files under the same category are the same --
for
example, /css/main.css and /css/foo.css are considered to be
the same thing.

I notice that Bricolage relies on a
everything-is-under-a-directory
approach, but what *is* the best practice here? Do people
simply not use
bricolage to manage CSS?

Thanks,
--d

Daisuke Maki <daisukeendeworks.jp> writes:
> We're trying to get a site rolling with Bricolage, and
we are
> stumped at a seemingly easy to solve problem: namely,
how do you
> mange CSS files under bricolage?
>
> We naively thought that you could simply use a CSS
story type, but
> the URI scheme got to be a problem: for example, we
didn't want CSS
> files that looked like /css/foo/index.css or
/css/foo/foo.css. But
> if you don't include the slug in the URI category,
Bricolage thinks
> that difference css files under the same category are
the same --
> for example, /css/main.css and /css/foo.css are
considered to be the
> same thing.
>
> I notice that Bricolage relies on a
everything-is-under-a-directory
> approach, but what *is* the best practice here? Do
people simply not
> use bricolage to manage CSS?

We just manage them as Media files.
Similar to images and javascript files.

A downside with Media is, you cannot easily see the diffs
from version
to version.

Steffen
-- 
Steffen Schwigon <schwigonwebit.de>
Dresden Perl Mongers <http://dresden-pm.org/>

Deutscher Perl-Workshop <http://www.perl-work
shop.de/>

We manage CSS files as 'media' instead of stories. This
allows you to  
edit the CSS files using your favourite text editor and
makes it easy  
to manage in Bricolage by having the file names the way you
want.

-a




On 17 Dec 2007, at 10:29, Daisuke Maki wrote:

> Hi,
>
> We're trying to get a site rolling with Bricolage, and
we are  
> stumped at
> a seemingly easy to solve problem: namely, how do you
mange CSS files
> under bricolage?
>
> We naively thought that you could simply use a CSS
story type, but the
> URI scheme got to be a problem: for example, we didn't
want CSS files
> that looked like /css/foo/index.css or
/css/foo/foo.css. But if you
> don't include the slug in the URI category, Bricolage
thinks that
> difference css files under the same category are the
same -- for
> example, /css/main.css and /css/foo.css are considered
to be the  
> same thing.
>
> I notice that Bricolage relies on a
everything-is-under-a-directory
> approach, but what *is* the best practice here? Do
people simply  
> not use
> bricolage to manage CSS?
>
> Thanks,
> --d
>

---------------------------------------------

Adam Ma'anit
Co-Editor
New Internationalist

Visit the NI website: http://www.newint.org/

Support independent media by subscribing: http://www.newint.org/ 
subscribe/

Shop for Fair Trade and Organic goodies: http://shop.newint.org/

Listen to Radio New Internationalist: http://www.newint.org/ra
dio/

Geek out with our Digital Edition: http://www.exacted
itions.com/shop/ 
386/422/

Phone: +44 (0)1865 811400
Fax: +44 (0)1865 793152

New Internationalist is an independent not-for-profit
communications
cooperative. Our multi-award winning magazine, New
Internationalist,  
brings
to life the people, the ideas and the action in the fight
for global
justice.

New Internationalist Publications Ltd. is incorporated in
England  
under no.1005239.
Registered Office: New Internationalist, 55 Rectory Road,
Oxford,   
OX4 1BW, UK

Although, I recently tried out using *stories* for CSS files
(all  
text files actually -- Javascript, Perl/CGI, etc.) and must
say that  
I quite like it. It does seem to work best if each one
resides in its  
own folder (via a slug) -- e.g., /ui/css/default/index.css,
/ui/css/ 
print/index.css, etc. -- but that actually keep things quite
neatly  
organized. And, the benefit is that small changes are easily
 
accomplished via the Bricolage UI and -- unlike media -- you
can  
actually get useful diffs when comparing versions.

(Thanks to Bret Dawson for making me give that a go.)

On 17-Dec-07, at 7:14 AM, Adam Ma'anit wrote:

> We manage CSS files as 'media' instead of stories. This
allows you  
> to edit the CSS files using your favourite text editor
and makes it  
> easy to manage in Bricolage by having the file names
the way you want.
>
> -a
>
>
>
>
> On 17 Dec 2007, at 10:29, Daisuke Maki wrote:
>
>> Hi,
>>
>> We're trying to get a site rolling with Bricolage,
and we are  
>> stumped at
>> a seemingly easy to solve problem: namely, how do
you mange CSS files
>> under bricolage?
>>
>> We naively thought that you could simply use a CSS
story type, but  
>> the
>> URI scheme got to be a problem: for example, we
didn't want CSS files
>> that looked like /css/foo/index.css or
/css/foo/foo.css. But if you
>> don't include the slug in the URI category,
Bricolage thinks that
>> difference css files under the same category are
the same -- for
>> example, /css/main.css and /css/foo.css are
considered to be the  
>> same thing.
>>
>> I notice that Bricolage relies on a
everything-is-under-a-directory
>> approach, but what *is* the best practice here? Do
people simply  
>> not use
>> bricolage to manage CSS?
>>
>> Thanks,
>> --d
>>
>
> ---------------------------------------------
>
> Adam Ma'anit
> Co-Editor
> New Internationalist
>
> Visit the NI website: http://www.newint.org/
>
> Support independent media by subscribing: http://www.newint.org/ 
> subscribe/
>
> Shop for Fair Trade and Organic goodies: http://shop.newint.org/
>
> Listen to Radio New Internationalist: http://www.newint.org/ra
dio/
>
> Geek out with our Digital Edition: http://www.exactedition
s.com/ 
> shop/386/422/
>
> Phone: +44 (0)1865 811400
> Fax: +44 (0)1865 793152
>
> New Internationalist is an independent not-for-profit
communications
> cooperative. Our multi-award winning magazine, New  
> Internationalist, brings
> to life the people, the ideas and the action in the
fight for global
> justice.
>
> New Internationalist Publications Ltd. is incorporated
in England  
> under no.1005239.
> Registered Office: New Internationalist, 55 Rectory
Road, Oxford,   
> OX4 1BW, UK
>
>
>
>

--
Phillip Smith,
Simplifier of Technology
Community Bandwidth
http://www.community
bandwidth.ca

Yeah, I was going to pipe in and say the same thing. It's
actually nice
having everything in its own directory, and the diffs the
Bricolage UI
offers are extra-helpful with stylesheets.

(Also: never underestimate the power of symlinks to bridge
the
transition from foo.css to foo/index.css.)

Best,

Bret


On Mon, 2007-12-17 at 11:23 -0400, Phillip Smith wrote:
> Although, I recently tried out using *stories* for CSS
files (all  
> text files actually -- Javascript, Perl/CGI, etc.) and
must say that  
> I quite like it. It does seem to work best if each one
resides in its  
> own folder (via a slug) -- e.g.,
/ui/css/default/index.css, /ui/css/ 
> print/index.css, etc. -- but that actually keep things
quite neatly  
> organized. And, the benefit is that small changes are
easily  
> accomplished via the Bricolage UI and -- unlike media
-- you can  
> actually get useful diffs when comparing versions.
> 
> (Thanks to Bret Dawson for making me give that a go.)
> 
> On 17-Dec-07, at 7:14 AM, Adam Ma'anit wrote:
> 
> > We manage CSS files as 'media' instead of stories.
This allows you  
> > to edit the CSS files using your favourite text
editor and makes it  
> > easy to manage in Bricolage by having the file
names the way you want.
> >
> > -a
> >
> >
> >
> >
> > On 17 Dec 2007, at 10:29, Daisuke Maki wrote:
> >
> >> Hi,
> >>
> >> We're trying to get a site rolling with
Bricolage, and we are  
> >> stumped at
> >> a seemingly easy to solve problem: namely, how
do you mange CSS files
> >> under bricolage?
> >>
> >> We naively thought that you could simply use a
CSS story type, but  
> >> the
> >> URI scheme got to be a problem: for example,
we didn't want CSS files
> >> that looked like /css/foo/index.css or
/css/foo/foo.css. But if you
> >> don't include the slug in the URI category,
Bricolage thinks that
> >> difference css files under the same category
are the same -- for
> >> example, /css/main.css and /css/foo.css are
considered to be the  
> >> same thing.
> >>
> >> I notice that Bricolage relies on a
everything-is-under-a-directory
> >> approach, but what *is* the best practice
here? Do people simply  
> >> not use
> >> bricolage to manage CSS?
> >>
> >> Thanks,
> >> --d
> >>
> >
> > ---------------------------------------------
> >
> > Adam Ma'anit
> > Co-Editor
> > New Internationalist
> >
> > Visit the NI website: http://www.newint.org/
> >
> > Support independent media by subscribing: http://www.newint.org/ 
> > subscribe/
> >
> > Shop for Fair Trade and Organic goodies: http://shop.newint.org/
> >
> > Listen to Radio New Internationalist: http://www.newint.org/ra
dio/
> >
> > Geek out with our Digital Edition: http://www.exactedition
s.com/ 
> > shop/386/422/
> >
> > Phone: +44 (0)1865 811400
> > Fax: +44 (0)1865 793152
> >
> > New Internationalist is an independent
not-for-profit communications
> > cooperative. Our multi-award winning magazine, New
 
> > Internationalist, brings
> > to life the people, the ideas and the action in
the fight for global
> > justice.
> >
> > New Internationalist Publications Ltd. is
incorporated in England  
> > under no.1005239.
> > Registered Office: New Internationalist, 55
Rectory Road, Oxford,   
> > OX4 1BW, UK
> >
> >
> >
> >
> 
> --
> Phillip Smith,
> Simplifier of Technology
> Community Bandwidth
> http://www.community
bandwidth.ca
> 
> 
-- 
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bretpectopah.com
www.pectopah.com

We manage all our css as stories.  We simply use another
output  
channel to get the .css extension.

When we redesigned our site, we put the css throughout the
category  
structure, and our templates know to include references to
the proper  
css in the proper files at burn time.

-Matt


On Dec 17, 2007, at 11:24 AM, Bret Dawson wrote:

> Yeah, I was going to pipe in and say the same thing.
It's actually  
> nice
> having everything in its own directory, and the diffs
the Bricolage UI
> offers are extra-helpful with stylesheets.
>
> (Also: never underestimate the power of symlinks to
bridge the
> transition from foo.css to foo/index.css.)
>
> Best,
>
> Bret
>
>
> On Mon, 2007-12-17 at 11:23 -0400, Phillip Smith
wrote:
>> Although, I recently tried out using *stories* for
CSS files (all
>> text files actually -- Javascript, Perl/CGI, etc.)
and must say that
>> I quite like it. It does seem to work best if each
one resides in its
>> own folder (via a slug) -- e.g.,
/ui/css/default/index.css, /ui/css/
>> print/index.css, etc. -- but that actually keep
things quite neatly
>> organized. And, the benefit is that small changes
are easily
>> accomplished via the Bricolage UI and -- unlike
media -- you can
>> actually get useful diffs when comparing versions.
>>
>> (Thanks to Bret Dawson for making me give that a
go.)
>>
>> On 17-Dec-07, at 7:14 AM, Adam Ma'anit wrote:
>>
>>> We manage CSS files as 'media' instead of
stories. This allows you
>>> to edit the CSS files using your favourite text
editor and makes it
>>> easy to manage in Bricolage by having the file
names the way you  
>>> want.
>>>
>>> -a
>>>
>>>
>>>
>>>
>>> On 17 Dec 2007, at 10:29, Daisuke Maki wrote:
>>>
>>>> Hi,
>>>>
>>>> We're trying to get a site rolling with
Bricolage, and we are
>>>> stumped at
>>>> a seemingly easy to solve problem: namely,
how do you mange CSS  
>>>> files
>>>> under bricolage?
>>>>
>>>> We naively thought that you could simply
use a CSS story type, but
>>>> the
>>>> URI scheme got to be a problem: for
example, we didn't want CSS  
>>>> files
>>>> that looked like /css/foo/index.css or
/css/foo/foo.css. But if you
>>>> don't include the slug in the URI category,
Bricolage thinks that
>>>> difference css files under the same
category are the same -- for
>>>> example, /css/main.css and /css/foo.css are
considered to be the
>>>> same thing.
>>>>
>>>> I notice that Bricolage relies on a
everything-is-under-a-directory
>>>> approach, but what *is* the best practice
here? Do people simply
>>>> not use
>>>> bricolage to manage CSS?
>>>>
>>>> Thanks,
>>>> --d
>>>>
>>>
>>> ---------------------------------------------
>>>
>>> Adam Ma'anit
>>> Co-Editor
>>> New Internationalist
>>>
>>> Visit the NI website: http://www.newint.org/
>>>
>>> Support independent media by subscribing: http://www.newint.org/
>>> subscribe/
>>>
>>> Shop for Fair Trade and Organic goodies: http://shop.newint.org/
>>>
>>> Listen to Radio New Internationalist: http://www.newint.org/ra
dio/
>>>
>>> Geek out with our Digital Edition: http://www.exactedition
s.com/
>>> shop/386/422/
>>>
>>> Phone: +44 (0)1865 811400
>>> Fax: +44 (0)1865 793152
>>>
>>> New Internationalist is an independent
not-for-profit communications
>>> cooperative. Our multi-award winning magazine,
New
>>> Internationalist, brings
>>> to life the people, the ideas and the action in
the fight for global
>>> justice.
>>>
>>> New Internationalist Publications Ltd. is
incorporated in England
>>> under no.1005239.
>>> Registered Office: New Internationalist, 55
Rectory Road, Oxford,
>>> OX4 1BW, UK
>>>
>>>
>>>
>>>
>>
>> --
>> Phillip Smith,
>> Simplifier of Technology
>> Community Bandwidth
>> http://www.community
bandwidth.ca
>>
>>
> -- 
> Bret Dawson
> Producer
> Pectopah Productions Inc.
> (416) 895-7635
> bretpectopah.com
> www.pectopah.com
>

Is there any way to return just the stories in the root
category using  
the advanced search tool? Everything we try either returns
nothing or  
everything.

-Matt

On Dec 17, 2007, at 13:19, Matt Rolf wrote:

> Is there any way to return just the stories in the root
category  
> using the advanced search tool? Everything we try
either returns  
> nothing or everything.

No, there isn't. I normally search for the "Home
Page" story when I  
just want /index.html, myself. I don't usually have anything
else in  
the root.

Best,

David

We manage .css and other readable text files as stories of
"file" type.  We
made a special type of story with it's own output channel
that has a basic
root level (default) template... the template looks to the
story for a
custom textarea field called "text" and spits it
out.  This way we can open
up the story and edit the contents of the "text"
field and we have a
revision history, etc.  We use the slug to name the file.

In cases where we want these files to contain dynamic
content derived from
information in bric, we just create a special template in
the directory at
hand (this overrides our default template) and in these
cases we still have
the template version history to keep track of changes.

We used to manage these text files like "media"
but found it difficult to
edit them when they are used this way.  We find the media
type is most
useful for binary files - or files you don't frequently edit
with a text
editor.

JD

On Dec 17, 2007 10:16 AM, Matt Rolf <rolfmdenison.edu> wrote:

> We manage all our css as stories.  We simply use
another output
> channel to get the .css extension.
>
> When we redesigned our site, we put the css throughout
the category
> structure, and our templates know to include references
to the proper
> css in the proper files at burn time.
>
> -Matt
>
>
> On Dec 17, 2007, at 11:24 AM, Bret Dawson wrote:
>
> > Yeah, I was going to pipe in and say the same
thing. It's actually
> > nice
> > having everything in its own directory, and the
diffs the Bricolage UI
> > offers are extra-helpful with stylesheets.
> >
> > (Also: never underestimate the power of symlinks
to bridge the
> > transition from foo.css to foo/index.css.)
> >
> > Best,
> >
> > Bret
> >
> >
> > On Mon, 2007-12-17 at 11:23 -0400, Phillip Smith
wrote:
> >> Although, I recently tried out using *stories*
for CSS files (all
> >> text files actually -- Javascript, Perl/CGI,
etc.) and must say that
> >> I quite like it. It does seem to work best if
each one resides in its
> >> own folder (via a slug) -- e.g.,
/ui/css/default/index.css, /ui/css/
> >> print/index.css, etc. -- but that actually
keep things quite neatly
> >> organized. And, the benefit is that small
changes are easily
> >> accomplished via the Bricolage UI and --
unlike media -- you can
> >> actually get useful diffs when comparing
versions.
> >>
> >> (Thanks to Bret Dawson for making me give that
a go.)
> >>
> >> On 17-Dec-07, at 7:14 AM, Adam Ma'anit wrote:
> >>
> >>> We manage CSS files as 'media' instead of
stories. This allows you
> >>> to edit the CSS files using your favourite
text editor and makes it
> >>> easy to manage in Bricolage by having the
file names the way you
> >>> want.
> >>>
> >>> -a
> >>>
> >>>
> >>>
> >>>
> >>> On 17 Dec 2007, at 10:29, Daisuke Maki
wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> We're trying to get a site rolling
with Bricolage, and we are
> >>>> stumped at
> >>>> a seemingly easy to solve problem:
namely, how do you mange CSS
> >>>> files
> >>>> under bricolage?
> >>>>
> >>>> We naively thought that you could
simply use a CSS story type, but
> >>>> the
> >>>> URI scheme got to be a problem: for
example, we didn't want CSS
> >>>> files
> >>>> that looked like /css/foo/index.css or
/css/foo/foo.css. But if you
> >>>> don't include the slug in the URI
category, Bricolage thinks that
> >>>> difference css files under the same
category are the same -- for
> >>>> example, /css/main.css and
/css/foo.css are considered to be the
> >>>> same thing.
> >>>>
> >>>> I notice that Bricolage relies on a
everything-is-under-a-directory
> >>>> approach, but what *is* the best
practice here? Do people simply
> >>>> not use
> >>>> bricolage to manage CSS?
> >>>>
> >>>> Thanks,
> >>>> --d
> >>>>
> >>>
> >>>
---------------------------------------------
> >>>
> >>> Adam Ma'anit
> >>> Co-Editor
> >>> New Internationalist
> >>>
> >>> Visit the NI website: http://www.newint.org/
> >>>
> >>> Support independent media by subscribing:
http://www.newint.org/
> >>> subscribe/
> >>>
> >>> Shop for Fair Trade and Organic goodies:
http://shop.newint.org/
> >>>
> >>> Listen to Radio New Internationalist: http://www.newint.org/ra
dio/
> >>>
> >>> Geek out with our Digital Edition: http://www.exactedition
s.com/
> >>> shop/386/422/
> >>>
> >>> Phone: +44 (0)1865 811400
> >>> Fax: +44 (0)1865 793152
> >>>
> >>> New Internationalist is an independent
not-for-profit communications
> >>> cooperative. Our multi-award winning
magazine, New
> >>> Internationalist, brings
> >>> to life the people, the ideas and the
action in the fight for global
> >>> justice.
> >>>
> >>> New Internationalist Publications Ltd. is
incorporated in England
> >>> under no.1005239.
> >>> Registered Office: New Internationalist,
55 Rectory Road, Oxford,
> >>> OX4 1BW, UK
> >>>
> >>>
> >>>
> >>>
> >>
> >> --
> >> Phillip Smith,
> >> Simplifier of Technology
> >> Community Bandwidth
> >> http://www.community
bandwidth.ca
> >>
> >>
> > --
> > Bret Dawson
> > Producer
> > Pectopah Productions Inc.
> > (416) 895-7635
> > bretpectopah.com
> > www.pectopah.com
> >
>
>

On Dec 20, 2007, at 13:45, John Durkin wrote:

> We used to manage these text files like
"media" but found it  
> difficult to
> edit them when they are used this way.  We find the
media type is most
> useful for binary files - or files you don't frequently
edit with a  
> text
> editor.

Didn't I add the ability to edit Media that are of the MIME
type text/ 
* in the UI? Or is that just in the trunk? Or am I
misremembering?

Best,

David