Closed (fixed)
Project:
CSS
Version:
6.x-1.0
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 May 2010 at 12:18 UTC
Updated:
30 May 2010 at 12:20 UTC
Just wondering:
Is this module meant to use CSS definitions on a per node basis?
Just for info:
Today I read this interesting article about blogs with unique designs per post:
- http://www.webdesignerdepot.com/2010/05/showcase-of-blogs-with-unique-po...
For Wordpress it seams there's a module to achieve this called Art Direction:
- http://wordpress.org/extend/plugins/art-direction
Therefore: can CSS module be compared to Wordpress' Art Direction plugin?
Comments
Comment #1
fax8 commentedHi there,
Exactly.
I'm not experienced with Art Direction or Wordpress but the description of Art Direction looks pretty similar to CSS module's.
Basically CSS module adds a CSS field for each enable node type: this means that you are able to add you css rules to any node creating css based node layouts. The only limit of this module is that it can't modify the page html layout so only CSS styling is possible.
Setting this as fixed, feel free to reopen if you still have questions.
Thanks,
Fabio Varesano
Comment #2
Marc Bijl commentedHi Fabio,
Thanks for the quick reply,
and very interesting not to say inspiring stuff!
Few questions indeed ;)
(1)
Is the CSS field added for every node type (so that all nodes of a certain type have the same design), or for every node separately (so that every node can have its own design)?
(2)
Imagine: after creating seperate CSS definitions per node for a few years, I want to get rid of this (and have all nodes in the same layout again). What can I do?
Regarding this 2nd question, I can imagine it will be smart to use only a limited set of names for classes, which can be used AND defined for each node e.g. "excerpt", "paragraph1", "paragraph2", "primaryimage", "secondaryimage", etc etc. Once I don't feel the need anymore to have all these classes defined per node, I can empty the CSS fields of all nodes (SQL/PHPMyAdmin), and -if necessary- set standard definitions in one general CSS file. Is that correct?
Cheers,
Marc Bijl
UPDATE
======
Just in case you're interested,
another post about this trend here:
- http://www.smashingmagazine.com/the-death-of-the-blog-post
Comment #3
fax8 commented1 - The css field is added to every node of each enabled node type. This means that if you have a node type called "Blog post" and you enable CSS module on it, you'll be able to style each node of type "Blog post" with it's own CSS rules. The module doesn't currently prermits per node type CSS rules but it could be a nice feature to have, so if you need it feel free to open a feature request. Maybe I can code that for D7 version of CSS module.
2 - Just drop CSS module SQL table. If you use standardized class names on your node you won't loose them and you'll perfectly be able to style them in your theme on a regular .css file.
FV
Comment #4
Marc Bijl commentedWow, man, this is absolutely fab!
I got very inspired e.g. by the site of Jason Santa Maria:
- http://jasonsantamaria.com/articles
Every article has its own "theme" (except header and footer on the page). At Jasons site may be a bit overdone here and there (for my taste), but it's definitely very, very inspiring! Great way to create glossy like blog; something between the old fashioned blog and printed magazine. What they say, a blogazine!
Thnx very much,
you just made my day man!
btw
A css per node type won't be necessary for me; in fact I think such a module once existed. Hmm, let me think...
Ah, it was done by Bèr Kessels, called Sections module (http://drupal.org/project/sections).
I've used it long, long time ago, when I started to make my first Drupal site ;)
CU
marc
Comment #5
dagomar commentedI was also looking for a module like this, because I got inspired by this: http://www.smashingmagazine.com/the-death-of-the-blog-post/
I'd also like a blog where I can just change the whole design on a per-node basis. Looks like I found the module to do this :)
Thanks!
(btw thats a really interesting article I posted, perhaps some inspiration for others)
Comment #6
fax8 commentedcool! give css module a try!