Advanced Wiki Formatting

Overview ¶ 

Below are some of the more specialized commands you'll need to make your wiki more dynamic.

Images ¶ 

Images can be clearer, quicker, and easier—than a wiki with text only. You can add images to both Answers posts and wiki articles. Simply position the text cursor in the wiki text where you want the image tag to go, then drag the image from your image uploader's library onto the wiki editing text box or Answers post. Doing so copies the image identifier automatically and inserts a basic image tag.

That's the easiest way to add images, but if you'd like to do it manually, follow these instructions instead: Drag an image from your library into the "Image Manager" box in the sidebar and hover over the image to get the image identifier. Once you have the identifier, you can manually add the tag (see format below) to the wiki text.

For wiki articles and Answers posts ¶ 


If you'd like, you can skip over size and align fields altogether. They default to standard and right, respectively. The caption and link fields are also optional.

Videos ¶ 

Currently, we support embedded videos from Vimeo, YouTube, and Screencast.

The only thing better than pictures are moving pictures. You can add videos to your wikis (but not guides, presently). The format for videos is similar to that for images; but rather than identifying videos by a numeric identifier specific to your site, you identify them by a link to the video on the service where the video is hosted (e.g. Vimeo). So to add a video to a wiki article, you just need to duplicate wiki syntax that looks like the following:

[video|<link to video>|size=small,large|align=left,right,center]

As with images, the size and align specifications are optional, but for videos they default to large and center respectively. You can add a caption to a video, but the formatting is different than that for images. Consequently, you can add wiki markup to the caption text. Here's an example use of the video tag, complete with caption text that includes a link:

[video|]A video about [|iFixit].[/video]

Note that without a caption, there's no closing [/video] tag, but that to provide a caption, a closing tag is added and the caption text is nested between the opening and closing tag.

Screencast Embedding ¶ 

You'll need to do a little extra work to embed videos from Screencast. You can't just copy and paste the URL for a Screencast video, because the URL to view a video on the Screencast site is very different from the URL to embed the same video. The URL you need is the last one in the big block of text you'll get if you copy and paste the Embed on your page HTML. It should look something like:<long identifier>/embed

Copy that URL and paste it as the appropriate field of the wiki syntax below:

[video|<long identifier>/embed]

Summaries ¶ 

In both guide introductions and wiki articles you can supply a summary for the guide or article that appears in search results, lists of popular items, and so on. Because the summary text shows up in different contexts and in very tight spaces, it can't contain any wiki formatting (including raw and code tags). Here's an example summary:

[summary]Model M6497 or A1005 / 500, 600, 700, 800, or 900 MHz G3 processor.[/summary]

This text will show up in a number of places, but will not show up where you put it in the wiki text. The actual summary tag usually renders to nothing. Instead, the text it contains is pulled out and used elsewhere.

Escaping Wiki Formatting ¶ 

There are times when wiki syntax can get in the way of your explanations. It might happen when you are explaining code or if your particular text stylings include characters that our formatting interprets as a wiki syntax command.

Don't start pulling our your hair out just yet. You can escape wiki formatting. When you do, whatever you type into your editing page will appear "as is" on your wiki page. There are two primary methods for escaping wiki formatting: raw and code.

Raw ¶ 

In all likelihood, you'll rarely need [raw], but we like to prepare you just about everything. [raw] is typically used to include text that would normally be treated as special wiki formatting.

So, let's say that you (for some ungodly reason) want to wrap a word or phrase in two plus signs: ++insert reason here++ . Normally, wiki formatting would translate those double plus signs as a command to underline the word. [raw] prevents the wiki from making those changes.

To use it, just wrap text with a [raw] tag, like so: [raw] "your text goes here" [/raw]. Now, your text won't be interpreted as part of any wiki markup.

As a note, [raw]text doesn't take on a monospace typeface, as it does in code formatting (explained below). The purpose of [raw] is merely to escape wiki formatting. Monospace formatted text looks cool, but technically does not escape wiki formatting. If you'd prefer monospace text to [raw], just wrap your text in backquotes in the following manner: ``...``.

Code ¶ 

You'll probably rely on [code] more frequently. Using[code]leaves your text untouched by wiki formatting, but it also displays text as monospace within a discrete block—that makes [code] especially useful for examples of actual code. Still, [code] has many different applications. We've used [code]throughout this page to enclose examples of wiki syntax in blocks.

To use [code], simply enclose your text in [code]...[/code]. Below is an example of how to add those tags:

At its heart, Automotive Right to Repair is about consumer choice. As an owner, you should have the right to repair your car wherever you want: at the manufacturer repair center, at the trusty corner mechanic, or in your driveway.

Dynamic Lists ¶ 

Before we delve into creating dynamic lists, you must first understand what they are and how they function. A dynamic list is essentially an incomplete list; and because it's incomplete, you can keep adding items onto it. A dynamic list searches through material on the site looking for tags that are relevant to the list. It then groups all of the documents together in list form.

For example, let's say you've created guides of varying difficulty levels, but you want to display all the easy guides together on a category page. You can do that with a dynamic list. Simply add a tag on the guide's editing page. Type "easy" into the guide field and click add. Once all the related guides are tagged with the same identifying tag, you can create dynamic lists of step-by-step guides on any wiki page, like a category page.

You'll need the following information to create a dynamic list:

  • Tag
  • Item
  • Guide type

Use the example code below to create your own dynamic list. Simply insert your own information into the appropriate fields:

[guidelist|item=iPhone 3GS|type=howto]

You can also create lists of wiki pages. Just add a comma-separated list of tags after the vertical bar, as in the following examples:


Go back to the Help Index

Was this article helpful to you?
Didn't find the answer you were looking for? Ask a Question