Voting starts in March for the Drupal Association Board election.
The Drupal Cookbook (for Beginners) helps Drupal "newbies" by providing a walkthrough of a common Drupal Setup.
This handbook was originally written for Drupal 5. While the information is generally transferable to Drupal 6, some buttons, links, and menu items have been renamed or moved. Every attempt is made to keep these handbooks current.
The intent of the Cookbook is to help the new Drupal user create a typical site. At that point the user will be better equipped to diving deeper into more advanced features.
This cookbook requires a basic understanding of the General Concepts of Drupal. Additional resources for understanding terms used in Drupal include:
The Cookbook and other documentation on drupal.org uses the following standard for indicating site navigation:
Administer >> Access control >> User management >> Roles.
The above example tells the user to click on "Administer" in the navigation menu, then "Access control", then "User management", and then "Roles".
Working with Drupal
Here are some general reccomendations:
- Use a test site that uses the same Drupal version and modules as the target site. Use a copy of the live database. Avoid development on a live site.
- Don't try to make the "perfect site" on the first attempt. Muddle through for a while. Stressing over the perfect solution can lead to frustration.
- Start by learning the basic functionality of Drupal. Find out what Drupal can do before working towards a specific goal. Once comfortable with the "core" features and behavior, move on to more complex contributed modules such as Views, CCK, and Organic Groups. These modules and some others require a good bit of understanding to master. The power and flexibility of Drupal and its modules will become apparent over time.
- If you need a custom theme, customize one of the default themes before creating starting from scratch. Refer to the Drupal 5 theme guide or Drupal 6 theme guide.
- Limit the number of blocks, images, and graphics that clutter the page.
- Participate in the forums, the Documentation Team, and IRC.
Get support through Drupal.org
Before posting to the Drupal.org site:
- Search to see if the subject has already been covered to avoid having duplicate postings & issues. If Drupal's search fails, Google will often point to the right references. To use Google to limit the results to Drupal.org include in the search field site:drupal.org
- Ask one question per post. The issue tracking system can only handle one at a time.
- Don't hesitate to ask the question again and add
I'm a newbie, can you say this in easier to understand terms, please?
- Before posting, read the tips for posting in the Drupal Forums. Try to describe the situation/case completely. Explain what has been done so far and what you are trying to achieve.
- When requesting changes don't demand or threaten to abandon Drupal, and certainly don't resort to name calling or derogatory comments. Often times the best way is to jump in and ask how to get involved.
- In general you will see core versions written as 5.x and 6.x or a specific version as 5.18 or 6.12. Contributed modules are listed with a core compatibility and a version number, such as 5.x-2.5 or 6.x-1.6, which mean "Drupal 5 compatible, Version 2, release 5" or "Drupal 6 compatible, Version 1, release 6." This way, if you see "5.x-2.5" you can know that it means a module release rather than a core release.
For example, if a page is not showing up correctly, be prepared to provide the following information:
- A descriptive title
- Operating system and browser name. Version information and a list of potentially relevant plug-ins you are using are often important.
- Version of Drupal (5.x, 6.x etc)
- Any contributed modules
- The versions of PHP and MySQL being used, as well as the name/URL of the hosting provider. To see which versions of PHP and MySQL (or other database) that the site is using, in Drupal 5 navigate to: Admin >> Logs >> Status Report, and in Drupal 6: admin >> reports >> status.
Things to keep in mind
A common mistake when approaching a solution to a problem in Drupal is to make an assumption about how Drupal works. Drupal is a unique and powerful platform that is probably quite different from other solutions you may have encountered.
Start simply by making something visible, then celebrate what you have accomplished. Taking one small step at a time will lead to a better site. Don't indiscriminately add many contributed modules right away. Get comfortable with modules one at a time. Modules that are not appropriate or used should be disabled and uninstalled.
As with most things worth mastering, there is a learning curve with Drupal. But there is lots of support available as well.
Module developer's guide
A Drupal site can have three kinds of modules (the 3 Cs):
Core modules that ship with Drupal and are approved by the core developers and the community.
Contributed modules written by the Drupal community and shared under the same GNU Public License (GPL) as Drupal.
Custom modules created by the developer – often for a particular use case specific to the site they're working on.
This section of the Developing for Drupal handbook will help you to write your own modules and to collaborate with the community on shared projects.
This is the link where beginners start to create own module please click on this link :-