Repository Wiki

Examples of markup languages:  HTML – HyperText Markup Langauge  XML – Extensible Markup Language  XHTML - Extensible HyperText Markup Language Vanilla software is computer software that is not customized from its delivered form - i.e. it is used by a business without any customizations applied to it. Wikitext language or wiki markup is a markup language that offers a simplified alternative to HTML and is used to write pages in wiki websites such as Wikipedia. There is no commonly accepted standard wikitext language. The grammar, structure, features, keywords and so on are dependent on the particular wiki software used on the particular website. CamelCase (also spelled "camel case" and sometimes known as medial capitals) is the practice of writing compound words or phrases in which the words are joined without spaces and are capitalized within the compound — as in LaBelle, BackColor, or iMac. The name comes from the uppercase "bumps" in the middle of the compound word, suggestive of the humps of a camel. Contents Modelling Standards – Naming conventions and modeling techniques Quality Assurance – Test reference, goal of the QA, Steps to be followed when submitting a repository for QA GoAgileMAP – What is MAP? MAP reports, Documentation and Manuals Projects – brief descriptions of SAPS projects, members of the projects and the locations. FAQ – contains common modeling issues encountered by users and possible solutions to the issues. Creating and linking Wiki pages CamelCase characters or medial capitals are used to name and create links or pages. These are produced by capitalizing words in a phrase and removing the spaces between them. Editing Wiki Pages

Normal Text Editing Italics (_italics_) or two ticks (''italics'') for italics

Bold Asterisk (*bold*) or three ticks ('''bold''') for bold Test Test

Quotes Quotes are done using the normal notation: Use single quotes for words you want in 'single quotes' and double quotes around words you want "double quoted"

Underline Plus sign (+underline+) for Underline

Strikethrough Minus sign (-strikethrough-) for

Headings Bang (!) at the start of a line for H1, Bang Bang (!!) at the start of a line for H2, Bang Bang Bang (!!!) for H3, etc.

!Example of Heading1 !!Example of Heading2 !!!Example of Heading3

Lines Four dashes (- - - -) at the beginning of a line gives you a horizontal line (a.k.a. rule).

Note: anything immediately following these dashes will not be rendered. Like this: and this:

Code At sign (@code snippet@) for code snippet print('hello world');

Linking Formatting Rules

Basic Linking Any "word" using PascalCase automatically becomes a link. For example, FlexWiki, HelloWorld or TheDemocraticParty. PascalCase words without topics (like HelloWorld) become links that will create topics when you click on them. Words can also include WikiNamespaces, which will be automatically stripped off when displaying the link. FlexWiki.PascalCase becomes PascalCase. FlexWiki tries to be somewhat smart about automatic linking, but it has severe limits. For instance, it removes the "S" off the end of WikiNamespaces to find WikiNamespace, but not the "D" off WikiNamespaced . Anchors are also supported, see Anchors.

Linking to URLs Like PascalCased words, any URL becomes a link: http://www.blizzard.com. Notice the formating changes for a link to an external site. Care must be taken when using automatic URL linking, because punctuation immediately (before any whitespace) following the URL will be included. Periods are okay following a domain name ( http://www.blizzard.com. ) or after a path separator ( http://www.blizzard.com/inblizz/. ) but they will usually generate "file not found" errors when following a filename ( http://www.blizzard.com/inblizz/reviews.shtml. ). To place punctuation immediately after a URL, use a FreeLink.

Some URL links require URL Encoding before they will work. This won't work: http://maps.google.com/maps?q=1000+Aerial+Center+Pky,+Cary,+NC+27513&spn=0.0 23328,0.034083&hl=en You first have to encode it, then it works. http://maps.google.com/maps?q=1000%20Aerial%20Center%20Pky%2C%20Cary%2C %20NC%2027513&spn=0.023328%2C0.034083&hl=en Question For a URL link, why can't you just encode the generated HREF ? The link text itself doesn't have to be encoded—it probably shouldn't be—but the HREF should always be. Question How come I can't put a link into a list? Request Links are very restrictive in what they allow - for instance, I can't seem to put in a link to mk:@MSITStore:C:\Debuggers\debugger.chm::/hh/DebugMS/r19_metacmds_ A_99939ae5-be91-4ff3-a7fe-3162f8cd11da.xml.htm - I tried the encoding of various parts, but I wasn't able to get it to work for this url. Can we make it less restrictive? What's the trade-off here? Question Creating a page with numbers seems to confuse the auto page title formatting. For example, creating a page called SQLServer2000 creates a page with the title "SQL Server2000". Is there a way to force the space between Server and 2000? Answer I think that you would do it like this Faux Topic Name for "FauxTopicName". Or like this for your "SQLServer2000" example, SQL Server 2000. Check out the re-labeling links section below. Note that for intranet use you can also link to Windows shares using file:////server_name\share_name (this link doesn't go anywhere).

