X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/7d8a362f1be332313c2d9020fc92a0ea5258f377..d243c0645d995c44a9f394c322375aeecc28d919:/doc/sandbox.mdwn

diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn
index d0cc29ab7..b7c9fc185 100644
--- a/doc/sandbox.mdwn
+++ b/doc/sandbox.mdwn
@@ -4,7 +4,7 @@ This is the SandBox, a page anyone can edit to try out ikiwiki.
 
 So, I'm wondering why ikiwiki requires links to have no spaces in their names, and uses .html suffixes. I really don't like having to use [[CamelCase]] for multi-word links, and it's generally not good practice to encode stuff like filetype or specific technologies in the URL; that's what we have a MIME type for. Anyhow, this is really just a test for playing around in the sanbox, but those are the two things that bother me the most off the bat about ikiwiki.
 
-> For the former: because links with spaces get parsed as [[preprocessor_directives|preprocessordirectives]].  You can get away with it if the first word doesn't correspond to a preprocessor directive.  If you have another syntax you'd prefer, feel free to propose it.  For instance, I can imagine extending the syntax with something like [["link with spaces"]].
+> For the former: because links with spaces get parsed as [[preprocessor_directives|preprocessordirective]].  You can get away with it if the first word doesn't correspond to a preprocessor directive.  If you have another syntax you'd prefer, feel free to propose it.  For instance, I can imagine extending the syntax with something like [["link with spaces"]].
 > For the latter: see the new `usedirs` option if you want to avoid .html suffixes.
 
 ----
@@ -61,6 +61,7 @@ Bulleted list
   * two
      * three
        * four
+        * five
 
 ----
 
@@ -106,3 +107,7 @@ So what's the point? [[How is this different to any other WiKi|features]]
 ----
 Test.. I was looking for a wiki supporting OpenID~ 
 
+----
+me too...
+
+[[if test="sandbox/C++" then="[[sandbox/C++]]" else="sad face!"]]
\ No newline at end of file