How to add css styles to a website?

Ruby Apps Radiant CMS
21

On 9/22/06, John W. Long [email protected] wrote:

I’d appreciate a patch that addressed these issues.

Deal! I kinda fell in love with Radiant in the past few days (evaluating
it)
so it will be a pleasure.

Be patient, because I’m still studying hard for college. A week from now
and
I’ll get to it.

22

On 22/09/06, Keith B. [email protected] wrote:

I need to build a small archive, but not really a date based one. I
just need to show 5 Articles at a time, then the next five. I assume
a behavior would do this, but actually at the moment have no idea how
to start. Any tips and prods in the right direction appreciated.

I’m not sure how to automatically increment the offset, but this would
be kinda what’s needed:

<r:children:each offset=“0” limit=“5” by=“name” order=“asc”>

–
Regards,
Dave

23

2006/9/20, John W. Long [email protected]:

It’s probably better to create a layout with a content type of
“text/css” and put just the tag <r:content /> in the layout. Then create
a page, assign the layout, and paste your css in the body part.

Well, i figured out how to apply css to one page, but the children
won’t use the styles. I just don’t get a site-wide css working with
the possibilties radiant offers. How it works with a static css file
is clear to me. Can someone give me a little more help :slight_smile: ?

Thanks,
Tino

24

On 9/24/06, Tino B. [email protected] wrote:

2006/9/20, John W. Long [email protected]:

It’s probably better to create a layout with a content type of
“text/css” and put just the tag <r:content /> in the layout. Then create
a page, assign the layout, and paste your css in the body part.

Well, i figured out how to apply css to one page, but the children
won’t use the styles. I just don’t get a site-wide css working with
the possibilties radiant offers. How it works with a static css file
is clear to me. Can someone give me a little more help :slight_smile: ?

Create a temporary Radiant instance and when you run script/setup_db
select option 3 (styled blog). This seems to do what you are asking
for.

HTH,
Tom

25

Create a temporary Radiant instance and when you run script/setup_db
select option 3 (styled blog). This seems to do what you are asking
for.

Ah, now i have understood the flow. Thanks.

Tino

26

To avoid having stylesheets in my sitemaps, I create a page part named
“no-map”. Then I do <r:children:each><r:unless
part=“no-map”></r:unless></r:children>

2006/9/25, Steven N. [email protected]:

27

On 20 Sep 2006, at 23:54, John W. Long wrote:

On the Ruby site we put the stylesheets in public/stylesheets.

Given the difficulty of keeping the stylesheet out of the navigation
(when working with r:children:each) if you put your CSS in the
database, moving the stylesheet out of Radiant seems like the best
practice to me, no? Or we should have some sort of fifth status
option: draft/review/published/hidden/hiddenfromnav. What’s the
meaning of the current ‘hidden’, BTW?

-- Steven N. http://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.org stevenn at apache.org
28

On 9/25/06, Steven N. [email protected] wrote:

… we should have some sort of fifth status
option: draft/review/published/hidden/hiddenfromnav. What’s the
meaning of the current ‘hidden’, BTW?

I agree we should have a status of “special” or something like that for
stylesheets and content that would not be included by default in
eachlistings and similar.

Not every content is going to be a regular page.

Giovanni, having that would save you a “no-map” hack :slight_smile:

-M

29

I know that something like that would save a hack, but I’m starting to
think
that page parts should be naturally used to describe attributes of the
page.

2006/9/25, Mislav MarohniÄ? [email protected]:

30

On 9/25/06, Giovanni I. [email protected] wrote:

I know that something like that would save a hack, but I’m starting to
think that page parts should be naturally used to describe attributes of the
page.

Funny. I always thought that page parts should be naturally used to hold
parts of the page.

What next, you will need revision date attribute besides published date
and
you will start creating page parts everywhere holding a timestamp and
being
named ‘revision date’?