Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
Well Ive installed drupal onto my server and have been playing around with it figuring out how things work and the idea of nodes etc. My question now is whats the simplest way to transfer my current design into drupal. The website is for a sports team. My design basically is as follows:
header
navigation level 1 (contains primary links)
navigation level 2 (secondary links - as in "my account" etc and the login field as well. Ill be creating the login field from a drupal based tutorial I found on making your own login forms)
left column (always visible but content should be dynamic ie latest news, recent matches)
center column (team news goes in here as well as mission statement)
right column (sponsor advertisements go here, no need for it to be dynamic since it will rarely be edited)
footer (spans all three columns also static since wont be updated frequently)
I'm having a tough time here trying to figure out which I should choose, Drupal or Joomla? I hear that theming in Joomla is much easier, but then again in Drupal 6 it's suppose to be pretty rockin'. However, who knows when Drupal 6 will actually be released. Regardless there are a few functionalities that I need.
I need a fully functional shopping cart, which I have seen the one on the Drupal site. I would like to hear how other people have been liking it.
I'm porting a hand-coded outdated site to use drupal. It's an online magazine. I have pretty much everything figured out except one thing that's been bugging me for a while (doing this part time).
Like a paper magazine, the site releases "issues" which all contain multiple articles. I think that what I'm after is something that's lacking (but not unfeasible) from drupal and that the category module (which I'm not a big fan of). In my primary link menu, I have a "Back issues" link and in there I want to list all back issues. An issue should be a custom type because it contains some text and images. Each article is a "child" of a particular issue and they should all be listed inside the issue custom type node body.
Here is what I was thinking and you can probably let me know if that all makes sense.
1. Create an Issue content type with all the custom fields I want to have
2. Create an Issue vocabulary and have all the issues releases as terms (ex: august 2007)
3. Install the View fusion module (or something like it) to be able to render a view inside of the body of a node and allow to list all the articles tagged with the given term.
4. Create an Article content type with a required vocabulary term selection from the Issue vocabulary to correctly categorize the article.