Drupal web practices Wilson Wingston Sharon firstname.lastname@example.org
Planning saves time Plan your site. Drupal provides a good toolset to help you build your site but you still need to plan. Good wireframes and proper planning can avoid significant misunderstandings and problems later. Plan for the future. You should revisit and reevaluate your site each time there is a major version release of Drupal. This does not mean you have to upgrade it, but you should evaluate and plan for an upgrade approximately each 12-24 months.
Maintenance Get involved in the community. This will help you follow development trends and, while helping others, you may just come across a cool idea that solves your own problem. Back up your site. Back up both the database and the files on the web server. Test your backups! If you don't test them, you have no idea if you are doing it right. Test your PHP snippets. Drupal gives you a great deal of power and flexibility when using PHP code in blocks. Unfortunately, a stray character or a missing semi-colon breaks PHP. Drupal then attempts to evaluate this broken code on any requested page, the PHP interpreter chokes on it and therefore your whole site is broken
Maintainance Set up a test site using your live data. You do not want to have to ask in the forums how to save your site. Never do development or testing on your live production site. Drupal is fast and easy to install. Always test on a test site first. Test that your backups work and that you know how to do a restore of your site. The test system can be your local desktop..
Maintainance You do not want to discover the hard way that you forgot a file or did not know how to do this when your site is down. Test your site upgrade procedure before risking your live site and document the steps you take. 2 am upgrades on a whim always lead to disaster.
More mngmt Modules that are not part of core may or may not be supported by their contributor for a Drupal version upgrade. Check if all your modules have upgrades before moving drupal core. Rename or remove update.php from the root of your Drupal directory unless you are actually updating your site. There are protections for it in the update script, but why take a chance.
Accounts and roles Do not use the first user account for day to day stuff on your site. This account should be used for the site setup, major configuration changes and upgrades only. Set up some appropriate roles (do not forget to update these roles as you add new modules). Some role suggestions are 'site admin', 'user admin', 'site contributor'. What roles you need to create will depend on the type of site you have designed. Note that anyone who can administer users can grant themselves additional permissions.
Updating drupal Read update.txt – comprehensive information about how to upgrade. Put site into maintenance mode. Back up site and settings.php Disable all contrib modules. Upload new drupal core files. Run update.php Enable all modules. Run update.php again.
cron www.mysite.com/cron.php is the cron task scheduler that runs unobtrusive drupal maintenance tasks. Use curl,lynx,wget to set up cron. Server os dependant so see documentation of your hosting provider to see that cron runs at least once a week.
Going live Domain hosting services include Domain naming registration Server space Mail id Site administration tasks Google for a good hosting provider before buying space.
Search engine optimization Categories content properly. Maintain a robots.txt Use nodewords module to manage meta tags for your site. Publicize. Be patient google will find you.
In conclusion Webmastering need not be a daunting task. Don’t be scared of asking around in forums. Read “readme.txt” – usually very helpful. Google any problem you have with drupal.