This documentation relates to an earlier version of Confluence.
View this page in the current documentation or visit the current documentation home.

Confluence Notation Guide Overview

Skip to end of metadata
Go to start of metadata
All Versions
Table of Contents

Confluence pages are stored internally in a simple content-formatting language called Wiki Markup, based on Textile.

The Wiki Markup Editor allows users to edit Confluence pages directly in wiki markup language. This has the advantage of being faster than the Rich Text Editor for some formatting tasks. When using the wiki markup editor to edit a page, examples of commonly used markup are displayed in a panel on the right called the Quick Notation Guide, with a link to the Full Notation Guide for more detail.

Because wiki markup is designed to be simple to learn, the quickest way to learn wiki markup is to edit an existing page, switch to the wiki markup editor and experiment. More resources on wiki markup editing can be found below.

Full Notation Guide To customise the look and feel of the notation guide, please see these instructions.
Working with Headings
Working with Text Effects
Working with Text Breaks
Working with Links
Working with Anchors
Working with Images
Working with Lists
Working with Tables
Working with Macros
Confluence Emoticons

Here's a short example of some typical markup:

What you type

What you get



Confluence Markup


Ideally, the markup should be readable and even clearly understandable when you are
editing it. Inserting formatting should require few keystrokes, and little thought.

After all, we want people to be concentrating on the words, not on where the angle-brackets
should go.

  • Kinds of Markup
    • Text Effects
    • Headings
    • Text Breaks
    • Links
    • Other

Here, in comparison, is how that would look if you had to edit the page in HTML:





RELATED TOPICS

Rich Text Editor Overview
Writing Confluence pages
Creating a New Page
Working with Macros

Take me back to Confluence 2.0 Home



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.