A wiki is a web site where any users with access can collaborate and edit the web site directly using a simplified markup language. You create and modify wiki topics in a simple markup language within a web browser.

In WEM, a single wiki page is called a topic and a collection of topics is called a wiki space. You can create multiple wiki spaces. Permissions determine who can read or change the content of the wiki space. You can search across a wiki space as well as create topics on the fly. In addition, you can add attachments to wiki topics.

This section describes wiki concepts and describes how to use the provided wiki functionality.

Creating a wiki space

To add a wiki to your website, simply go to the Website Console and copy the Wiki Content (/content/wiki) to the location in your site structure where you want to start the new wiki space.

  1. Open the Websites Console.
  2. Copy the Wiki Content structure from /content/wiki to where you want to create a wiki.
  3. Rename the newly created wiki space by changing its title as appropriate.
  4. Open the main page of the newly created wiki. 
file

Modifying wiki topics

After you create a wiki space you can edit the main topic (or any new topics you may have created).

To modify a wiki topic:

  1. In the Websites Console, navigate to the page where you have started your wiki.
  2. Click the Edit tab and edit the wiki page, using the wiki syntax for simple formatting.
    • You can switch between Wysiwyg and Wiki text edit mode by clicking Convert to Wysiwyg/WIKI-text in Advanced Operations. Both edit modes provide formatting shortcuts.
    • Optionally, in the topic title field you can enter a new name for the topic. If you do not type a name, the title will automatically be used as topic name for this wiki page.
  3. Click Save to persist your changes or, to save the page without notifying subscribed users of the change, click Quiet Save. Click Preview to see what your page looks like before saving (all changes are saved in the wiki page's history).
file

Creating wiki topics

After you create a wiki space you can also create new topics by either:

Deleting wiki topics

You can delete wiki topics and spaces by either entirely removing them from the system or archiving them in the attic.

To delete a wiki topic or space:

  1. Navigate to the wiki topic that you want to delete.
  2. Click the Edit tab.
  3. Below the textarea, under Advanced Operations, click Delete. WEM requests confirmation that you want to delete and recommends that you archive the topic in the attic.
  4. To move the topic to the attic, click Delete. To delete the page entirely, clear the Attic check box and click Delete. You can also click Cancel to keep the topic.

Renaming and/or moving wiki topics

To rename or move a wiki topic:

  1. Navigate to the wiki topic that you want to rename or move.
  2. Click the Edit tab.
  3. Below the textarea, under Advanced Operations, click Move/Rename.
  4. To change the name of the topic, type a new name in the New Name field.
  5. To move a topic, select a new parent from the New Topic Parent list. To move subtopics with the main topic, select the Move subtopics check box.
  6. Click Rename to make the change. If you make a mistake, you can click Reset to revert to current settings or click Cancel to close the Rename page.

Modifying topic properties

To modify topic properties:

  1. Navigate to the wiki topic that you want to modify properties for.
  2. Click the Edit tab.
  3. Below the textarea, under Advanced Operations, click Edit topic properties.
  4. Make changes to the topic properties and click Apply to save them or Cancel to ignore them. See Environment Variables for information on how to use and include environment variables in topic pages.

Adding attachments to topics

To add an attachment to a topic:

  1. Navigate to the wiki topic that you want to attach files to.
  2. Click the Attachments tab.
  3. Click Browse to upload a local file.
    • If you want the attachments to be listed on the topic page, select the check box in Display Options.
    • If you want to create a link to the attached file, select the check box in the Attach new file.
  4. Click Upload to upload the attachment.
file

Viewing topic history

To view changes made to a particular wiki topic:

  1. Navigate to the wiki topic that you want to view the history for.
  2. Click the History tab. WEM displays any changes that were made to the topic and saved.
file

Subscribing to and unsubscribing from topics

To subscribe to a topic whenever changes are made:

  1. Navigate to the wiki topic you want to subscribe to.
  2. Click the History tab.
  3. Click the subscribe to this topic link. If you are subscribed to a topic, the link changes to unsubscribe from this topic. Click the link to unsubscribe.

Wiki Syntax

The following section describes wiki syntax, including the following:

Simple Formatting

Simple formatting includes the commands you need to format your wiki text.

Paragraph and Linebreak

For a new paragraph, just insert an empty line. So this is on a new paragraph. For an explicit\\ line break, add two {{\\}}.

displays as:

For a new paragraph, just insert an empty line.

So this is on a new paragraph. For an explicit

line break, add two \\.

Bold

This is **bold text**.

displays as:

This is bold text.

Italics

This is //italic text//.

displays as:

This is italic text.

Underline

This is __underlined text__.

displays as:

This is underlined text.

Strikethrough

This is --deleted text--.

displays as:

This is deleted text.

Superscript and Subscript

Water is also known as H,,2,,O. Einstein says: E = mc^^2^^.

displays as:

Water is also known as H2O.

Einstein says: E = mc2.

Small Fonts

This is ((small text)).

displays as:

This is small text.

Monospaced

Please delete the file ==test.bak==.

displays as:

Please delete the file test.bak.

Combined Formattings

This is **//bold and italic text//**. Einstein says: ==**e = mc^^2^^**==.

displays as:

This is bold and italic text.

Einstein says: e = mc2.

Escaping

This is a {{{single **line** escape}}} {{{ And this **is** a multiline __escape__. }}} Further, a tilde ~~ escapes all special formattings, like ~**bold~** or ~WikiWords.

displays as:

This is a single **line** escape

And this **is** a multiline __escape__.

Further, a tilde ~ escapes all special formattings, like **bold** or WikiWords.

Boxes, Code, and Pre

If you use the multiline escaping mentioned previously ({{{...}}}), the output is a simple <pre>...</pre> with no special style.

If you want to display a code example, use the @@ formatting. This generates a <pre><code>...</code></pre> block with a box around it. For convenience, the first linefeed after the @@ marker is removed from the output.

file

displays as:

public int hashCode() {
int h = hash;
if (h == 0) {
int off = offset;
char val[] = value;
int len = count;
for (int i = 0; i < len; i++) {
h = 31*h + val[off++];
}
hash = h;
}
return h;
}
@@ with preceeding whitespaces, does not close this block.

If the @@ pair is on a single line, the <pre> is omitted:

Example: In java, @@System.out.println("Hello, world");@@ outputs ==Hello, world== on the console.

displays as:

Example: In java, System.out.println("Hello, world"); outputs Hello, world on the console.

If you just need a box, use the @@@ formatting.

@@@ This example is surrounded by a box,\\ that also can span multiple paragraphs. @@@

displays as:

This example is surrounded by a box,

that also can span


multiple


paragraphs.

Indentation (blockquote)

Lines with starting > characters are blockwise indented: > This is indented once, >> and this is indented twice, >>> and so on... > Of course this is properly nested. : Alternatively, you can use colons ":" for :: indentation.

displays as:

Lines with starting > characters are blockwise indented:

 

This is indented once,

 

and this is indented twice,

 

and so on...

 

Of course this is properly nested.

Alternatively, you can use colons ":" for

indentation.

 

Horizontal Rule (hr)

To insert a horizontal rule, just put 3 or more dahes on a single line: ---

displays as:


Linking and Images

This section describes the various ways you can link in the wiki including using WikiWords, internal linking, external linking, and anchors. Images and images with links are also described.

WikiWords

The easiest way to link topics is to use WikiWords. WikiWords must start with an uppercase letter and then have either consecutive uppercase letters terminated with a lowercase letter or have a "camelcase" letter, that is, they have intercaps. Numbers count as both lower- and uppercase letters.

Valid Wiki Words:

  • TestCase
  • TESTCase
  • TestCase1
  • CQ355
  • Test1

Not Wiki Words:

  • testcase
  • TEST
  • Testcase
  • cq355
  • com.day.wiki.parser.Test.Case
  • No

You can escape WikiWords by either preceeding them with a ~ or an !. If you need an ! before a wiki word, you need to escape it.

~NoLinking or !NoLinking. But ~!YesLinking.

displays as:

NoLinking or NoLinking. But !YesLinking.

Internal Linking

If the name of a topic is not a wiki word, you can explicitly link to it, using the link markup. There are alternative link markup styles to comply with most of other wiki syntaxes. Internal links can also contain a WikiSpace reference.

This links [to_here].

This links [[to_here]].

This links to another space [Sandbox.TestTopic].

 

This links [to_here|Here].

This links [[to_here|Here]].

This links [[to_here][Here]].

 

displays as:

file

Anchors

To create an anchor, preceed a word by a # sign.

In the [#Anchor1|section] mentioned below...

#Anchor1 The section with the anchor.

displays as:

file

Note

All headings automatically create an anchor tag by mangling the characters of their heading text. View the generated html in order to retrieve the exact label.

External Links

External links follow the same syntax as internal ones. just use a full qualified URL or an absolute path to a resource.

Welcome to [http://www.day.com|DAY].

Click [/admin|here] for the servlet engine console.

displays as:

file

Images

Use double curly brackets to specify an image source.

Smiley: {{smiley.jpg}}

Image with alt text: {{corrupt.jpg|Corrupt Image}}

displays as:

file

Images in links

Consequently, you can use images in links:

Click here for a smile [http://en.wikipedia.org/wiki/Smile|{{smiley.jpg}}]

displays as:

file

Email

Sent mail to [mailto:sheriff@day.com].

Sent mail to [mailto:sheriff@day.com|the sheriff.]

displays as:

Sent mail to sheriff@day.com.

Sent mail to the sheriff.

Lists

This section describes the syntax for ordered, unordered, and definition lists.

Unordered Lists (ul)

Unordered list items start with consecutive asterisks * followed by a whitespace. The number of asterisks indicate the indentation level. Preceeding whitespaces are ignored and can be used to indent the lists nicely in wiki-text. To create a multiline item, use the linebreak \\ markup.

* List Item Level 1
* List Item Level 1
** List Item Level 2
*** List Item Level 3\\
This continues on the 2^^nd^^ line.
*** List Item Level 3 @@
Some sample
code that lives inside
the list.
@@
*** List Item Level 3
* List Item Level 1

displays as:

  • List Item Level 1
  • List Item Level 1
    • List Item Level 2
      • List Item Level 3

        This continues on the 2nd line.
      • List Item Level 3
        Some sample code that lives inside the list. 
      • List Item Level 3
  • List Item Level 1

Ordered Lists (ol)

Ordered lists work the same way as unordered lists, but they use the hash # character for indentation. Ordered and unordered lists can also be combined.

# Item 1
# Item 2
## Item 2.1
## Item 2.2
### Item 2.2.1
**** Unordered Item
**** Unordered Item
# Item 3

displays as:

  1. Item 1
  2. Item 2
    1. Item 2.1
    2. Item 2.2
      1. Item 2.2.1
        • Unordered Item
        • Unordered Item
  3. Item 3

Definition Lists (dl)

Definition list terms start with a semicolon ; followed by a colon : followed by the definition.

; Coffee : Black hot drink ; Milk : White cold drink

displays as:

Coffee
Black hot drink
Milk
White cold drink

Headings

Headings start with consecutive equal = characters. The number of characters specify the heading level. Closing equal characters are nice but unnecessary. Alternatively you can use TWiki syntax. If the heading markup is directly followed by 2 !!, the heading does not appear in the TOC.

==== Heading 4 Example ====
---++++ ~TWiki Heading 4 Example

====!! Heading 4 Example (no toc) ====
---++++!! ~TWiki Heading 4 Example (no toc)

displays as:

Heading 4 Example

TWiki Heading 4 Example

Heading 4 Example (no toc)

TWiki Heading 4 Example (no toc)

Tables

Tables are built with bar | characters. Each table cell is built with the contents between 2 bars. To create cells that span several columns use consecutive bars. To create cells that span several rows, use a ^ character in the empty rows. Table headers are either created with * markup around the text or by a = that directly follows the |.

| *A* | *B* | *C* | *D* |
| A1 | B1 | C1 | D1 |
|| AB2 | C2 | D2 |
| A3 | B3 | C345 | D3 |
| A4 | B4 |^ | D4 |
| A567 | B5 |^ | D5 |
|^ | B6 | C6 | D6 |
|^ || BC789 | D7 |
| A8 ||^ | D89 |
| A9 ||^ |^ |

displays as:

file

The alignment of the cell is determined by the spacing between the | and the cell text. Use 0 or 1 space to align the cell left, 2 spaces to center the cell and 3 or more spaces to right align the cell.

|= Country |= Population | 
| Switzerland | 7.5 Mio | 
| Italy | 58.1 Mio | 
| Germany | 82.4 Mio |

displays as:

file

Environment Variables

There are four environment scopes that define variables:

  1. text - The text scope contains the variables that are defined just within the wiki text. 
  2. topic - The topic scope contains the variables that are defined for that topic.
  3. space - The space scope contains the variables of this topic and all ancestor topics up to the topic-space, that is, all the properties of all topics you see in the trail.
  4. global - The global scope contains the variables of globally defined properties.
  5. all - Not really a scope, just represents a holistic view of all scopes, where the global is overlayed by the space by the topic by the text scope.

Defining a variable

To define a variable, use the <wiki:set/> tag. This variable will always be defined in the text scope.

<wiki:set name="myvar">Hello **world**.</wiki:set>

Dumping an environment

To dump an environment, use the <wiki:env/> tag.

__**Text Scope**__\\
<wiki:env scope="text"/>\\
__**Topic Scope**__\\
<wiki:env scope="topic"/>\\
__**Space Scope**__\\
<wiki:env scope="space"/>\\
__**Global Scope**__\\
<wiki:env scope="global"/>\\
__**//all// Scope**__\\
<wiki:env scope="all"/>

displays as:

Text scope

Name Value
GOOGLE [http://www.google.com/search?q=%var.args%|%var.args%]
LINK <a href="%var.args.0%">%var.args.1%</a>
loop Recursive %loop%
me.email somebody@day.com
me.fullname Some Body
me.home /content/wiki/Users/sbody
me.userid sbody
myvar Hello **world**.
product.company Day Software
product.copy &copy; 2010 by %product.company%
wiki.docroot /apps/wiki/docroot
wiki.prefix  
wiki.url http://wiki.day.com
wiki.version 1.0.0.SNAPSHOT.20090107

Topic Scope

Name Value
topic.attachments WikiSyntax/wiki:attachments
topic.name WikiSyntax
topic.parent.path /apps/wiki/content/Wiki
topic.path /apps/wiki/content/Wiki/WikiSyntax
topic.space Wiki
topic.title  
topic.uuid ce14f39d-7686-40fc-8fdc-8071358d80b3

Space scope

Name Value
APACHE_JIRA [%jira.url%/%var.args%|{{%bugzilla.icon%}}&nbsp;%var.args%]
ATTACHURLPATH %topic.attachments%
BC <div><iframe src="http://mis-info.day.com/card.php?user=%topic.name%" width="510" frameborder="0" height="320"></iframe></div>
BUG {{%bugzilla.icon%}}&nbsp;<a href='%bugzilla.url%%var.args%' target='_new'>Bug #%var.args%</a>
CQ Communiqu&eacute;
DAM [http://dam.day.com/dam/home?media=content/%var.args%|%var.args% in DAM]
JCR JCR {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/JCR-%var.args%' target='_new'>JCR-%var.args%</a>
JIRA {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/%var.args%' target='_new'>%var.args%</a>
RECENT_CHANGES <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes below %topic.name%:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path%//element(*, wiki:Topic) order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
RECENT_CHANGES_THIS <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes of this page:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path% order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
SLING {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/SLING-%var.args%' target='_new'>SLING-%var.args%</a>
SPREADSHEET <script>document.write(String.fromCharCode(60) + "iframe width='100%' height='500' frameborder='0' src='ht"+"t"+"p"+":"+"/"+"/"+"spreadsheets.google.com/a/day.com/pub?key=pyj5rBGg3r4QvsPU-jwSCHg&output=html&gid=0widget=true'>"+String.fromCharCode(60)+"/iframe>");</script>
TOC <wiki:toc/>
bugzilla.icon %wiki.docroot%/bug_small.png
bugzilla.url http://bugs.day.com/bugzilla/show_bug.cgi?id=
jira.url https://issues.apache.org/jira/browse
topic.name WikiSyntax
topic.parent.path /apps/wiki/content/Wiki
topic.path /apps/wiki/content/Wiki/WikiSyntax
topic.space Wiki
topic.title  
topic.uuid ce14f39d-7686-40fc-8fdc-8071358d80b3
wiki.docroot %wiki.prefix%/apps/wiki/docroot
wiki.prefix  

Global scope

Name Value
APACHE_JIRA [%jira.url%/%var.args%|{{%bugzilla.icon%}}&nbsp;%var.args%]
ATTACHURLPATH %topic.attachments%
BC <div><iframe src="http://mis-info.day.com/card.php?user=%topic.name%" width="510" frameborder="0" height="320"></iframe></div>
BUG {{%bugzilla.icon%}}&nbsp;<a href='%bugzilla.url%%var.args%' target='_new'>Bug #%var.args%</a>
CQ Communiqu&eacute;
DAM [http://dam.day.com/dam/home?media=content/%var.args%|%var.args% in DAM]
H %ICON{help}%
ICON {{%wiki.prefix%/apps/wiki/content/Wiki/WikiIcons/wiki:attachments/%var.args%.gif|%var.args%}}
JCR {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/JCR-%var.args%' target='_new'>JCR-%var.args%</a>
JIRA {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/%var.args%' target='_new'>%var.args%</a>
N %ICON{new}%
P %ICON{pencil}%
RECENT_CHANGES <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes below %topic.name%:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path%//element(*, wiki:Topic) order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
RECENT_CHANGES_THIS <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes of this page:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path% order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
S %ICON{starred}%
SLING {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/SLING-%var.args%' target='_new'>SLING-%var.args%</a>
SPREADSHEET <script>document.write(String.fromCharCode(60) + "iframe width='100%' height='500' frameborder='0' src='ht"+"t"+"p"+":"+"/"+"/"+"spreadsheets.google.com/a/day.com/pub?key=pyj5rBGg3r4QvsPU-jwSCHg&output=html&gid=0widget=true'>"+String.fromCharCode(60)+"/iframe>");</script>
T %ICON{tip}%
TOC <wiki:toc/>
TODO %ICON{todo}%
W %ICON{warning}%
Y %ICON{choice-yes}%
bugzilla.icon %wiki.docroot%/bug_small.png
bugzilla.url http://bugs.day.com/bugzilla/show_bug.cgi?id=
jira.url https://issues.apache.org/jira/browse
wiki.docroot %wiki.prefix%/apps/wiki/docroot
wiki.prefix  

all scope

Name Value
APACHE_JIRA [%jira.url%/%var.args%|{{%bugzilla.icon%}}&nbsp;%var.args%]
ATTACHURLPATH %topic.attachments%
BC <div><iframe src="http://mis-info.day.com/card.php?user=%topic.name%" width="510" frameborder="0" height="320"></iframe></div>
BUG {{%bugzilla.icon%}}&nbsp;<a href='%bugzilla.url%%var.args%' target='_new'>Bug #%var.args%</a>
CQ Communiqu&eacute;
DAM [http://dam.day.com/dam/home?media=content/%var.args%|%var.args% in DAM]
GOOGLE [http://www.google.com/search?q=%var.args%|%var.args%]
H %ICON{help}%
ICON {{%wiki.prefix%/apps/wiki/content/Wiki/WikiIcons/wiki:attachments/%var.args%.gif|%var.args%}}
JCR {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/JCR-%var.args%' target='_new'>JCR-%var.args%</a>
JIRA {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/%var.args%' target='_new'>%var.args%</a>
LINK <a href="%var.args.0%">%var.args.1%</a>
N %ICON{new}%
P %ICON{pencil}%
RECENT_CHANGES <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes below %topic.name%:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path%//element(*, wiki:Topic) order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
RECENT_CHANGES_THIS <div style="float:right; width: 300px; border: 1px solid grey; background-color:#ddd; padding: 5px; font-size:10pt;"><strong style="font-size:10pt">Recent changes of this page:</strong><!-- Note that // should be descendant-or-self and thus include the current topic in the result - but as it is implemented only as descendant in CRX/Jackrabbit, this does not work. --><wiki:search jcrQuery="/%topic.path% order by @wiki:lastModified descending" numResults="10"><wiki:searchResults> [<wiki:get name="result.topic.path"/>|<wiki:get name="result.topic.displayTitle"/>] <address style="font-size:8pt"> <wiki:get name="result.topic.lastModified"/> by [<wiki:get name="result.topic.lastModifiedBy"/>] </address> </wiki:searchResults></wiki:search></div>
S %ICON{starred}%
SLING {{%bugzilla.icon%}}&nbsp;<a href='%jira.url%/SLING-%var.args%' target='_new'>SLING-%var.args%</a>
SPREADSHEET <script>document.write(String.fromCharCode(60) + "iframe width='100%' height='500' frameborder='0' src='ht"+"t"+"p"+":"+"/"+"/"+"spreadsheets.google.com/a/day.com/pub?key=pyj5rBGg3r4QvsPU-jwSCHg&output=html&gid=0widget=true'>"+String.fromCharCode(60)+"/iframe>");</script>
T %ICON{tip}%
TOC <wiki:toc/>
TODO %ICON{todo}%
W %ICON{warning}%
Y %ICON{choice-yes}%
bugzilla.icon %wiki.docroot%/bug_small.png
bugzilla.url http://bugs.day.com/bugzilla/show_bug.cgi?id=
jira.url https://issues.apache.org/jira/browse
loop Recursive %loop%
me.email somebody@day.com
me.fullname Some Body
me.home /content/wiki/Users/sbody
me.userid sbody
myvar Hello **world**.
product.company Day Software
product.copy &copy; 2007 by %product.company%
topic.attachments WikiSyntax/wiki:attachments
topic.name WikiSyntax
topic.parent.path /apps/wiki/content/Wiki
topic.path /apps/wiki/content/Wiki/WikiSyntax
topic.space Wiki
topic.title  
topic.uuid ce14f39d-7686-40fc-8fdc-8071358d80b3
wiki.docroot /apps/wiki/docroot
wiki.prefix  
wiki.url http://wiki.day.com
wiki.version 1.0.0.SNAPSHOT.20090107

Dumping a variable

To dump one variable, use the <wiki:get/> tag:

<wiki:get name="myvar"/>

displays as:

Hello **world**.

Using a variable in an HTML argument

If you want to use a variable in an HTML argument, you can reference it by using the ${var} syntax. To include the variable in the wiki-text, that is, if you want the variable to be parsed again, use the % syntax:

myvar is: %myvar%

Illegal vars: %test$ 50% %%\\
Empty vars: "%foo.bar%"\\

displays as:

myvar is: Hello world.

Illegal vars: %test$ 50% %
Empty vars: ""

Note

The difference between <wiki:get/> and the %var% syntax is the render time. The tag is executed when the document is rendered, where as with the property notation, the variable is replaced during the parsing of the text.

Variables containing other variables

Variables can contain other variables:

<wiki:set name="product.copy">&copy; 2010 by %product.company%</wiki:set>
<wiki:set name="product.company">Day Software </wiki:set>
<wiki:set name="loop">Recursive %loop%</wiki:set>
//%product.copy%//
//%loop%// test.

displays as:

© 2010 by Day Software
Recursive test.

Variables containing arguments

Variables can contain arguments (see also BUG definition in previous tables):

<wiki:set name="GOOGLE">[http://www.google.com/search?q=%var.args%|%var.args%]</wiki:set>
View google results for %GOOGLE{jcr}%.

<wiki:set name="LINK"><a href="%var.args.0%">%var.args.1%</a></wiki:set>
%LINK{http://www.day.com,Day Software}%

displays as:

View google results for jcr.

Day Software

Extending the wiki

The wiki can also be extended through a plugin API.


Your comments are welcome!
Did you notice a way we could improve the documentation on this page? Is something unclear or insufficiently explained? Please leave your comments below and we will make the appropriate changes. Comments that have been addressed, by improving the documentation accordingly, will then be removed.

ADD A COMMENT

 

In order to post a comment, you need to sign-in.

Note: Customers with DayCare user accounts need to create a new account for use on day.com.

***