I am a web developer/designer and have been looking for a good framework that I can use for my projects, but one that will also integrate seamlessly into a CMS that is hopefully easy to use for my clients. So naturally, Drupal was the first brought to my attention. I have installed and messed around with it, and while I haven't gotten my head wrapped around it yet, I like what I see.
I've read a bit about there being a fair amount of differences between 6 and 7. Would it still be worthwhile for me to start learning on 6 (which I have a book about, "Pro Drupal Development") or should I wait until 7 is out? I'd really hate to learn something and then have to completely undo my way of thinking to suit the latest version. I don't want to get stuck in a position with a large project and a framework I don't understand (I've been there, it equals angry clients and hair loss. I like my hair and want to keep what's left of it).
My next question is a bit more specific. I started trying to learn how to create themes and noticed that there was an option to have your admin theme different from the main site theme. This is good, as it's one of my bosses requirements for moving into a new CMS. However, I did notice that when creating Content (a Page, for example), the theme seems to go from Admin to Site after I save. Is this a limitation of the system, or can all administrative features use the same theme? Clients seem to get confused easily with things like that, so it's a major concern for me.
Finally, how long until 7 is released? I read somewhere that it won't happen until 90% of the bugs have been released. I looked for a roadmap, but didn't see one.
If these questions have been asked and answered elsewhere (and I'm sure they have), please just point me in the right direction.
Thanks.
Comments
Well..
I can't answer all of your questions but I would say jump in. Drupal 6 is a great system. Just because Drupal 7 is coming out, It doesn't mean you have to move to it. In fact, i THINK drupal.org is still on 5 or was for a long while after 6 came out. Baffled by this, I was enlightened when one of the regulars on the development team said, "Why switch to 6? 5 is stable here, and secure." Good point. Another reason not to switch to 7 quickly is that many, many modules are not going to be 7 compatible. Many are, but not all. Also, the API documentation pages are excellent with regard to showing changes between the different versions. The curve is steep enough that I would say start with 6 and move to 7 IF there is a need to. Otherwise, 6 isn't going away and it's stable and secure.
With regard to your theme issues. I am a little confused. Page creation shouldn't be included in the admin theme. If a user clicks on "Create Content" then "page" the theme should not be the admin theme. I think there is an option in there somewhere to include the admin theme in content creation pages and maybe this is selected in your case. I know that in all of my sites, the admin theme is never seen by users and they use the create content pages all the time. That said, most of those sites are still running on 5. Because, there isn't any reason to upgrade. The work and are secure.
I would definitely recommend
I would definitely recommend drupal. I would use 6 for your current work and install 7 somewhere to play with and learn. You could use 6 and never upgrade if it works for you.
creating content in drupal is not an administrative funciton as many admins want users to create content (blogs, user profiles, video, etc.). If you want to make it the same as the admin theme, the easiest way I can think is to create a node-add.tpl.php and maybe node-preview.tpl.php (you'll have to verify that is the correct title, as I am just working on my first theme as well) that has the same style as the admin page. Then use triggers/actions to redirect after saving, as when you save by default you are redirected to the content page that you just added.
There i ssurely more than one way to do this as there is for almost everything in drupal. This method is not recommended if users can create content as they would be redirected to the admin page and get an access denied error. You can also create these templates for specific content types. Search for info on tpl files and you should find your answer. Root Candy, although I've not used it looks like a nice admin theme. I would try a couple of different themes before you dig to deep as one may do what you want out of the box.
I am sure you can have the theme dependent on the user as well I am just not sure how to do that.
Just wanted to add learn cck, views, and rules should be mandatory. You can do a lot with just those modules.
Chris
.
Ditto on using Drupal 6. You could use it for a while or keep using it, but it's not worth waiting on Drupal in general just because 7 isn't out yet. There are many reasons to keep using Drupal 6 for a while on production sites even after 7 is released.
It sounds like you checked the option to have Edit Content be included in what is handled by the administrative theme. So if adding or editing content is done in the administrative theme, it will go back to the main theme after saving simply because its taking you to the page in question. Basically, after you submit it, you are back "on the site" and no longer in an administrative area.
Excellent
Thank you for the responses on this. I am definitely going to start learning 6 then.