Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote> <i> <b> <img> <div> <span> <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <embed> <object> <param> <strike> <caption> <iframe>

This site allows HTML content. While learning all of HTML may feel intimidating, learning how to use a very small number of the most basic HTML "tags" is very easy. This table provides examples for each tag that is enabled on this site.

For more information see W3C's HTML Specifications or use your favorite search engine to find other sites that explain HTML.

Preformatted

Most unusual characters can be directly entered without any problems.

If you do encounter problems, try using HTML character entities. A common example looks like &amp; for an ampersand & character. For a full list of entities see HTML's entities page. Some of the available characters include:

Using custom PHP code

Custom PHP code may be embedded in some types of site content, including posts and blocks. While embedding PHP code inside a post or block is a powerful and flexible feature when used by a trusted user with PHP experience, it is a significant and dangerous security risk when used improperly. Even a small mistake when posting PHP code may accidentally compromise your site.

If you are unfamiliar with PHP, SQL, or Drupal, avoid using custom PHP code within posts. Experimenting with PHP may corrupt your database, render your site inoperable, or significantly compromise security.

Notes:

• Remember to double-check each line for syntax and logic errors before saving.
• Statements must be correctly terminated with semicolons.
• Global variables used within your PHP code retain their values after your script executes.
• register_globals is turned off. If you need to use forms, understand and use the functions in the Drupal Form API.
• Use a print or return statement in your code to output content.
• Develop and test your PHP code using a separate test script and sample database before deploying on a production site.
• Consider including your custom PHP code within a site-specific module or template.php file rather than embedding it directly into a post or block.
• Be aware that the ability to embed PHP code within content is provided by the PHP Filter module. If this module is disabled or deleted, then blocks and posts with embedded PHP may display, rather than execute, the PHP code.

A basic example: Creating a "Welcome" block that greets visitors with a simple message.

• Add a custom block to your site, named "Welcome". With its input format set to "PHP code" (or another format supporting PHP input), add the following in the Block body:

  print t('Welcome visitor! Thank you for visiting.');
  

• To display the name of a registered user, use this instead:

  global $user;
  if ($user->uid) {
    print t('Welcome @name! Thank you for visiting.', array('@name' => $user->name));
  }
  else {
    print t('Welcome visitor! Thank you for visiting.');
  }
  

Drupal.org offers some example PHP snippets, or you can create your own with some PHP experience and knowledge of the Drupal system.

Quoted content can be placed between [quote] tags in order to be displayed as an indented quote. Every [quote] tag must have a corresponding [/quote] tag. For example:

[quote]This is a simple quote.[/quote]

Additionally, there is an optional attribute which allows quotes to specify the original author.

[quote=Mr. Drupal]This is a quote with an attribution line.[/quote]

Finally, multiple [quote] tags can be nested within one another. Just remember that every [quote] tag must have a corresponding [/quote] tag.

[quote]I think she says it best...
[quote=Ms. Quotation]This is a quote nested within another quote.[/quote]
but you can't argue with
[quote=Ms. Reply]The more quotes, the merrier.
Just don't get too carried away.[/quote]
And I have nothing more to say.[/quote]