Module - CKEditor - WYSIWYG HTML editor

This module will allow Drupal to replace textarea fields with the CKEditor - a visual HTML editor, sometimes called WYSIWYG editor. This HTML text editor brings many of the powerful WYSIWYG editing functions of known desktop editors like Word to the web. It's very fast and doesn't require any kind of installation on the client computer.

What is CKEditor?

CKEditor is the next version of FCKeditor. The editor has been rebranded and completely rewritten. It is now much faster (the code has been optimized), loads faster (the number of files has been reduced, so the browser will perform less HTTP requests) and developers friendly.

Read More 
www.ckeditor.com/ckeditor-for-drupal 
www.drupal.org/project/imce
www.drupal.org

page.tpl.php

General utility variables:

• $base_path: The base URL path of the Drupal installation. At the very least, this will always default to /.
• $css: An array of CSS files for the current page.
• $directory: The directory the theme is located in, e.g. themes/garland or themes/garland/minelli.
• $is_front: TRUE if the current page is the front page.
• $logged_in: TRUE if the user is registered and signed in.
• $is_admin: TRUE if the user has permission to access administration pages.

Read More

www.drupal.org

Drupal Accessibility Statement

As an inclusive community, we are committed to making sure that Drupal is an accessible tool for building websites and that Drupal helps you create websites that are themselves accessible.

This initiative started with advancements with Drupal 7 accessibility. We have committed to ensuring that all features of Drupal core conform with the Worldwide Web Consortium (W3C) guidelines: WCAG 2.0 and ATAG 2.0. Where possible we will also update the previous version of Drupal core, version 6, to enhance its accessibility.

Accessible Features in Drupal

If you rely on a screen reader or other assistive technology, you will be glad to know that we have built Drupal to encourage and support the proper use of semantic markup. For example, you should be able to use headings reliably for page-level navigation.

The accessibility team has worked to identify barriers to accessibility with Drupal and worked to resolve them. We've identified and resolved a number of issues in the core code of Drupal 7 and raised awareness within the community. We've added some additional support for Rich Internet Applications by adding some WAI-ARIA support. There have been many improvements to both the visitor and administrator sides of Drupal, especially:

• Search engine form and presentation
• Drag and Drop functionality
• Color contrast and intensity
• Adding skip navigation to core themes
• Image handling
• Form labeling
• Removing duplicate or null tags

Read More

www.drupal.org

Module - Visitors

This module used for displaying a visitors info.

Reports

• View pages that have recently been visited.
• View pages that have been hit frequently.
• View pages count per month.
• View pages count per day of month.
• View pages count per day of week.
• View pages count per hour.
• View pages count per host.
• View access log.
• View user activity report (hits, nodes, comments).
• View referer list.

Visitors Block

• Total Visitors.
• Unique Visitor.
• Registered Users.
• Last Registered User.
• Published Nodes.
• Your IP.

Read More

www.drupal.org

Module Counter

Counter module counts how many visitors on your website. This module provides real time counting. All data saved to database.
Features:

• Count Site Counter per day, minute even second!
• Count Unique Visitor
• Count Registered and Unregistered User
• Count Published and unpublised Node
• Display Web Server IP and Client IP
• Report: Client IP, Access Date, Access Page
• Initial values
• Visitor Statistic per day, week, month and year!

Read More
www.drupal.org

How the Drupal theme system works

A theme is a collection of files that define the presentation layer. You can also create one or more "sub-themes" or variations on a theme. Only the .info file is required, but most themes and sub-themes will use other files as well. The following diagram illustrates the files that are found in a typical theme and sub-theme.
Drupal 6

theming requirements
Drupal 7

theming requirements

.info (required)

All that is required for Drupal to see your theme is a ".info" file. Should the theme require them, meta data, style sheets, JavaScripts, block regions and more can be defined here. Everything else is optional.

The internal name of the theme is also derived from this file. For example, if it is named "drop.info", then Drupal will see the name of the theme as "drop". Drupal 5 and below used the name of the enclosing folder of the theme.

Info files for themes are new in Drupal 6. In version 5, .info files were used solely for modules.
template files (.tpl.php)

These templates are used for the (x)HTML markup and PHP variables. In some situations they may output other types of data --xml rss for example. Each .tpl.php file handles the output of a specific themable chunk of data, and in some situations it can handle multiple .tpl.php files through suggestions. They are optional, and if none exists in your theme it will fall back to the default output. Refrain from having complex logic in these files. In most cases, it should be straight (x)HTML tags and PHP variables. A handful of these templates exist in directories where core and contributed modules exist. Copying them to your theme folder will force Drupal to read your version.

Note: The theme registry caches information about the available theming data. You must reset it when adding or removing template files or theme functions from your theme.
template.php

For all the conditional logic and data processing of the output, there is the template.php file. It is not required, but to keep the .tpl.php files tidy it can be used to hold preprocessors for generating variables before they are merged with the markup inside .tpl.php files. Custom functions, overriding theme functions or any other customization of the raw output should also be done here. This file must start with a PHP opening tag "http://drupal.org/node/337173

Module: - ImageCache

ImageCache allows you to setup presets for image processing. If an ImageCache derivative doesn't exist the web server's rewrite rules will pass the request to Drupal which in turn hands it off to ImageCache to dynamically generate the file.

http://drupal.org/project/imagecache