ImageField provides an image upload field for CCK. ImageField is a CCK-based alternative to the legacy Image project. It boasts features such as multiple images per node, resolution restrictions, default images, and extensive Views support.
ImageField does not provide a built-in thumbnail solution, but complements the incredibly powerful thumbnail generation module ImageCache.
ImageField related projects
ImageCache - Dynamic thumbnail generation.
ImageField Extended - Add additional data to images other than the default Description, Title and Alt.
ImageField Focus - Define custom focus and crop areas to be combined with ImageCache.
ImageField Crop - Crop images permanently after upload.
Image FUpload - Bulk image uploader.
Dependencies
ImageField 6.x depends on the CCK and FileField modules.
ImageField 5.x depends on the CCK and ImageAPI modules.
Compatibility notes
Image.module - Imagefield is not compatible with image.module content types. If you add an imagefield CCK field to the image type provided by image module, image module will delete all the imagefield images on every node update.
Migration
See the FileField Handbook for a list of migration scripts from other modules such as Image.module, Image Attach, or Node Images.
Read More...
www.drupal.org
Sunday, October 16, 2011
Saturday, October 15, 2011
Module - FileField
FileField provides a universal file upload field for CCK. It is a robust alternative to core's Upload module and an absolute must for users uploading a large number of files. Great for managing video and audio files for podcasts on your own site.
Features
Configurable upload paths allow you to save files into per-field or per-user directories
Per-field and per-node file size limits
Extensive API for extending field widgets and managing files
Full revision/translation file management
Views support
Ajax Uploads (and progress bar support with the PECL uploadprogress extension)
Pretty Icons
All the goodness of CCK (multiple output formats, shared fields, multiple values, and much more)
Read More...
www.drupal.org
Features
Configurable upload paths allow you to save files into per-field or per-user directories
Per-field and per-node file size limits
Extensive API for extending field widgets and managing files
Full revision/translation file management
Views support
Ajax Uploads (and progress bar support with the PECL uploadprogress extension)
Pretty Icons
All the goodness of CCK (multiple output formats, shared fields, multiple values, and much more)
Read More...
www.drupal.org
Friday, October 14, 2011
Module - Administration menu
Provides a theme-independent administration interface (aka. "navigation", "back-end"). It's a helper for novice users coming from other CMS, a time-saver for site administrators, and useful for developers and site builders.
Administrative links are displayed in a CSS/JS-based menu at the top on all pages of your site. It not only contains regular menu items — tasks and actions are also included, enabling fast access to any administrative resource your Drupal site provides.
Showcase and Quality Assurance
Test-drive in various themes on the demonstration site or watch a short demo reel.
Behaviour and Integration
Works in all themes and all browsers.
Exposes all administration links including all tabs/tasks and actions to provide direct access to any page.
Extensible with add-on features by other modules. Devel integration is built-in.
Themeable administration menu icon.
(3.x only) Implements client-side caching to minimize server-side performance impact.
(7.x-3.x only) Exposes links to individual configuration items (e.g., content types, menus, views, etc.) including their contextual links.
Related modules
This module is intended for administrative users, not for regular/anonymous users. Try SimpleMenu, Nice Menus, or DHTML Menu.
Installation
Read the documentation.
Grant the "access administration menu" and "access administration pages" user permissions to selected roles.
Drupal 6 only:
The "Administer" menu link must be enabled, but may reside in a different menu than "Navigation".
Ensure your theme outputs $closure. If the menu does not appear, consult the README.txt first.
Read More...
www.drupal.org
Administrative links are displayed in a CSS/JS-based menu at the top on all pages of your site. It not only contains regular menu items — tasks and actions are also included, enabling fast access to any administrative resource your Drupal site provides.
Showcase and Quality Assurance
Test-drive in various themes on the demonstration site or watch a short demo reel.
Behaviour and Integration
Works in all themes and all browsers.
Exposes all administration links including all tabs/tasks and actions to provide direct access to any page.
Extensible with add-on features by other modules. Devel integration is built-in.
Themeable administration menu icon.
(3.x only) Implements client-side caching to minimize server-side performance impact.
(7.x-3.x only) Exposes links to individual configuration items (e.g., content types, menus, views, etc.) including their contextual links.
Related modules
This module is intended for administrative users, not for regular/anonymous users. Try SimpleMenu, Nice Menus, or DHTML Menu.
Installation
Read the documentation.
Grant the "access administration menu" and "access administration pages" user permissions to selected roles.
Drupal 6 only:
The "Administer" menu link must be enabled, but may reside in a different menu than "Navigation".
Ensure your theme outputs $closure. If the menu does not appear, consult the README.txt first.
Read More...
www.drupal.org
Thursday, October 13, 2011
Module - Pathauto
he Pathauto module automatically generates path aliases for various kinds of content (nodes, categories, users) without requiring the user to manually specify the path alias. This allows you to get aliases like /category/my-node-title.html instead of /node/123. The aliases are based upon a "pattern" system which the administrator can control.
Pathauto depends on the Token module. See screenshots of the bulk delete and the admin settings screen. View a screencast of Using Pathauto and Views to get Index Aliases.
Stable 6.x version: Most Drupal 6 users will want to use the official 6.x-1.x releases (which were ported from 5.x-2.x). If you are upgrading from Drupal 5, be sure to read the upgrade guide
Development 6.x version: For the daring Drupal 6 users who want to test out improvements from the Drupal 7 version, the 6.x-2.x version is where all the cool stuff is being back-ported. Make sure you're using the latest 6.x-1.x-dev version of Token as well.
Development 7.x version: Drupal 7 users can start testing the 7.x-1.x releases which are currently in development. Any new features or UI changes will be only accepted for this version, and then back-ported to 6.x-2.x if possible.
Read More...
WWW.Drupal.org
Pathauto depends on the Token module. See screenshots of the bulk delete and the admin settings screen. View a screencast of Using Pathauto and Views to get Index Aliases.
Stable 6.x version: Most Drupal 6 users will want to use the official 6.x-1.x releases (which were ported from 5.x-2.x). If you are upgrading from Drupal 5, be sure to read the upgrade guide
Development 6.x version: For the daring Drupal 6 users who want to test out improvements from the Drupal 7 version, the 6.x-2.x version is where all the cool stuff is being back-ported. Make sure you're using the latest 6.x-1.x-dev version of Token as well.
Development 7.x version: Drupal 7 users can start testing the 7.x-1.x releases which are currently in development. Any new features or UI changes will be only accepted for this version, and then back-ported to 6.x-2.x if possible.
Read More...
WWW.Drupal.org
Wednesday, October 12, 2011
Module- Content Construction Kit (CCK)
The Content Construction Kit allows you to add custom fields to nodes using a web browser.
Drupal 7 and Fields in Core
Most of CCK has moved to core in the Drupal 7 version.
Please note that this is not the place to get support for D7 Fields! We are getting a number of support requests, bug reports, and even feature requests for D7 fields. Fields are in core in D7, you must file issues there, not here.
The D7 version of the contrib CCK package currently contains:
D6 -> D7 data migration code, see Migrating D6 Content Construction Kit (CCK) to D7 Fields for an explanation of how to upgrade your data.
some miscellaneous helpers to do things that core will not do, like maintain the PHP code snippets some fields may have been using to define allowed values (partially working)
The following features are now handled by separate, dedicated projects:
nodereference and userreference : References project - co-maintainer needed
content_permissions: Field permissions module. See this issue for progress on the D7 version.
fieldgroup : Field group module - with much more awesomeness than in D6 !
Yet to be defined, nothing ported yet:
content_copy : The D7 branch of the Features module supports expoting and importing content types and fields in 'feature' modules. There is currently no UI to manually export and import field definitions.
Integration with other modules:
Views - all Views field integration is handled by Views in D7.
Panels - all Panels field integration is handled by Panels in D7.
Token - see the D7 version of the Token module.
Devel - the Devel module will handle field generation code in D7.
Everything else is in Drupal 7 core.
Read More...
www.drupal.org
Drupal 7 and Fields in Core
Most of CCK has moved to core in the Drupal 7 version.
Please note that this is not the place to get support for D7 Fields! We are getting a number of support requests, bug reports, and even feature requests for D7 fields. Fields are in core in D7, you must file issues there, not here.
The D7 version of the contrib CCK package currently contains:
D6 -> D7 data migration code, see Migrating D6 Content Construction Kit (CCK) to D7 Fields for an explanation of how to upgrade your data.
some miscellaneous helpers to do things that core will not do, like maintain the PHP code snippets some fields may have been using to define allowed values (partially working)
The following features are now handled by separate, dedicated projects:
nodereference and userreference : References project - co-maintainer needed
content_permissions: Field permissions module. See this issue for progress on the D7 version.
fieldgroup : Field group module - with much more awesomeness than in D6 !
Yet to be defined, nothing ported yet:
content_copy : The D7 branch of the Features module supports expoting and importing content types and fields in 'feature' modules. There is currently no UI to manually export and import field definitions.
Integration with other modules:
Views - all Views field integration is handled by Views in D7.
Panels - all Panels field integration is handled by Panels in D7.
Token - see the D7 version of the Token module.
Devel - the Devel module will handle field generation code in D7.
Everything else is in Drupal 7 core.
Read More...
www.drupal.org
Tuesday, October 11, 2011
Module- Token
Tokens are small bits of text that can be placed into larger documents via simple placeholders, like %site-name or [user]. The Token module provides a central API for modules to use these tokens, and expose their own token values.
Read More..
www.drupal.org
Monday, October 10, 2011
Module- Views
Drupal 7 note
When installing Views on Drupal 7, you absolutely must have CTools of at least alpha4 and you may need to flush cache as much as twice. There are currently issues with core's cache flushing that means one cache flush isn't necessarily enough. Also, if your CTools' version is older than CTools 7.x-1.0-alpha4 things will crash a lot..
What is Views
The Views module provides a flexible method for Drupal site designers to control how lists and tables of content (nodes in Views 1, almost anything in Views 2) are presented. Traditionally, Drupal has hard-coded most of this, particularly in how taxonomy and tracker lists are formatted.
This tool is essentially a smart query builder that, given enough information, can build the proper query, execute it, and display the results. It has four modes, plus a special mode, and provides an impressive amount of functionality from these modes.
Among other things, Views can be used to generate reports, create summaries, and display collections of images and other content.
Read More....
www.drupal.org
When installing Views on Drupal 7, you absolutely must have CTools of at least alpha4 and you may need to flush cache as much as twice. There are currently issues with core's cache flushing that means one cache flush isn't necessarily enough. Also, if your CTools' version is older than CTools 7.x-1.0-alpha4 things will crash a lot..
What is Views
The Views module provides a flexible method for Drupal site designers to control how lists and tables of content (nodes in Views 1, almost anything in Views 2) are presented. Traditionally, Drupal has hard-coded most of this, particularly in how taxonomy and tracker lists are formatted.
This tool is essentially a smart query builder that, given enough information, can build the proper query, execute it, and display the results. It has four modes, plus a special mode, and provides an impressive amount of functionality from these modes.
Among other things, Views can be used to generate reports, create summaries, and display collections of images and other content.
Read More....
www.drupal.org
Sunday, October 9, 2011
Theming Guide
This handbook is about customizing the look and feel of a Drupal site. We'll show you how you can modify the appearance of your Drupal site without requiring expert knowledge of programming. And if you wish to go further, we cover that too.
This guide assumes some knowledge of HTML and CSS but no PHP programming knowledge is necessary. It also assumes you have administrator's privileges to a Drupal site. You might also want to familiarize yourself with some of the terminology used in Drupal. We concentrate on Drupal 7 with notes for Drupal 6 where applicable.
Other Places to Explore
Installing Themes - To install existing, contributed themes, please visit Installing themes
Contributed Themes - Free Contributed themes at drupal.org. See demos of some of them at Theme Garden.
Custom Themes - Unique custom themes created by Drupal designers that you can hire.
Theming Tutorials - View a number of theming videos which guide you through common scenarios
Support - Having problems? Check the troubleshooting FAQ, ask in the theming forum or contact us on IRC @ #drupal-themes.
Module Developer's Guide - Module developers can consult the module developer's guide, specifically Using the theme layer (Drupal 7.x) and (Drupal 6.x)
HTML and CSS techniques - See the best practices page
Overview
We start with customizing the appearance using an existing theme. You may be surprised how customizable an existing theme can be simply by changing a few settings. From there we discuss ways to make your own theme based on an existing theme, and then show you how to tweak it through the use of CSS stylesheets.
Next we'll explore how to override various theme's parts; regions and node types. We then move onto creating your own theme from scratch; which isn't all that difficult. Finally we'll cover more advanced topics employing PHP coding.
Our concentration throughout this document will be on using preferred techniques. We touch briefly on what's possible but our discussion will center on Drupal's preferred theming engine and best practices. This involves, among other things, copying files and modifying the copies, overriding files with your own versions rather than modifying the originals and housing all your modified theme's files under the sites/all/themes directory. This is a step towards upgrade-proofing your site and facilitates future maintenance.
This entire handbook is currently undergoing a reorganization to help make this information more accessible. Please pardon the dust. Everyone can help with this project. You can find out more information about this reorganization and how to join in on the working group's project page.
About theming
Theming Drupal 6 and 7
Theming Drupal 5
Tools, best practices and conventions
Updating a theme to a new version
More theming resources and guides
Theme HowTos
Theming forms in your theme
Theme snippets
Core themes
Contributed themes
Missing topics
www.drupal.org
This guide assumes some knowledge of HTML and CSS but no PHP programming knowledge is necessary. It also assumes you have administrator's privileges to a Drupal site. You might also want to familiarize yourself with some of the terminology used in Drupal. We concentrate on Drupal 7 with notes for Drupal 6 where applicable.
Other Places to Explore
Installing Themes - To install existing, contributed themes, please visit Installing themes
Contributed Themes - Free Contributed themes at drupal.org. See demos of some of them at Theme Garden.
Custom Themes - Unique custom themes created by Drupal designers that you can hire.
Theming Tutorials - View a number of theming videos which guide you through common scenarios
Support - Having problems? Check the troubleshooting FAQ, ask in the theming forum or contact us on IRC @ #drupal-themes.
Module Developer's Guide - Module developers can consult the module developer's guide, specifically Using the theme layer (Drupal 7.x) and (Drupal 6.x)
HTML and CSS techniques - See the best practices page
Overview
We start with customizing the appearance using an existing theme. You may be surprised how customizable an existing theme can be simply by changing a few settings. From there we discuss ways to make your own theme based on an existing theme, and then show you how to tweak it through the use of CSS stylesheets.
Next we'll explore how to override various theme's parts; regions and node types. We then move onto creating your own theme from scratch; which isn't all that difficult. Finally we'll cover more advanced topics employing PHP coding.
Our concentration throughout this document will be on using preferred techniques. We touch briefly on what's possible but our discussion will center on Drupal's preferred theming engine and best practices. This involves, among other things, copying files and modifying the copies, overriding files with your own versions rather than modifying the originals and housing all your modified theme's files under the sites/all/themes directory. This is a step towards upgrade-proofing your site and facilitates future maintenance.
This entire handbook is currently undergoing a reorganization to help make this information more accessible. Please pardon the dust. Everyone can help with this project. You can find out more information about this reorganization and how to join in on the working group's project page.
About theming
Theming Drupal 6 and 7
Theming Drupal 5
Tools, best practices and conventions
Updating a theme to a new version
More theming resources and guides
Theme HowTos
Theming forms in your theme
Theme snippets
Core themes
Contributed themes
Missing topics
www.drupal.org
Thursday, October 6, 2011
Multilingual Guide
You can configure a website to support more than one language or to support languages other than English (also known as a localized, internationalized or a multilingual website).
Drupal has two core modules which enable translation:
Locale module for user interface elements (built-in system strings such as menu items, form labels, help text, and button labels such as 'Log in', 'Logout', 'Submit', 'View', 'Edit', 'Delete' etc.)
Content translation module for site content (the actual user-created pages, stories, blocks, etc. of the website)
You can extend the functionality of these modules with contributed modules for language and locale. For a proper multilingual menu system and multi-lingual blocks and taxonomy install Internationalization module, and read the related documentation. If you are looking for a quick start, refer to the tutorial called "Basic Internationalization setup".
You can automate translation discovery and updates with the Localization update module. Alternatively, you can also manually import an existing translation through the administration interface:
Drupal 6: Administer > Site Building > Translate Interface > Import (http://example.com/admin/build/translate/import)
Drupal 7: Configuration > Regional and language > Translate Interface > Import (http://example.com/admin/config/regional/translate/import)
To quickly install an already localized version of Drupal (which currently supports over 80 languages), you can use an install profile called Localized Drupal.
For translations for Drupal core, modules and themes see http://localize.drupal.org. If you don't have a translation file for your language, you may need to translate the interface on your own. To contribute localized versions of Drupal, see Translate Drupal to your language in the Getting Involved Guide.
Drupal language-related resources.
Install Drupal in another language
Internationalization issues (besides translation)
Language-specific communities
Drupal local groups directory
Geographical groups directory
Writing code for localized modules? See the Localization API section of the Developing for Drupal guide.
Translating a site interface to different languages (Locale core module)
Translating content to different languages (Content Translation core module)
Contributed modules for language and locale
Other internationalization issues (other than translation)
www.drupal.org
Drupal has two core modules which enable translation:
Locale module for user interface elements (built-in system strings such as menu items, form labels, help text, and button labels such as 'Log in', 'Logout', 'Submit', 'View', 'Edit', 'Delete' etc.)
Content translation module for site content (the actual user-created pages, stories, blocks, etc. of the website)
You can extend the functionality of these modules with contributed modules for language and locale. For a proper multilingual menu system and multi-lingual blocks and taxonomy install Internationalization module, and read the related documentation. If you are looking for a quick start, refer to the tutorial called "Basic Internationalization setup".
You can automate translation discovery and updates with the Localization update module. Alternatively, you can also manually import an existing translation through the administration interface:
Drupal 6: Administer > Site Building > Translate Interface > Import (http://example.com/admin/build/translate/import)
Drupal 7: Configuration > Regional and language > Translate Interface > Import (http://example.com/admin/config/regional/translate/import)
To quickly install an already localized version of Drupal (which currently supports over 80 languages), you can use an install profile called Localized Drupal.
For translations for Drupal core, modules and themes see http://localize.drupal.org. If you don't have a translation file for your language, you may need to translate the interface on your own. To contribute localized versions of Drupal, see Translate Drupal to your language in the Getting Involved Guide.
Drupal language-related resources.
Install Drupal in another language
Internationalization issues (besides translation)
Language-specific communities
Drupal local groups directory
Geographical groups directory
Writing code for localized modules? See the Localization API section of the Developing for Drupal guide.
Translating a site interface to different languages (Locale core module)
Translating content to different languages (Content Translation core module)
Contributed modules for language and locale
Other internationalization issues (other than translation)
www.drupal.org
Wednesday, October 5, 2011
Site Building Guide
This is the customization guide and 'how to' guide for implementing business functionality and features into your Drupal site.
For information on managing the ongoing operation of a Drupal site, see the Administration Guide. For information on developing the basic information architecture using menus, taxonomies, blocks etc, see the Structure Guide.
Best practices
Building the site functionality
Contributed modules
Core modules
Distributions
HowTos
Site builder's toolkit
Site building: beginner, intermediate, advanced
Site recipes
www.drupal.org
For information on managing the ongoing operation of a Drupal site, see the Administration Guide. For information on developing the basic information architecture using menus, taxonomies, blocks etc, see the Structure Guide.
Best practices
Building the site functionality
Contributed modules
Core modules
Distributions
HowTos
Site builder's toolkit
Site building: beginner, intermediate, advanced
Site recipes
www.drupal.org
Tuesday, October 4, 2011
Structure Guide
Welcome to the Drupal Structure Guide. This guide provides comprehensive information on tools and techniques for organising the information architecture of a Drupal site. The guide shows you the fundamentals of organizing your content, making it easy to navigate, and allowing you to direct your users to relevant information.
This book covers topics such as:
Content types
Navigation menus
Blocks
Taxonomies
Views
Panels
Who should read this guide
This book should be read by:
Information architects
Interface designers
Site developers
In other words, anyone who needs to understand the fundamentals of structuring a Drupal site should read this guide.
For information on adding features to a site, see the Site Building Guide.
For information on changing the visual properties of a site, see the Theming Guide.
For information on managing the daily tasks of running a Drupal site, see the Administration Guide.
Working with nodes, content types and fields
Organizing content with taxonomy
Book module: Creating structured documents
Configuring comments
Working with Menus
Working with Views
Working with blocks (content in regions)
Working with links and related content
Working with user profile information
Presenting content to mobile users
Creating complex layouts with Panels
www.drupal.org
This book covers topics such as:
Content types
Navigation menus
Blocks
Taxonomies
Views
Panels
Who should read this guide
This book should be read by:
Information architects
Interface designers
Site developers
In other words, anyone who needs to understand the fundamentals of structuring a Drupal site should read this guide.
For information on adding features to a site, see the Site Building Guide.
For information on changing the visual properties of a site, see the Theming Guide.
For information on managing the daily tasks of running a Drupal site, see the Administration Guide.
Working with nodes, content types and fields
Organizing content with taxonomy
Book module: Creating structured documents
Configuring comments
Working with Menus
Working with Views
Working with blocks (content in regions)
Working with links and related content
Working with user profile information
Presenting content to mobile users
Creating complex layouts with Panels
www.drupal.org
Monday, October 3, 2011
Administration Guide
This guide provides information about the daily or ongoing operation of a Drupal site.
For information on developing the information architecture of a Drupal site, see the Structure Guide. For information about adding features and creating the business logic of a site, see the Site Building Guide.
Getting started with Drupal 7 administration
Getting started with Drupal 6 administration
Site configuration in Drupal 6
Securing your site
Backing up and migrating a site
Launching a site
Managing URLs
Managing content
Managing site performance
Managing users
Monitoring a site
Preparing end user and administrator guides
Upgrading from previous versions
www.drupal.org
For information on developing the information architecture of a Drupal site, see the Structure Guide. For information about adding features and creating the business logic of a site, see the Site Building Guide.
Getting started with Drupal 7 administration
Getting started with Drupal 6 administration
Site configuration in Drupal 6
Securing your site
Backing up and migrating a site
Launching a site
Managing URLs
Managing content
Managing site performance
Managing users
Monitoring a site
Preparing end user and administrator guides
Upgrading from previous versions
www.drupal.org
Sunday, October 2, 2011
Installation guide
Drupal provides an installation script that automatically populates database tables and configures the correct settings in the settings.php file. This section covers preparing for installation, running the installation script itself, and the steps that should be done after running the installation script has completed. It also explains how to do a "multi site" installation, where a number of different Drupal sites run off the same code base.
Before proceeding with your first Drupal installation, you should also review the best practices section. For help with Drupal terms, see the glossary page.
Other tools
Some of the steps in the installation process can be performed with tools such as graphical applications for moving files and managing databases or tools that are provided by your hosting service. This documentation focuses on performing tasks at the command line. For information on using other tools, see the documentation that accompanies the application or is provided by your hosting service.
Creating a test site on a local computer
It is considered a good practice to do all development work on a separate test site before making changes to a production site. A test site allows you to evaluate the impact of upgrades, new modules, modifications to themes etc. without causing disruption to your live site. For information about setting up a web server on a local computer, see the Local Server Setup section of the Developing for Drupal guide.
Alternative methods for installation
Some web hosting companies offer "one-click" installations of Drupal, or specific Drupal support. You may be able to locate one on the Drupal hosting handbook page.
There is also information about Drupal distributions, which include installation profiles and pre-packaged distributions of Drupal and modules. These may be of help as well.
System requirements
Quick install with FTP
Quick install for beginners
Quick install for developers (command line)
Before you begin
Step 1: Download and uncompress Drupal
Step 2: Create the database
Step 3: The settings.php file
Step 4: Run the installation script
After Installation
Troubleshoot installation problems
Advanced and multisite installation
Installation how-to articles
Installing modules and themes
Migrating to Drupal
Installing Drupal on Windows
Using an installation profile
Install Drupal in another language
WWW.drupal.org
Before proceeding with your first Drupal installation, you should also review the best practices section. For help with Drupal terms, see the glossary page.
Other tools
Some of the steps in the installation process can be performed with tools such as graphical applications for moving files and managing databases or tools that are provided by your hosting service. This documentation focuses on performing tasks at the command line. For information on using other tools, see the documentation that accompanies the application or is provided by your hosting service.
Creating a test site on a local computer
It is considered a good practice to do all development work on a separate test site before making changes to a production site. A test site allows you to evaluate the impact of upgrades, new modules, modifications to themes etc. without causing disruption to your live site. For information about setting up a web server on a local computer, see the Local Server Setup section of the Developing for Drupal guide.
Alternative methods for installation
Some web hosting companies offer "one-click" installations of Drupal, or specific Drupal support. You may be able to locate one on the Drupal hosting handbook page.
There is also information about Drupal distributions, which include installation profiles and pre-packaged distributions of Drupal and modules. These may be of help as well.
System requirements
Quick install with FTP
Quick install for beginners
Quick install for developers (command line)
Before you begin
Step 1: Download and uncompress Drupal
Step 2: Create the database
Step 3: The settings.php file
Step 4: Run the installation script
After Installation
Troubleshoot installation problems
Advanced and multisite installation
Installation how-to articles
Installing modules and themes
Migrating to Drupal
Installing Drupal on Windows
Using an installation profile
Install Drupal in another language
WWW.drupal.org
Saturday, October 1, 2011
Understanding Drupal
Welcome to Drupal! Drupal is a powerful content management system, meaning you can power many different types of websites with it without knowing any coding languages.
If you're new to Drupal or having your own website, then this guide is for you.
The beginning is the most important part of the work - Plato
The following pages should introduce you to the Drupal project, some best practices the community has accumulated, the concepts and technologies that underpin Drupal, and basic installation and configuration.
The Drupal documentation is currently being restructured. Some content has been moved to the Administration Guide, Structure Guide and Site Building Guide.
If you need help installing Drupal, the Installation Guide has step by step instructions and troubleshooting tips.
Drupal concepts
Glossary
Technology stack
Is Drupal secure?
Choosing a Drupal version
Books about Drupal
Third party resources
Tips on using the documentation
www.drupal.org
If you're new to Drupal or having your own website, then this guide is for you.
The beginning is the most important part of the work - Plato
The following pages should introduce you to the Drupal project, some best practices the community has accumulated, the concepts and technologies that underpin Drupal, and basic installation and configuration.
The Drupal documentation is currently being restructured. Some content has been moved to the Administration Guide, Structure Guide and Site Building Guide.
If you need help installing Drupal, the Installation Guide has step by step instructions and troubleshooting tips.
Drupal concepts
Glossary
Technology stack
Is Drupal secure?
Choosing a Drupal version
Books about Drupal
Third party resources
Tips on using the documentation
www.drupal.org
Subscribe to:
Posts (Atom)