|
|
Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
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.
| Tag Description | You Type | You Get |
|---|---|---|
| Anchors are used to make links to other pages. | <a href="http://movie.acerainbow.com">Ace Rainbow</a> | Ace Rainbow |
| Emphasized | <em>Emphasized</em> | Emphasized |
| Strong | <strong>Strong</strong> | Strong |
| Cited | <cite>Cited</cite> | Cited |
| Coded text used to show programming source code | <code>Coded</code> | Coded |
| Unordered list - use the <li> to begin each list item | <ul> <li>First item</li> <li>Second item</li> </ul> |
|
| Ordered list - use the <li> to begin each list item | <ol> <li>First item</li> <li>Second item</li> </ol> |
|
| Definition lists are similar to other HTML lists. <dl> begins the definition list, <dt> begins the definition term and <dd> begins the definition description. | <dl> <dt>First term</dt> <dd>First definition</dd> <dt>Second term</dt> <dd>Second definition</dd> </dl> |
|
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 & for an ampersand & character. For a full list of entities see HTML's entities page. Some of the available characters include:
| Character Description | You Type | You Get |
|---|---|---|
| Ampersand | & | & |
| Greater than | > | > |
| Less than | < | < |
| Quotation mark | " | " |
Linodef is a filter for internal links. It uses a simple but unique markup so Linodef doesn't interfere with other filter modules.
The ID of a node or of a taxonomy term and optionally a fieldname are the solely elements stored in your text. One advantage of this method in comparison to similar filter modules is the fact that the links don't break if you change the node title or term name. Furthermore, if you change the title of the node or the value of a field or the name of a term then those are automatically updated in your text, too.
To embed elements into your text, prepend the element ID with the hash key # and surround them by brackets []: [#ID]. That way a node title is inserted and linked. To embed the content of a field, add the field name: [#ID:field_name]. Moreover it is possible to add a field value number in the case you have a field with multiple values and want to use a different value than the first: [#ID:field_name:number].
The syntax is as following:
| Tag Description | You Type | You Get |
|---|---|---|
| Embed node title and link to the node. | [#ID] | node title |
| Embed field value and link to the node. | [#ID:field_name] | field value |
| Embed field value and link to the node. | [#ID:field_name:field_value_number] | certain field value of a multiple values field |
| You Type | You Get |
|---|---|
[#8] | Perry Rhodan |
[#8:field_firstnames] | Gucky |
[#8:field_firstnames:0] | Gucky |
[#8:field_firstnames:1] | Atlan |
Options set the ID type (embedded element type) and the embed method. They are entered right after the ID or the field settings and are separated by a comma. The number of options a tag can have is not limited.
| Tag Description | You Type | You Get |
|---|---|---|
| Embed an element with options. | [#ID,option1,option2="optionvalue",...] | Depends on the options used. |
| Embed a field value with options. | [#ID:field_name,option1,option2="optionvalue",...] | Depends on the options used. |
| Embed a certain field value with options. | [#ID:field_name:field_value_number,option1,option2="optionvalue",...] | Depends on the options used. |
Here we use the modification "nolink" to have an output without a link to the element and the ID type option "tid" to embed a taxonomy term instead of a node. The taxonomy term has the id=5 and the name Jupiter. If the term has a path alias then the link contains this instead of the default drupal path (the example is limited to the default path). Furthermore we have a node (optional option "nid") with id=5 and the title Kallisto.
| You Type | You Get |
|---|---|
[#5,tid] | Jupiter |
[#5,tid,nolink] | Jupiter |
[#5,nid,nolink] | Kallisto |
[#5,nolink] | Kallisto |
Comments act as an indicator for Linodef tags, to describe your tag for yourself or other editors. A comment can be inserted inside the tag prepended with a space and it may consist of all UTF-8 characters except the closing bracket ].
Comments are visible only during editing and never appear by viewing a text. The nature of comments is that they must not modified automatically and therefore will not change unless you change it. This is important to understand since the content the tag displays can change automatically and so the comment may be outdated. So try to use a common description.
| Tag Description | You Type | You Get |
|---|---|---|
| Use comments to give information about the tag during editing. | [#ID comment] | node title |
| Comment a field content. | [#ID:field_name:field_value_number comment] | node title |
| Comments work together with options. | [#ID:field_name:field_value_number,option1,option2="optionvalue",... comment] | Depends on the options used. |
Use the option "linktext" to create links to elements using a custom text: [#ID,linktext="your Text"]
| You Type | You Get |
|---|---|
[#8,linktext="your Text"] | your Text |