E-mails Linking an e-mail address is similar to the html a tag. mailto:[email protected]

You can even give more recipients: mailto:[email protected];[email protected] And subject: mailto:[email protected]?subject=Hello%20my%20friend You can give friendly name too "Contacts":mailto:[email protected];[email protected]

Contacts "Contacts":mailto:[email protected]?subject=Hello%20my%20friend

Contacts -- SzaMa - 2006.04.16 And CC: or BCC: mailto:[email protected]?subject=Hello%20my%20friend&cc=somebodyelse@e [email protected] -- AaronSachs - 2006.12.07

Free Linking Surrounding a word with square brackets is called a FreeLink and will give you a link whether you use PascalCase or not. So, putting square brackets around camelCase, gives you camelCase. However, you should generally use PascalCased words. I mean, whyNotUsePascalCaseHere. Question This doesn't seem to work for UNC paths (on an Intranet), and for some reason if a ! is in the link, it seems to abort making a link, when !'s are used for windows private shares (and hence all of our UNC paths would have them in my case). It's also possible to have one word links (without using square brackets), but they're special; see: one-word topic names.

Question This doesn't work with titles with spaces. In fact, while FlexWiki seems to support pages that have spaces in the name (ie, I can rename a page to have spaces and navigating to the page works fine), there doesn't seem to be any possible way to link to them. Am I missing something? Question How does one do relative/absolute links? (with no hostname?) I've managed to get FlexWiki running on my laptop (using Apache on Linux), and it'd be useful to link to documentation and other sites on my laptop that are not part of the wiki. I can't rely on a hostname, as I may wish to have remote access to these files, and may need to use an IP number.

Preventing Linking To prevent PascalCase words from being linked, start and end the word with two doublequotes. To show PascalCase non-linked, you enter: ""PascalCase""

This is particularly useful, for preventing linking to a FauxTopicName, one-word topic name, or plural forms of TLAs, such as ROMs. Question How to prevent PascalCase words from being linked in Bold text? I have a paragraph in which few lines are in bold. But if I try to escape the PascalCased words as mentioned here, the text is no longer bold. Any workaround? Answer It is possible to have all the text in the paragraph in bold except the escaped PascalCase term. By escaping the PascalCase it prevents all other formatting. The one case where this is not the case is if you use a Presentations.Container and then use CSS to reset the contents of the container back to bold. -- JohnDavidson [2008-Sep-30]

"Relabel"ing links If you know you want a link, but want to display text other than the linking text, you can "relabel" the link. These are sometimes called arbitrary links or piped link. They will have fomatting matching their link type. The pattern for them is :. (Someone called this pattern a Textism, but I'm unfamiliar with the term.) Examples:

You write

FlexWiki displays

"pascal case":PascalCase

pascal case

"camel case":[camelCase]

camel case

"pascal case":FlexWiki.PascalCase

pascal case

"camel case":FlexWiki.[camelCase]

camel case

"Microsoft Corp.":http://www.microsoft.com

Microsoft Corp.

"http://www.flexwiki.com/images/go.gif":http://www.flexwiki.com Question Is it possible to link to a topic in another namespace other than the one the current topic is in? I tried something like OtherNameSpace.TopicName and it doesn't seem to work. Answer I think this is answered in the table above now, but I haven't been able to test it fully yet. Question Why can't you mix Basic Links with Relabeled links (see below) This is a BasicLink followed by a relabeled link to IBM A relabeled link to IBM followed by a BasicLink A link to http://www.ibm.com followed by a BasicLink

Anchors/Bookmarks (available in build 1.8.0.1661 or later) Any WikiPageProperty or HiddenWikiPageProperty (see FormattingRules#WikiPageProperty) becomes an anchor (or bookmark) on that page. You can reference that anchor by using the # form, e.g. FormattingRules#Properties