debugging a wiki text parsing error, please come back in a few minutes
The XPages editor in Domino Designer has a Source tab, which shows the XML contents of the page. That XML format is explained here.
Usually you edit XPages in the editor Design tab, which shows what the page will look like. Changes in the Design tab or in the Properties view will make changes to the XML in the Source view. This document aims to explain the different structures used to represent the page content in XML. An understanding of the format gives the benefits of working with source instead of the Properties panels: it allows you to edit values in the source tab, to search an Application for text using the Search menu, to use find and replace when you want to make changes, to use cut, copy and paste when you want to restructure an XPage or create many similar controls.
The simplest structures covered are:
The following are more complicated, and are not necessary to understand most pages:
The following controls are accessories to the normal controls that are listed in the palette. Each requires some parent control to function, so they cannot be used stand-alone. They may seem odd or strange when you first see them in the source, so some details are provided below.
Open the new Domino Designer in Eclipse. In the Database Navigator, create an application. (Right-click, New Application, enter a title like test01, click OK). Expand your application. Double-click on the new XPage design element, click New XPage, name it page1.
Type in the text "hello world". Switch to the Source tab, at the bottom of the editor.
The text you typed in is in the middle.
If you preview the XPage in a web browser, it will display that text exactly as you typed it (use the Preview button in the toolbar).
Such text is known as markup text.
[At run-time that markup text is represented by a control, whose "text" property is set to the entered text.]