xcfit 0.2.0

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/WikiTheming/properties.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<AddChild>true</AddChild>
+<Files/>
+<Help>Style FitNesse the way you like (theming).</Help>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/WritingPlugins/content.txt

@@ -0,0 +1,37 @@
+FitNesse is extensible. It can be extended via components configured in the ConfigurationFile. Since version 20150226 FitNesse also has another mechanism: service providers. It's using the Java [[!-ServiceLoader-!][http://docs.oracle.com/javase/7/docs/api/java/util/ServiceLoader.html]] functionality to load services dynamically.
+
+!2 How does it help me?
+Previously, to install a plugin you had to download the plugin and load it alongside FitNesse (either from the plugins folder or by using a build tool such as Ant or Maven to launch FitNesse) '''and''' you had to configure the plugin in the ConfigurationFile. When a plugin has a service provider it is no longer needed to also define it in the configuration file. Just put the plugin  jar on the FitNesse class path or in the plugins folder and it will be configured automatically.
+
+!2 Add service providers to your plugin
+To add a service provider the plugin provider class (plugin feature factory) has to be configure in
+
+{{{META-INF/services/fitnesse.plugins.PluginFeatureFactory}}}This file has to contain the plugin implementations (which should implement the !-PluginFeatureFactory-! interface), one per line. Plugins can also extend !-PluginFeatureFactoryBase-!, which contains empty implementations for all methods.
+
+The interface looks like this:
+
+{{{public interface PluginFeatureFactory {
+
+  Authenticator getAuthenticator();
+
+  ContentFilter getContentFilter();
+
+  void registerResponders(ResponderFactory responderFactory) throws PluginException;
+
+  void registerSymbolTypes(SymbolProvider symbolProvider) throws PluginException;
+
+  void registerWikiPageFactories(WikiPageFactoryRegistry wikiPageFactoryRegistry) throws PluginException;
+
+  void registerTestSystemFactories(TestSystemFactoryRegistry testSystemFactoryRegistry) throws PluginException;
+
+  void registerSlimTables(SlimTableFactory slimTableFactory) throws PluginException;
+
+  void registerCustomComparators(CustomComparatorRegistry customComparatorRegistry) throws PluginException;
+
+}
+}}}
+The methods ''getAuthenticator()'' should return one instance. If multiple plugins provide an authenticator, the first authenticator found will be used. The setting can be overridden by explicitly defining an authenticator in the configuration file.
+
+The same rules are applicable for ''getContentFilter()''.
+
+The ''registerXxx'' methods are invoked with the appropriate provider or registry. It is the responsibility of the plugin to register it's plugins with those providers.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/WritingPlugins/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/content.txt

@@ -0,0 +1,2 @@
+!2 Administering FitNesse
+!contents -R1 -g -h

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/AdministeringFitNesse/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<Search/>
+<Static/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/DeliveringTheRightSystem/content.txt

