- It makes Wiki hyperlinks instantly recognizable
- It leads to interesting Wiki topics
- It avoids the need to fiddle with HTML tags
-- It avoids over-general topics, because at least two words are required
+- It avoids over-general topics because at least two words are required
**Syntax of a WikiWord**
- [[WikiWord]]
- [[GoodStyle]]
- [[AVeryLongWikiTopicNameIsAlsoPossible]]
-- [[ProblemY2K]]
+- [[YearTwoThousand]]
**Bad examples for WikiWords:**
- Insert WikiWords wherever you can. Rich linking helps to make a Wiki successful.
- To stop a WikiWord from being turned into a hyperlink, insert the text `<nop>` immediately before the WikiWord.
- A topic is usually presented in the singular. Plural WikiWords are automatically linked to the singular topic, i.e. the link [[WikiWords]] links to the topic [[WikiWord]].
-- Sometimes you have to be creative to find a good WikiName. For example, if you want to create a topic about the year 2000 problem, you could go for [[FixY2K]] or [[YearTwoK]] or [[YearTwoThousand]], but not [[Year2K]] or [[Y2K]] or Y2000.
-- Turn acronyms into WikiWords, i.e. take [[FaqIndex]] for a "FAQ index" topic.
+- Sometimes you have to be creative to find a good WikiName. Examples:
+ - To create a topic about the the **Bread Slicer 1.2** product, use `BreadSlicer1dot2` or `BreadSlicer1pt2`, but not `BreadSlicer1.2`.
+ - To create a topic about **year 2000**, you could go for `YearTwoK` or `YearTwoThousand`, but not `Year2K` or `Y2K` or `Y2000`.
+- Turn acronyms into WikiWords, i.e. take `FaqIndex` for a "FAQ index" topic.
+- You can create nicer looking links by using double square brackets, i.e. write `[[TWiki access control]]` to get a link to [[TWikiAccessControl]] that looks like [[TWiki access control|Main/TWikiAccessControl]].
+
+**_Related Topics:_** [[WikiSyntax]], [[TextFormattingRules]]
git://git.openafs.org / openafs-wiki.git / blobdiff