X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/7d8a362f1be332313c2d9020fc92a0ea5258f377..f02672c113813c37a659991ae984a2368e15b8db:/doc/sandbox.mdwn
diff --git a/doc/sandbox.mdwn b/doc/sandbox.mdwn
index d0cc29ab7..a39264e18 100644
--- a/doc/sandbox.mdwn
+++ b/doc/sandbox.mdwn
@@ -1,29 +1,18 @@
-This is the SandBox, a page anyone can edit to try out ikiwiki.
+This is the [[SandBox]], a page anyone can edit to try out ikiwiki (version [[!version ]]).
----
-
-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 latter: see the new `usedirs` option if you want to avoid .html suffixes.
-
-----
-
-testing openid ... ignore.
-
-Test. ÐÑовеÑка. ãã¹ã ıÄüÅöçİ à¸à¸à¸ªà¸à¸ éphémère
+test
+[[ä¸ææ¾ç¤º]]
Here's a paragraph.
-Here's another one with *emphasised* text.
-
-do ë characters work? Sure.
-
-OpenID test. It works!!
+The following code block is pre-formatted:
-Test..
+ Testing what
+ pre-formatted code blocks
+ look like.
-There are Polish diacritical characters: Ä
, Ä, Ä, Å, Å, ó, Å, ż, ź.
+Here's another one with *emphasised* text.
# Header
@@ -35,7 +24,7 @@ There are Polish diacritical characters: Ä
, Ä, Ä, Å, Å, ó, Å, ż, ź.
>
> > This is nested blockquote.
>
->> And without a space works too.
+>> Without a space works too.
>>> to three levels
>
> Back to the first level.
@@ -51,6 +40,7 @@ Numbered list
3. baz
4. qux
5. quux
+ 6. wibble
Bulleted list
@@ -61,48 +51,40 @@ Bulleted list
* two
* three
* four
+ * five
----
-[[haiku hint="sandbox play"]]
+[[!template id=note text="this is generated by the [[plugins/haiku]] plugin"]]
+[[!haiku hint="sandbox play"]]
----
+The haiku will change after every save, mind you.
+
## Different sorts of links:
-* [[WikiLink]]
-* [[different_name_for_a_WikiLink|WikiLink]]
-* [[different name for a WikiLink (with spaces this time)|WikiLink]]
+* [[Features]]
+* [[different_name_for_a_WikiLink|ikiwiki/WikiLink]]
*
* [GNU](http://www.gnu.org/)
* [Email](mailto:noone@invalid)
-* WikiLink without any markup.
+* [![ikiwiki logo](http://ikiwiki.info/logo/ikiwiki.png)](http://ikiwiki.info)
+* plain old html link
+* [[foo]]
-----
-This sandbox is also a [[blog]]!
-
-[[inline pages="sandbox/*" rootpage="sandbox" show="5"]]
-
-----
-[[newpage]]
----
+This SandBox is also a [[blog]]!
-Ethan wants to make a [[sandbox/castle]] in the sand.
+[[!inline pages="sandbox/* and !*/Discussion" rootpage="sandbox" show="4" archive="yes"]]
-hi
-
-just testing
-
-Testing a user page for [[users/kyle]]
-
-----
-what happens if i edit something with an openid set?
+--------
------------
+This gives an example of inline code: `tar | netcat` is a nice way to transfer bulk files over the net
-So what's the point? [[How is this different to any other WiKi|features]]
+But, of course, rsync is better.
----
-Test.. I was looking for a wiki supporting OpenID~
+Let's see what happens... ~~