Greetings,
I've been reading up on Stories and Pages. I'm still not convinced I understand the advantages of one over the other - and maybe there isn't one.

In my case, I've got a library of informative articles. The library gets expanded when I (or my editor) have time and content to publish. These seem like they'd be perfect for the Page part of Drupal because they follow a heirarchy and don't change much if at all once they're uploaded.

I also have 6 regular columns, written by other folks and edited by my editor and myself. These seem like they'd work under the Stories framework. I'd like to be able to tie links back into the library items within each story based on the topics and keywords used in them. (Aside: Can Drupal be set up to automatically display links back to the library topics based on unique keywords for each article? ) But these also don't change much after they've been published.

I also have an established forum and Ad delivery engine to add to the mix. I think the forum is easy to combine with Drupal - just a link. The Ad delivery engine use PHP and javascript code - again I think Drupal will handle it fine though I haven't looked into how just yet.

Does it make sense to use Pages and Stories the way I've described or does it really matter? I assume that in order to display the Stories under one generic grouping (like "Columns" for example) I would create a new menu item?

Sorry for the vagueness of my questions. I'm still trying to wrap my mind around how the whole of Drupal works - big task.

TIA
Gregg

Comments

gbanse’s picture

I think I answered my own question.

To some degree it is arbitrary which type you use. But here's how I set it up and why.

I chose to use Pages for content about the website, the business and the business of running the website. This content does not allow comments, is seperate from the content I want crawled by the search engines and I'm the only one who has rights to add/edit/delete it.

I chose to let stories be the content that my authors publish and the community can comment on. WHen combined with Taxonomy_Access (the module) I have reasonable granularity on the security. I can limit access to any particular term but I do have premoderation in place so no matter what node the poster wants his piece to go in, I have final say BEFORE it goes live.

Pretty simple really. Now I'm onto laying out the framework for blogs.