I am examining the feasibility of moving my site, fairhousing.com, from ColdFusion to Drupal. One thing I want to do is run three blogs. One would be for fair housing news and would be the dominant content on the home page. The other two would be for job listings and fair housing events and would be accessible from the left-hand navigation.
As I understand it, the built-in Drupal blog module will allow all users to have a blog. I don't want that. I want three blogs, and I want to be able to specify where each blog displays.
I've installed the Everyblog module, which gives me any number of blogs, but I don't seem to have any way to choose to have just ONE blog displaying on the home page - it's either all or nothing.
Am I wrong about either blog solution? Are there any others I should look at?
Thanks!
Comments
=-=-
For what you want I don't know that the blog.module or any blog.module is appropriate. I'd create my own content types for each area (what you are calling a blog).
ie "fair housing news" content type
ie "fair housing events" content type
so on so forth. If the need for other fields is necessary expand on content type creation by employing the CCK.module and it's field add on modules.
This method affords you the ability to create a custom taxonomy for each content type and create lists as you see fit. You can also set the "fair housing news" content type to be automatically promoted to front page, while other content types can be set by default not to show on front page.
Not necessary imo. It might
Not necessary imo. It might be better to use just the blog content type, and create seperate taxonomies for the 3 blogs. Display only your frontpage taxonomy on the front page, and link to the other blogs with the housing news/events taxonomies.
Edit: Well let me append that perhaps both approaches are equally valid, but they're more versatile in different ways.
=-=
the versatility of using seperate content types will come into play, if the OP decides he/she wants a certain content type to have a specific field available to it but not want that field available in all blogs created by the blog.module.
example: the fair housing events content type, may need a date field while the others do not.
That's true, but you also
That's true, but you also clutter up your interface with 3 different add node buttons. It would be a big issue especially if you decide to go for up to 4/5/6 blogs.
Also, if you have something that's both an event and a news, you can create 1 blog to belong in both taxonomies, rather than create 2 posts. But it really depends on what the user needs.
Thanks! That's exactly what
Thanks! That's exactly what I need. I've looked at the CCK.module, and I haven't tried it yet to see if it will work with 6.x.
Now, a related question - since all pieces of content are assigned a sequential node number, with no differentiation between blog posts, news items, jobs, pages, stories, etc., is there a way to display, for example, all the nodes of content type "Jobs" in one place?
And VM, you're right - I will probably want to customize the fields, now that I know I can, so I think your approach will work a little better for me. But it's nice to know about the taxonomies.
I'm a complete newbie, as you can tell. :)
=-=
you can assign paths using the path.module (to write url aliases) and pathauto.module to automate path alaises.
this will allow you to create paths to lists. ie: yoursite.com/jobs points to a listing of all content with the term jobs. taxonomy.module will come in handy here and using the documentation about taxonomy.module will help you better understand how taxonomy.module works with regards to listings.
you can of course expand on this by employing the views.module and create your own lists or content and place them at whatever path you choose.