@@ -0,0 +1,43 @@
+As we discussed in AcceptanceTests, FitNesse testing is about building the ''right code'', as opposed to unit-level testing, which is about building the ''code right''. By "right code" we mean "right system": the feature set with the most business value.
+
+!3 Everybody Helps Deliver the Right System
+Unit-level testing can be done by individual programmers or pairs of programmers without any involvement on the part of non-programmers. FitNesse must be shared among programmers and non-programmers. Try sharing the use of FitNesse among all the disciplines on your software team: managers, programmers, testers, business analysts and experts, customer representatives, users, useability experts, technical writers, support staff, and others. Everybody can benefit from helping to define and run FitNesse tests.
+
+!3 Write The Tests First
+As close as possible to the beginning of a software project, before you have done much requirements analysis, try to get key project stakeholers together to begin defining FitNesse AcceptanceTests. If you are using an agile development method such as Extreme Programming, it will be fairly straightforward to fit this into your schedule and routine. But if not, you'll likely have to win over some hearts and minds, and break through a bit of inertia.
+
+!3 Put Prose and Test Tables Together
+We're not necessarily suggesting that you replace your entire requirements process, in its current form, with FitNesse tests. But we are suggesting that you integrate FitNesse tests and test pages into your requirements process. You may even find, as we have, that all of the prose, images, and everything else that typically goes into a requirements document can just as easily go on FitNesse test pages, along with the tests. The prose describe what the tests mean,
+
+!3 Example Scenario: Once There Was Some Pizza...
+Imagine that a large shipping company is replacing an aging inventory control system. It's a mammoth undertaking. Everybody is involved. But before they get underway, one of the key executives decides that FitNesse might be a big help. She asks the Product Manager for the new system to investigate FitNesse, and to try using it from the outset on the new system. They hire a contractor to provide some FitNesse training, and put together a plan for using it on the project.
+
+In the first two weeks of the project, before any requirements meetings or documents have happened, the Product Manager gets together with just a few major stakeholders: one of the lead architects, a senior developer, a testing veteran, and one of the inventory experts who will be an eventual user of the system.
+
+The Product Manager brings these other 4 people together in a small meeting room containing some Actual Food in the form of pizza and drinks. The senior developer agrees to create test tables in FitNesse on te fly on his laptop. Yes! Test tables on the fly! Can that possibly work? Absolutely.
+!3 A Few First Test Tables
+This team uses pizza, white boards, paper, Excel, FitNesse, and animated discussion to create only two first FitNesse tables. Each table has 6 or 8 rows, and 5 or 6 columns. Both tables concern a single requirement (at least that's what everybody currently believes), and fit on a single test page. The test page contains only the two tables and a first stab at some explanatory prose. The meeting breaks up, after scheduling another similar meeting the next day.
+!3 "Wait. You Meant ''That''?"
+Test tables describe requirements differently than prose (as we discuss in AcceptanceTests). The exercise of defining test tables for a requirement is a bracing and enlightening one.
+
+Even when a team thinks they have a set of requirements nailed down in prose, using traditional requirements analysis and documents, they will often find that they learn useful things by trying to express those requirements in terms of executable sets of inputs and expected outputs.
+
+You may often find that during the course of writing those tables, heated debates arise about the true meaning of the requirement. These are a healthy thing! You want these debates to occur, and you want them to occur as early as possible in the project, and certainly before any code has been written.
+
+Our intrepid team has several such heated debates between mouthfuls of pizza, and they manage to come to agreement on all of them, in a way that is then expressed in those first two tables. Lots of discussion and sketching and writing all get boiled down to a small handful of inputs and expected outputs that eventually must execute correctly.
+!3 So What? What Does that Give You?
+What can our team show for these first couple of hours of work? Well, they all agree that:
+ * The two tables and their accompanying prose describe all the important inputs and outputs for this one requirement (as far as they can tell so far)
+ * The programmers have a very good idea what it means to write the code to get those two test tables to pass.
+ * Once those two test tables both run green, '''that requirement will be done''', and they can move on to another requirement.
+ * The Product Manager, tester, and inventory expert all agree that they may be able to refine the two test tables to describe a few ''unhappy path'' scenarios that they did not identify in the meeting.
+!3 Successive Refinement: Let's Talk About the Tests
+As the days and weeks go by, the team creates and publishes more test pages containing more test tables and prose. They organize these into a Test Suite. As the weeks pass, tables and test pages get split, combined, moved a round, and otherwise refined.
+
+Within the first couple of weeks, the programmers get those first two test tables for that first requirement to turn from red to green. They send out a triumphant email. But instead of getting back a congratulatory email from the Product Manager, they get back an email saying "You know what? It turns out that that work is not ''exactly'' what we needed..." So the Development Manager and the Product Manager get together and '''refine those first two tables''' so that they ''do'' describe exactly what was needed.  Over the next couple of weeks, the programmers refine their work to get these new test tables to pass. And then they do in fact receive their congratulatory email.
+
+The point of this is that when it comes to addressing any ambiguities or misunderstandings in requirements, '''test tables are the perfect thing to talk about'''. By refining the test tables, and organizing the requirements discussion around them, the team successively refines the system itself. (They may also successively refine their ability to deliver the system iteratively and incrementally, but that's another story!)
+!2 Learning More
+If you haven't already done so, check out the [[Two Minute Example][<FitNesse.UserGuide.TwoMinuteExample]]. You should also check out AcceptanceTests.
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/DeliveringTheRightSystem/properties.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<Help>How Teams Can Use FitNesse: an Introduction</Help>
+<RecentChanges>true</RecentChanges>
+<WhereUsed/>
+<saveId>1238102182100</saveId>
+<ticketId>6331798438264035314</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/EditingFitNessePages/content.txt

@@ -0,0 +1,46 @@
+!2 Editing and Creating Pages in !-FitNesse-!
+!-FitNesse-! is a [[wiki web server][http://wiki.org/wiki.cgi?WhatIsWiki]]. Before you can begin [[creating test tables][<UserGuide.WritingAcceptanceTests]], you need to know a bit about how a wiki works.
+
+A wiki allows any authorized user to make changes to any edit-enabled page, or to create new pages, simply by using their Web browser. If you are working with a copy of !-FitNesse-! on your own machine, you are probably authorized to make such changes.
+
+!3 Editing a Page
+Once you are on a page your want to change, hit the '''Edit''' button in the upper left. (If the button does not appear, then the page is not edit-enabled.)
+
+A new page will pop up with an edit frame containing the markup language of the current page. You specify formatting using a simple markup language. If you're not into wiki markup, switch to the rich text editor mode. Simply make your changes to the page and hit the '''Save''' button. ''Voila!'' Your changes appear on the page.
+
+!3 Creating New Pages
+Every !-FitNesse-! page has a name in so-called camel-case format, in which the first letter is uppercase, and, at least, one other letter in the word is uppercase. The name of this page, EditingFitNessePages, is an example. This convention makes it truly easy to create new pages and links to those pages.
+
+When you edit an existing page and insert a new camel-case word, such as !-ThisHereNewPage-!, and then click the Save button, FitNesse interprets that to be a link to a new, as-yet-uncreated page. It indicates this to you by putting a question mark at the end of the name.
+
+If you then click on that question mark, !-FitNesse-! displays an edit frame, enabling you to put something on that new page. If you type anything at all in there and click Save, your new page is created, and the link to it is enabled on the originating page.
+
+!3 Try Creating a New Page with a Link Back to This One
+Try it yourself. Click on the question mark at the end of this word: ThisHereNewPageExample Put something on the page, click the Save button, and then return here. A good thing to put on the new page is the word EditingFitNessePages so that you can return to this page easily!
+
+!3 Using Templates
+If you find yourself adding the same boilerplate wiki text in many different places, it may be worthwhile to use it as a template. All immediate children of a page named !-TemplateLibrary-! are marked as templates for all pages who have the !-TemplateLibrary-! as a brother or uncle. It will appear in the drop down box above the text area in the plain text editor. When the "Insert Template" button is clicked, it will overwrite the current selection with the selected template (or insert the template at the caret if there is no selection).
+
+!2 A Few Formatting Examples
+The wiki markup language is fairly powerful. To see how we accomplished each of the formatting examples below, you can simply click the Edit button and check it out for yourself.
+
+You can '''make text bold''' by putting three single quotes (ticks) on each side of it (e.g., !-'''make text bold'''-!).
+
+You can ''make text italic'' by putting two tick marks on each side of it (e.g., !-''make text italic''-!).
+
+You can center a line by prefixing it with !-!c-!
+
+!c This line is centered.
+You can make a horizontal rule by using four or more dashes.
+So !- ---- -! becomes
+
+----
+For more examples of wiki markup language formatting widgets (as they are called), see MarkupLanguageReference.
+
+!3 Page Properties
+Each FitNesse page has several properties (Test, Suite, Edit, etc). You can read about setting them on PageProperties.
+
+!3 Pasting tables from Excel
+In the "plain text editor", there are 2 buttons on every edit window that have to do with spreadsheets like Excel. The first '''Spreadsheet to FitNesse''' will convert copied spreadsheet content into FitNesse tables. You have to paste the spreadsheet content into the edit window and then click.
+
+The second button, '''FitNesse to Spreadsheet''', is just as useful. When clicked it will convert all the tables in the edit window into a format that can be copied and pasted into a spreadsheet.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/EditingFitNessePages/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<WhereUsed/>
+<saveId>1238103025877</saveId>
+<ticketId>6855924077953894968</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/ExternalHtmlPages/content.txt

@@ -0,0 +1,20 @@
+You can include external HTML pages as sub-wikis within the !-FitNesse-! wiki. If you have a set of tests that were written in HTML before you started to use !-FitNesse-!, you can include these in your current test suites without converting them to !-FitNesse-! wiki pages.  If you prefer not to use the !-FitNesse-! wiki syntax and !-FitNesse-! editor to maintain your tests, you can still use !-FitNesse-! to execute your tests, both interactively and in batch, view test results and track test history.
+
+To include a folder of HTML files in the !-FitNesse-! wiki, simply place the folder somewhere beneath the !-FitNesseRoot-! folder that holds all the !-FitNesse-! wiki files.  Each folder containing HTML files will appear as a page and the HTML files will appear as child pages.
+
+Here's an example:
+
+ * We create a static wiki page called !-MyExternalPages-! and put the !contents widget in it.  This creates a folder called !-MyExternalPages-! with some wiki files in it (content.txt, properties.xml and maybe some zip files).
+ *  We create a folder called !-HtmlPages-! as a sub-folder of !-MyExternalPages-! and create several HTML files in !-HTMLPages-!: !-TestA.html-!, !-TestB.html-! and !-TestC.html-!.
+ * !-FitNesse-! now shows a page called !-HtmlPages-! as a child of !-MyExternalPages-! and three child pages of !-HtmlPages-! called !-TestA-!, !-TestB-! and !-TestC-!.
+
+The external HTML pages appear as read-only pages - you cannot edit them from !-FitNesse-! or change their properties (yet!).  The folder pages are always marked with the Suite property and the HTML pages are marked with the Test property if they contain at least one HTML table.  You can create !-SuiteSetup.html-! and !-SetUp.html-! files and !-FitNesse-! will treat these as special test pages, the same as wiki pages.
+
+This is a first version of this feature and so there are a few caveats:
+ * If you use the ?edit or ?properties URL syntax, you can get to the edit and properties pages, but they will fail if you try to save.
+ * The contents of the HTML files are placed as is inside a !-FitNesse-! page, and may break the page display if there are unbalanced tags or other HTML problems that may not be apparent when the HTML is displayed on its own.
+ * Hyperlinks, images, Javascript files and other external references in the HTML may not behave as expected when placed inside a !-FitNesse-! page.
+ * Wiki page names are generated from the HTML file names, but there is no check to avoid potential name collisions.  For example, !-TestA.html-! and testa.html will both generate !-TestA-! as a wiki page name.
+
+If you can avoid these issues, this feature should work well for you: it has been successfully used on a large suite of hundreds of HTML files.
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/ExternalHtmlPages/properties.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0"?>
+<properties>
+	<Edit>true</Edit>
+	<Files>true</Files>
+	<Properties>true</Properties>
+	<RecentChanges>true</RecentChanges>
+	<Refactor>true</Refactor>
+	<Search>true</Search>
+	<Versions>true</Versions>
+	<WhereUsed>true</WhereUsed>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/FilesSection/content.txt

@@ -0,0 +1,22 @@
+'''What is the 'files' section?'''
+The 'files' section is a directory where FitNesse keeps all of its non-wiki files such as images and other static files.
+
+'''How do I access the FilesSection?'''
+Simply add "/files/" on the end of the URL used to visit the FitNesse installation.  To get to the 'files' section of fitnesse.org the following url is used.
+http://www.fitnesse.org/files/
+
+Notice that this looks like a directory listing.  That is because the root of the FilesSection is a directory.  By clicking on a directory or file you will be redirected to that selection.  If it is a directory you will see a listing of its contents and if it is a file you will see the contents of the file.
+
+In general FitNesse will serve files from the FilesSection like any other web server would.
+
+'''How can I link to files in the FilesSection?'''
+Any file located in the FilesSection can be linked to from any Wiki page.  For example the link to the images directory would look like this:
+http://files/images/
+Notice that there is no domain name in the URL.  You could have put the domain name in like this:
+http://www.fitnesse.org/files/images/
+But that would not be taking advantage of the shortcut we have provided.
+
+'''Modifying the FilesSection?'''
+When you view a directory in the FilesSection you will see several controls at the bottom of the page.  They allows you to upload files from your hard drive to the current directory, add a new directory to the current directory, rename or delete an existing file.
+
+This allows you to upload and manage special documents and link to them from the appropriate page. You could also upload your most recent build to run tests against.

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/FilesSection/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<RecentChanges/>
+	<WhereUsed/>
+	<saveId>1213646204336</saveId>
+	<ticketId>2918076654716302964</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupHeaderAndFooter/content.txt

@@ -0,0 +1,3 @@
+ * If there is a wiki page named PageHeader its contents will be displayed at the top of every wiki page.
+ * If there is a wiki page named PageFooter its contents will be displayed at the bottom of every wiki page.
+ * PageHeader and PageFooter are inherited by a SubWiki

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupHeaderAndFooter/properties.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<RecentChanges/>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/LastModificationTime/content.txt

@@ -0,0 +1,7 @@
+You may see the time that a wiki page was last modified by using the ''!-!lastmodified-!'' widget.  It should be placed at the beginning of a line in the wiki text.
+
+!-!lastmodified-!
+
+The result of this widget is this:
+
+!lastmodified

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/LastModificationTime/properties.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<properties>
+<Files/>
+<RecentChanges/>
+<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/LinksWithinPages/content.txt

@@ -0,0 +1,96 @@
+When you have really longs pages it is convenient to list a bunch of links at the top of the page that will take you to sections further down in the page.  With a combination of a couple of wiki widgets, you can achieve this usefulness in FitNesse.
+
+The first component is called an '''Anchor'''.  Use anchors to designate locations in a page that you want to link to.  Create anchors like this:
+'''!-!anchor anchorName-!'''
+When saved, you wont see the anchors but they'll be there in the document.
+
+Now you just need to create a link to them.  You do that with the following syntax:
+'''!-.#pageBottom-!'''
+When saved this will turn into a link to the anchor named '''pageBottom''' in this case.
+
+.#pageBottom
+
+At the very bottom of this page, there is an anchor named '''pageBottom'''.  When you click in the link above, you will be taken to that hidden anchor.
+
+----
+And now, a little poem by '''William Butler Yeats''' to fill the space:
+
+That civilisation may not sink,
+
+Its great battle lost,
+
+Quiet the dog, tether the pony
+
+To a distant post;
+
+Our master Caesar is in the tent
+
+Where the maps ate spread,
+
+His eyes fixed upon nothing,
+
+A hand under his head.
+
+(Like a long-legged fly upon the stream
+
+His mind moves upon silence.)
+
+That the topless towers be burnt
+
+And men recall that face,
+
+Move most gently if move you must
+
+In this lonely place.
+
+She thinks, part woman, three parts a child,
+
+That nobody looks; her feet
+
+Practise a tinker shuffle
+
+Picked up on a street.
+
+(Like a long-legged fly upon the stream
+
+Her mind moves upon silence.)
+
+That girls at puberty may find
+
+The first Adam in their thought,
+
+Shut the door of the Pope's chapel,
+
+Keep those children out.
+
+There on that scaffolding reclines
+
+Michael Angelo.
+
+With no more sound than the mice make
+
+His hand moves to and fro.
+
+(Like a long-legged fly upon the stream
+
+His mind moves upon silence.)
+
+----
+
+!anchor pageBottom
+
+!c !1 You've hit the bottom of the page!
+
+
+
+
+
+
+
+
+
+
+
+
+
+

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/LinksWithinPages/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<LastModified>20090228113827</LastModified>
+	<RecentChanges>true</RecentChanges>
+	<WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupAliasLink/content.txt

@@ -0,0 +1,22 @@
+You can take any word, phrase, or image and turn it into a link using the following syntax:{{{
+[[word or phrase][wikiPage]]}}}Here are some examples:
+
+|!c Markup Text|!c Displayed as:|
+|!-click [[here][.FrontPage]].-!|click [[here][.FrontPage]].|
+|!-[[!img http://objectmentor.com/Images/OMI_HeaderArea_Logo.png][http://www.objectmentor.com]]-!|[[!img http://objectmentor.com/Images/OMI_HeaderArea_Logo.png][http://www.objectmentor.com]]|
+|!-[[''Recent Changes''][RecentChanges]]-!|[[''Recent Changes''][.RecentChanges]]|
+
+ * When the text is a wiki word, the link to the wiki word takes precedence, so you cannot override one wiki word to link to another.
+
+|!c Markup Text|!c Displayed as:|
+|!-click [[.RecentChanges][.FrontPage]].-!|click [[.RecentChanges][.FrontPage]].|
+
+ * When the link is a wiki word then, as usual, it may include a relative or an absolute path with respect to the parent page using < . > characters, or is a sibling if no path is specified. (See SubWiki for more details.)
+
+|!c Markup Text|!c Displayed as:|
+|!-click [[here][.FrontPage]].-!|click [[here][.FrontPage]].|
+|!-click [[here][MarkupAliasLink]].-!|click [[here][MarkupAliasLink]].|
+
+ * When the link is to an anchor on a different page, append the anchor's name.  (See LinksWithinPages)
+|!c Markup Text|!c Displayed as:|
+|!-click [[Bottom of Page][LinksWithinPages#pageBottom]].-!|click [[Bottom of Page][LinksWithinPages#pageBottom]].|

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupAliasLink/properties.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0"?>
+<properties>
+	<Files/>
+	<RecentChanges/>
+	<WhereUsed/>
+	<saveId>1238167070532</saveId>
+	<ticketId>-7119519436873449038</ticketId>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupBold/content.txt

@@ -0,0 +1,4 @@
+To set a word or phrase in '''bold''' simply enclose the section of text in three single quotes like this:
+
+|!c '''Markup Text'''|!c '''Displayed as'''|
+|!-I want '''this''' in bold.-!|I want '''this''' in bold.|

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupBold/properties.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0"?>
+<properties>
+  <Files/>
+  <LastModified>20060717205950</LastModified>
+  <RecentChanges/>
+  <WhereUsed/>
+</properties>

data/XCFitDemo/FitNesseRoot/FitNesse/UserGuide/FitNesseWiki/MarkupLanguageReference/MarkupCenter/content.txt

@@ -0,0 +1,7 @@
+You can center a line by prefixing it with !c
+
+!c This line is centered.
+
+|!c '''Markup Text'''|!c '''Displayed as'''|
+|!-this line is not centered-!|this line is not centered|
+|!-!c this text is centered-!|!c this text is centered|