The magazine I’m working for magazine looking to reproduce a rich layout of the paper on there website.
Each article (mixe of different asset :interview, blog post, discution, pool, article) have different layout
1 teaser node on the home page "teaser.jpg"
2 teaser node on the channel page node "teaser bis.jpg"
3 full length
There is a nice write up at http://drupal.org/nyobserver about this solution that involved creating one cck content type for the home page and an other for the channels edition
Previously I was involved (on the client side) of an other newspaper's website http://next.liberation.fr and http://voyages.liberation.fr
We will be able to use a new search panel and drag and drop facility of http://www.France24.com
We will help them to package it and release it to community
The france24 content search and drag and drop faciltity will a allow us the creat a rich article with different asset :
-interview
-blog post
-discution
-pool
-article
and spare use lot of the burden of choosing each asset with drop down menu on a fixed grid.
However I would like to find a more satisfactory way to store the content that a cck content type. A sort of list of the content and choosing for each of them is they will be include :
- in the teaser home or channel
There position on the page and on the teaser view :
- in a vertical inset
- in a horizontal inset.
There layout :
- Teaser en defonce
- Title
- Like a citation
- ETC…
| Attachment | Size |
|---|---|
| teaser node bis.jpg | 92.85 KB |
| full lenght article.jpg | 213.82 KB |
| teaser node.jpg | 76.98 KB |
Comments
Not sure if I fully
Not sure if I fully understand what you need. If you want absolute control over how the page should look (the exact order of articles in exactly the right place) I think a CCK type with nodereferences does provide the highest amount of flexibility. However, for a lot of purposes you could do just as well with nodequeues or by indicating in the articles themselves (with a dropdown or select list as a cck field) where they belong, and using that information to make your Views. And then you can just embed those Views in a page with blocks and panels.
If you want the display to be different for the full articles (and not just the teasers on the front page or channel pages) you can make use of modules such as Taxonomy Theme.
Something else NYobserve 2read about the nodereference solution?
Nodereferences is the way I want to go
Except the NYobservers.com would you recommand something else to read about this solution.
Can I use Taxonomy theme to give a different layout for a different sort of content ?
It say on http://drupal.org/project/taxonomy_theme but have you a good feed back of this module ?
taxonomy theme
Taxonomy_theme is a solid module.
Here's a screencast about the nodereferences approach - although it's pretty basic. If you want to save your previous frontpages when you make a new one (so people can see the frontpage of last week, last month, ...), make sure to either enable node revisions, or make new nodes with Node clone so you don't have to re-enter every bit of information.
You might also consider a combination of both approaches I described above: nodereferences for absolute control over the most important items on the frontpage, but Views that select on recency and taxonomy for the other items. That would lift some of the burden you're talking about. E.g. http://www.schamper.ugent.be/ is done almost entirely with Views that filter on taxonomy items.