Hello,
I have been tinkering with Drupal now for a few weeks and it is excellent. The more I use it, the more I realise just how much I have to learn.
One of the main things that puzzles me is how I can improve my site over and above the basic install.
I was wondering if there was a generally accepted "Best Practice" to follow regarding an installation and the usual extra modules most sites should use.
It appears that Views, CCK, an image module such as IMCE, a wysiwyg editor such as FCKeditor are very common.
I was wondering if there were any other "must have" modules that help matters.
I almost expect the answer "it depends on what you want to do" etc... But that doesn't really help as I am still a beginner and the initial learning curve can be quite steep.
So what are the basics us beginners should follow.
Also, is there a checklist somewhere of what the standard things one should do to get a site functioning standardly.
In other words has someone been good enough to write down a step by step procedure to follow, post-installation, to get everything up and running properly.
Things such as:
Enter basic site structure details
Create a home page
Create the menu's
Activate image module
Activate editor
etc. etc.
This would be utterly useful if it existed.
Can anyone help?
Thank you in advance.
Sam
Comments
I think the problem is that
I think the problem is that even within that small list people don't use it all, therefore the instructions/documentation is housed within the project sites of each of those modules independent of the others.
But I think a good first step (after installation) is to figure out what you want on your site with a pencil and a piece of paper. Then from there you figure out which modules you need, then look up the individual documentation for each of those modules.
Basic steps for Drupal beginners
Hi Sam. You've no doubt started doing so already, but the first place to visit is this site's own Documentation, particularly
http://drupal.org/getting-started
and within that, key sections like
http://drupal.org/handbook/customization/tutorials/beginners-cookbook
There's also documentation for some key modules, above and beyond that which comes with the modules.
It's a lot of stuff, and content aimed at beginners is mixed in with that for pros, so it can be a little hard to find the instructions you're looking for. I would just browse through the menus for a while to see what sort of content is in there, and take note of the items that look helpful.
On my own site, I have beginner-level instructions for administering a Drupal site:
http://www.drupalace.com/EDAM
You may find useful notes in there on creating pages, entering basic site details, etc. However, it's aimed at the admin of a site that's already set up, so there's no information on, for example, installing and configuring new modules. The Drupal.org documentation will be much more helpful there.
Some other posts might address specific questions of yours, like this post on a checklist I use for new site setup:
http://www.drupalace.com/blog/2009_01_20/checking_out_drupal_6_dipping_i...
Going back to Drupal.org and your questions, there's a section on best practices:
http://drupal.org/best-practices
And I know there's a section on "recipes" for specific types of sites, which might be a big help on what modules you'll want to consider for your planned purposes. Can't track it down right now; you'll probably come across it while perusing the documentation menu.
Good luck!
--------
Manuals, Q&A and more for the Drupal beginner
Basic Steps For Beginners
Hey Drupalace,
Now we're talking!
Looks like I've got a bit of studying to do.
It would be great if there was a more prominent procedural flow chart to help you step by step on what is really needed to make sure you have done everything you "should" do to get the set up right.
All this should be done with a view to following good SEO practice.
Things like duplicate content under different URL's can be a problem, but it's only when you start digging around that you realise this and that there are workarounds.
Why doesn't this get covered somewhere, along with dozens of other "best practices".
Perhaps it does exist, such as in the links you gave, I just wish it was a little easier to dig out the hidden gems and also to find the missing pieces from the puzzle.
It's kind of like when you do the install you think you have finished the puzzle. Then when you look, there seem to be a few pieces missing. Then when you find and insert those, you realise that you really only have half the box done.
Answers such as "figure out what you need and install the module" don't really cut it.
Most people realise that you need 4 wheels for a car, an engine and a steering wheel.
Some might not realise that if you add brakes, a petrol tank, speedometer, a rear view mirror and some seats, you can have a much better driving experience!!!
Thanks for your answer.
Please feel free to let me have any more tips ;-)
It would be greatly appreciated.
Thanks,
Sam
Hi Sam, or is it Colin
Hi Sam, or is it Colin (looked at your profile)
Part of the issue you seem to have is what you want to do
re your original post
"I almost expect the answer "it depends on what you want to do" etc... But that doesn't really help as I am still a beginner and the initial learning curve can be quite steep."
My first comment is that "it depends on what you want to do" is totally appropriate. In fact i would even go as far as to say Until you have gone as far as planning what you basically want to do with the site, you don't even know if Drupal is the correct tool.
Might i suggest a whiteboard
List who will use it and what they can do
What content there will be, maybe just draw out blocks of each content, maybe add thoughts on taxonomy and how each block associates with the rest
Once you have this you will have some idea, then you can move towards what you need. The thing is many things can be done in different ways, and there are modules that overlap so the correct choice is those that meet your needs and are compatable with each other. And on top of that your server needs to have the resources to run it all.
As a minimum i would say CCK ( some of which will be in D7 core) Views, and Contemplate. But remember each Module needs resources, which takes us back to what you want to do
I am no SEO "Expert", but personally I would not get too hung up on SEO, as untill you have content its a mute point. I have seen a number of sites where they are concentrating on SEO and statistics, when fixing the original dummy content would provide a far better use of resources. This doesnt mean ignore SEO, but more consider it in perspective to your content.