From eeb7c436cc670a5910bc868bc2afaa06933334dd Mon Sep 17 00:00:00 2001 From: Cache Saravento Date: Fri, 7 Aug 2015 14:07:50 -0300 Subject: Static generated site --- ikiwiki/directive/index.html | 186 ++++++++++++++++++++++++++ ikiwiki/formatting/index.html | 221 +++++++++++++++++++++++++++++++ ikiwiki/ikiwiki.js | 54 ++++++++ ikiwiki/index.html | 138 +++++++++++++++++++ ikiwiki/markdown/index.html | 136 +++++++++++++++++++ ikiwiki/openid/index.html | 142 ++++++++++++++++++++ ikiwiki/pagespec/attachment/index.html | 153 +++++++++++++++++++++ ikiwiki/pagespec/index.html | 226 ++++++++++++++++++++++++++++++++ ikiwiki/pagespec/po/index.html | 140 ++++++++++++++++++++ ikiwiki/pagespec/sorting/index.html | 138 +++++++++++++++++++ ikiwiki/relativedate.js | 75 +++++++++++ ikiwiki/searching/index.html | 143 ++++++++++++++++++++ ikiwiki/subpage/index.html | 141 ++++++++++++++++++++ ikiwiki/subpage/linkingrules/index.html | 160 ++++++++++++++++++++++ ikiwiki/toggle.js | 29 ++++ ikiwiki/wikilink/index.html | 164 +++++++++++++++++++++++ 16 files changed, 2246 insertions(+) create mode 100644 ikiwiki/directive/index.html create mode 100644 ikiwiki/formatting/index.html create mode 100644 ikiwiki/ikiwiki.js create mode 100644 ikiwiki/index.html create mode 100644 ikiwiki/markdown/index.html create mode 100644 ikiwiki/openid/index.html create mode 100644 ikiwiki/pagespec/attachment/index.html create mode 100644 ikiwiki/pagespec/index.html create mode 100644 ikiwiki/pagespec/po/index.html create mode 100644 ikiwiki/pagespec/sorting/index.html create mode 100644 ikiwiki/relativedate.js create mode 100644 ikiwiki/searching/index.html create mode 100644 ikiwiki/subpage/index.html create mode 100644 ikiwiki/subpage/linkingrules/index.html create mode 100644 ikiwiki/toggle.js create mode 100644 ikiwiki/wikilink/index.html (limited to 'ikiwiki') diff --git a/ikiwiki/directive/index.html b/ikiwiki/directive/index.html new file mode 100644 index 0000000..8dabb09 --- /dev/null +++ b/ikiwiki/directive/index.html @@ -0,0 +1,186 @@ + + + + + + + +directive + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ directive + +

+ +
+ +
+ +
+ +
+

+ Posted Sex 13 Mai 2011 13:06:00 BRT +

+

Directives are similar to a WikiLink in form, except they +begin with ! and may contain parameters. The general form is:

+ +
[[!directive  param="value" param="value"]]
+
+ +

This gets expanded before the rest of the page is processed, and can be used +to transform the page in various ways.

+ +

The quotes around values can be omitted if the value is a simple word. +Also, some directives may use parameters without values, for example:

+ +
[[!tag  foo]]
+
+ +

A directive does not need to all be on one line, it can be +wrapped to multiple lines if you like:

+ +
[[!directive  foo="baldersnatch"
+bar="supercalifragilisticexpialidocious" baz=11]]
+
+ +

Also, multiple lines of quoted text can be used for a value. +To allow quote marks inside the quoted text, delimit the block +of text with triple-double-quotes or triple-single-quotes:

+ +
[[!directive  text="""
+1. "foo"
+2. "bar"
+3. "baz"
+""" othertext='''
+1. 'quux'
+2. "foo"
+''']]
+
+ +

If you want to put text with triple quotes into a parameter value, you can +use perl-style here-doc syntax, even nesting it like this:

+ +
[[!directive  text=<<OUTER
+[[!otherdirective <<INNER
+inner text
+INNER]]
+outer text
+OUTER]]
+
+ +

ikiwiki also has an older syntax for directives, which requires a space in +directives to distinguish them from wikilinks. This +syntax has several disadvantages: it requires a space after directives with +no parameters (such as [[pagecount ]]), and it prohibits spaces in +wikilinks. ikiwiki now provides the !-prefixed +syntax shown above as default. However, ikiwiki still supports wikis using +the older syntax, if the prefix_directives option is disabled.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/formatting/index.html b/ikiwiki/formatting/index.html new file mode 100644 index 0000000..bce7005 --- /dev/null +++ b/ikiwiki/formatting/index.html @@ -0,0 +1,221 @@ + + + + + + + +Formatting wiki pages + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ Formatting wiki pages + +

+ +
+ +
+ +
+ +
+

+ Posted Qua 26 Ago 2009 14:05:29 BRT +

+

Text on this wiki is, by default, written in a form very close to how you +might write text for an email message. This style of text formatting is +called MarkDown, and it works like this:

+ +

Leave blank lines between paragraphs.

+ +

You can *emphasise* or **strongly emphasise** text by placing it +in single or double asterisks.

+ +

To create a list, start each line with an asterisk:

+ +
    +
  • "* this is my list"
    • +
  • "* another item"
    • +
+ + +

To make a numbered list, start each line with a number (any number will +do) followed by a period:

+ +
    +
  1. "1. first line"
    2. +
  2. "2. second line"
    3. +
  3. "2. third line"
    4. +
+ + +

To create a header, start a line with one or more # characters followed +by a space and the header text. The number of # characters controls the +size of the header:

+ +

# h1

+ +

## h2

+ +

### h3

+ +

#### h4

+ +
##### h5
+ +
###### h6
+ +

To create a horizontal rule, just write three or more dashes or stars on +their own line:

+ +
+ +

To quote someone, prefix the quote with ">":

+ +

To be or not to be, +that is the question.

+ +

To write a code block, indent each line with a tab or 4 spaces:

+ +
10 PRINT "Hello, world!"
+20 GOTO 10
+
+ +

To link to an url or email address, you can just put the +url in angle brackets: <http://ikiwiki.info>, or you can use the +form [link text](url)

+ +
+ +

In addition to basic html formatting using MarkDown, this wiki lets +you use the following additional features:

+ +
    +

  • To link to another page on the wiki, place the page's name inside double +square brackets. So you would use [[WikiLink]] to link to WikiLink.

    • +

  • Insert smileys and some other useful symbols. :-)

    • +

  • Use shortcuts to link to common resources.

    + +

    [[!wikipedia War_of_1812]]

    • +

  • Create and fill out templates for repeated chunks of +parameterized wiki text.

    • +

  • Insert various directives onto a page to perform useful +actions. +For example, you can:

    + +
      +

    • Add a table of contents to a page:

      + +

      [[!toc ]]

      • +

    • Change the title of a page:

      + +

      [[!meta title="full page title"]]

      • +

    • Create a blog by inlining a set of pages:

      + +

      [[!inline pages="blog/*"]]

      • +
    +
    • +
+ + +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/ikiwiki.js b/ikiwiki/ikiwiki.js new file mode 100644 index 0000000..aebc5cf --- /dev/null +++ b/ikiwiki/ikiwiki.js @@ -0,0 +1,54 @@ +// ikiwiki's javascript utility function library + +var hooks; + +// Run onload as soon as the DOM is ready, if possible. +// gecko, opera 9 +if (document.addEventListener) { + document.addEventListener("DOMContentLoaded", run_hooks_onload, false); +} +// other browsers +window.onload = run_hooks_onload; + +var onload_done = 0; + +function run_hooks_onload() { + // avoid firing twice + if (onload_done) + return; + onload_done = true; + + run_hooks("onload"); +} + +function run_hooks(name) { + if (typeof(hooks) != "undefined") { + for (var i = 0; i < hooks.length; i++) { + if (hooks[i].name == name) { + hooks[i].call(); + } + } + } +} + +function hook(name, call) { + if (typeof(hooks) == "undefined") + hooks = new Array; + hooks.push({name: name, call: call}); +} + +function getElementsByClass(cls, node, tag) { + if (document.getElementsByClass) + return document.getElementsByClass(cls, node, tag); + if (! node) node = document; + if (! tag) tag = '*'; + var ret = new Array(); + var pattern = new RegExp("(^|\\s)"+cls+"(\\s|$)"); + var els = node.getElementsByTagName(tag); + for (i = 0; i < els.length; i++) { + if ( pattern.test(els[i].className) ) { + ret.push(els[i]); + } + } + return ret; +} diff --git a/ikiwiki/index.html b/ikiwiki/index.html new file mode 100644 index 0000000..eecb26b --- /dev/null +++ b/ikiwiki/index.html @@ -0,0 +1,138 @@ + + + + + + + +ikiwiki + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ ikiwiki + +

+ +
+ +
+ +
+ +
+

+ Posted Sáb 24 Abr 2010 01:43:45 BRT +

+

This wiki is powered by ikiwiki.

+ +

Some documentation on using ikiwiki:

+ + + + +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/markdown/index.html b/ikiwiki/markdown/index.html new file mode 100644 index 0000000..a14a748 --- /dev/null +++ b/ikiwiki/markdown/index.html @@ -0,0 +1,136 @@ + + + + + + + +markdown + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ markdown + +

+ +
+ +
+ +
+ +
+

+ Posted Seg 10 Nov 2008 20:40:03 BRST +

+

Markdown +is a minimal markup language that resembles plain text as used in +email messages. It is the markup language used by this wiki by default.

+ +

For documentation about the markdown syntax, see formatting and +Markdown: syntax.

+ +

Note that WikiLinks and directives are not part +of the markdown syntax, and are the only bit of markup that this wiki +handles internally.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/openid/index.html b/ikiwiki/openid/index.html new file mode 100644 index 0000000..9e77d25 --- /dev/null +++ b/ikiwiki/openid/index.html @@ -0,0 +1,142 @@ + + + + + + + +OpenID + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ OpenID + +

+ +
+ +
+ +
+ +
+

+ Posted Sex 07 Mai 2010 23:30:42 BRT +

+

This wiki has OpenID disabled.

+ +

OpenID is a decentralized authentication mechanism +that allows you to have one login that you can use on a growing number of +websites.

+ +

If you have an account with some of the larger web service providers, +you might already have an OpenID. +Directory of OpenID providers

+ +
+ +

It's also possible to make a page in the wiki usable as an OpenID url, +by delegating it to an openid server. Here's an example of how to do that:

+ +
[[!meta  openid="http://yourid.myopenid.com/"
+       server="http://www.myopenid.com/server"]]
+
+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/pagespec/attachment/index.html b/ikiwiki/pagespec/attachment/index.html new file mode 100644 index 0000000..10c0529 --- /dev/null +++ b/ikiwiki/pagespec/attachment/index.html @@ -0,0 +1,153 @@ + + + + + + + +attachment + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ attachment + +

+ +
+ +
+ +
+ +
+

+ Posted Sex 23 Abr 2010 18:36:07 BRT +

+

This wiki has attachments disabled.

+ +

If attachments are enabled, the wiki admin can control what types of +attachments will be accepted, via the allowed_attachments +configuration setting.

+ +

For example, to limit most users to uploading small images, and nothing else, +while allowing larger mp3 files to be uploaded by joey into a specific +directory, and check all attachments for viruses, something like this could be +used:

+ +
virusfree() and ((user(joey) and podcast/*.mp3 and mimetype(audio/mpeg) and maxsize(15mb)) or (mimetype(image/*) and maxsize(50kb)))
+
+ +

The regular PageSpec syntax is expanded with the following +additional tests:

+ +
    +

  • "maxsize(size)" - tests whether the attachment is no larger than the +specified size. The size defaults to being in bytes, but "kb", "mb", "gb" +etc can be used to specify the units.

    • +

  • "minsize(size)" - tests whether the attachment is no smaller than the +specified size.

    • +

  • "ispage()" - tests whether the attachment will be treated by ikiwiki as a +wiki page. (Ie, if it has an extension of ".mdwn", or of any other enabled +page format).

    + +

    So, if you don't want to allow wiki pages to be uploaded as attachments, +use !ispage() ; if you only want to allow wiki pages to be uploaded +as attachments, use ispage().

    • +

  • "mimetype(foo/bar)" - checks the MIME type of the attachment. You can +include a glob in the type, for example mimetype(image/*).

    • +

  • "virusfree()" - checks the attachment with an antiviral program.

    • +
+ + +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/pagespec/index.html b/ikiwiki/pagespec/index.html new file mode 100644 index 0000000..18608a6 --- /dev/null +++ b/ikiwiki/pagespec/index.html @@ -0,0 +1,226 @@ + + + + + + + +pagespec + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ pagespec + +

+ +
+ +
+ +
+ +
+

+ Posted Qua 20 Out 2010 20:53:50 BRST +

+

To select a set of pages, such as pages that are locked, pages +whose commit emails you want subscribe to, or pages to combine into a +blog, the wiki uses a PageSpec. This is an expression that matches +a set of pages.

+ +

The simplest PageSpec is a simple list of pages. For example, this matches +any of the three listed pages:

+ +
foo or bar or baz
+
+ +

More often you will want to match any pages that have a particular thing in +their name. You can do this using a glob pattern. "*" stands for any part +of a page name, and "?" for any single letter of a page name. So this +matches all pages about music, and any SubPages of the SandBox, but does +not match the SandBox itself:

+ +
*music* or SandBox/*
+
+ +

You can also prefix an item with "!" to skip pages that match it. So to +match all pages except for Discussion pages and the SandBox:

+ +
* and !SandBox and !*/Discussion
+
+ +

Some more elaborate limits can be added to what matches using these functions:

+ +
    +
  • "glob(someglob)" - matches pages and other files that match the given glob. +Just writing the glob by itself is actually a shorthand for this function.
    • +
  • "page(glob)" - like glob(), but only matches pages, not other files
    • +
  • "link(page)" - matches only pages that link to a given page (or glob)
    • +
  • "tagged(tag)" - matches pages that are tagged or link to the given tag (or +tags matched by a glob)
    • +
  • "backlink(page)" - matches only pages that a given page links to
    • +
  • "creation_month(month)" - matches only files created on the given month +number
    • +
  • "creation_day(mday)" - or day of the month
    • +
  • "creation_year(year)" - or year
    • +
  • "created_after(page)" - matches only files created after the given page +was created
    • +
  • "created_before(page)" - matches only files created before the given page +was created
    • +
  • "internal(glob)" - like glob(), but matches even internal-use +pages that globs do not usually match.
    • +
  • "title(glob)", "author(glob)", "authorurl(glob)", +"license(glob)", "copyright(glob)", "guid(glob)" + +
      +
    • match pages that have the given metadata, matching the specified glob.
      • +
    +
    • +
  • "user(username)" - tests whether a modification is being made by a +user with the specified username. If openid is enabled, an openid can also +be put here. Glob patterns can be used in the username. For example, +to match all openid users, use user(*://*)
    • +
  • "admin()" - tests whether a modification is being made by one of the +wiki admins.
    • +
  • "ip(address)" - tests whether a modification is being made from the +specified IP address.
    • +
  • "comment(glob)" - matches comments to a page matching the glob.
    • +
  • "comment_pending(glob)" - matches unmoderated, pending comments.
    • +
  • "postcomment(glob)" - matches only when comments are being +posted to a page matching the specified glob
    • +
+ + +

For example, to match all pages in a blog that link to the page about music +and were written in 2005:

+ +
blog/* and link(music) and creation_year(2005)
+
+ +

Note the use of "and" in the above example, that means that only pages that +match each of the three expressions match the whole. Use "and" when you +want to combine expression like that; "or" when it's enough for a page to +match one expression. Note that it doesn't make sense to say "index and +SandBox", since no page can match both expressions.

+ +

More complex expressions can also be created, by using parentheses for +grouping. For example, to match pages in a blog that are tagged with either +of two tags, use:

+ +
blog/* and (tagged(foo) or tagged(bar))
+
+ +

Note that page names in PageSpecs are matched against the absolute +filenames of the pages in the wiki, so a pagespec "foo" used on page +"a/b" will not match a page named "a/foo" or "a/b/foo". To match +relative to the directory of the page containing the pagespec, you can +use "./". For example, "./foo" on page "a/b" matches page "a/foo".

+ +

To indicate the name of the page the PageSpec is used in, you can +use a single dot. For example, link(.) matches all the pages +linking to the page containing the PageSpec.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/pagespec/po/index.html b/ikiwiki/pagespec/po/index.html new file mode 100644 index 0000000..919d6b8 --- /dev/null +++ b/ikiwiki/pagespec/po/index.html @@ -0,0 +1,140 @@ + + + + + + + +po + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ po + +

+ +
+ +
+ +
+ +
+

+ Posted Seg 12 Jul 2010 16:42:30 BRT +

+

This wiki has po support disabled.

+ +

If the po plugin is enabled, the regular +PageSpec syntax is expanded with the following additional +tests that can be used to improve user navigation in a multi-lingual +wiki:

+ +
    +
  • "lang(LL)" - tests whether a page is written in the language +specified as a ISO639-1 (two-letter) language code.
    • +
  • "currentlang()" - tests whether a page is written in the same +language as the current page.
    • +
  • "needstranslation()" - tests whether a page needs translation +work. Only slave pages match this PageSpec. A minimum target +translation percentage can optionally be passed as an integer +parameter: "needstranslation(50)" matches only pages less than 50% +translated.
    • +
+ + +

Note that every non-po page is considered to be written in +po_master_language, as specified in ikiwiki.setup.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/pagespec/sorting/index.html b/ikiwiki/pagespec/sorting/index.html new file mode 100644 index 0000000..fbdd48e --- /dev/null +++ b/ikiwiki/pagespec/sorting/index.html @@ -0,0 +1,138 @@ + + + + + + + +sorting + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ sorting + +

+ +
+ +
+ +
+ +
+

+ Posted Sáb 12 Nov 2011 14:02:20 BRST +

+

Some directives that use +PageSpecs allow +specifying the order that matching pages are shown in. The following sort +orders can be specified.

+ +
    +

  • age - List pages from the most recently created to the oldest.

    • +

  • mtime - List pages with the most recently modified first.

    • +

  • title - Order by title (page name), e.g. "z/a a/b a/c"

    • +

  • path - Order by page name including parents, e.g. "a/b a/c z/a"

    • +

  • meta(title) - Order according to the [[!meta title="foo" sortas="bar"]] +or [[!meta title="foo"]] directive, or the page name if no +full title was set. meta(author), meta(date), meta(updated), etc. +also work.

    • +
+ + +

In addition, you can combine several sort orders and/or reverse the order of +sorting, with a string like age -title (which would sort by age, then by +title in reverse order if two pages have the same age).

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/relativedate.js b/ikiwiki/relativedate.js new file mode 100644 index 0000000..2a270d6 --- /dev/null +++ b/ikiwiki/relativedate.js @@ -0,0 +1,75 @@ +// Causes html elements in the 'relativedate' class to be displayed +// as relative dates. The date is parsed from the title attribute, or from +// the element content. + +var dateElements; + +hook("onload", getDates); + +function getDates() { + dateElements = getElementsByClass('relativedate'); + for (var i = 0; i < dateElements.length; i++) { + var elt = dateElements[i]; + var title = elt.attributes.title; + var d = new Date(title ? title.value : elt.innerHTML); + if (! isNaN(d)) { + dateElements[i].date=d; + elt.title=elt.innerHTML; + } + } + + showDates(); +} + +function showDates() { + for (var i = 0; i < dateElements.length; i++) { + var elt = dateElements[i]; + var d = elt.date; + if (! isNaN(d)) { + elt.innerHTML=relativeDate(d); + } + } + setTimeout(showDates,30000); // keep updating every 30s +} + +var timeUnits = [ + { unit: 'year', seconds: 60 * 60 * 24 * 364 }, + { unit: 'month', seconds: 60 * 60 * 24 * 30 }, + { unit: 'day', seconds: 60 * 60 * 24 }, + { unit: 'hour', seconds: 60 * 60 }, + { unit: 'minute', seconds: 60 }, +]; + +function relativeDate(date) { + var now = new Date(); + var offset = date.getTime() - now.getTime(); + var seconds = Math.round(Math.abs(offset) / 1000); + + // hack to avoid reading just in the future if there is a minor + // amount of clock slip + if (offset >= 0 && seconds < 30 * 60 * 60) { + return "just now"; + } + + var ret = ""; + var shown = 0; + for (i = 0; i < timeUnits.length; i++) { + if (seconds >= timeUnits[i].seconds) { + var num = Math.floor(seconds / timeUnits[i].seconds); + seconds -= num * timeUnits[i].seconds; + if (ret) + ret += "and "; + ret += num + " " + timeUnits[i].unit + (num > 1 ? "s" : "") + " "; + + if (++shown == 2) + break; + } + else if (shown) + break; + } + + if (! ret) + ret = "less than a minute " + + return ret + (offset < 0 ? "ago" : "from now"); +} diff --git a/ikiwiki/searching/index.html b/ikiwiki/searching/index.html new file mode 100644 index 0000000..f977a66 --- /dev/null +++ b/ikiwiki/searching/index.html @@ -0,0 +1,143 @@ + + + + + + + +searching + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ searching + +

+ +
+ +
+ +
+ +
+

+ Posted Qua 26 Ago 2009 14:05:46 BRT +

+

This wiki has searching disabled.

+ +

If searching is enabled, you can enter search terms in the search field, +as you'd expect. There are a few special things you can do to construct +more powerful searches.

+ +
    +
  • To match a phrase, enclose it in double quotes.
    • +
  • AND can be used to search for documents containing two expressions.
    • +
  • OR can be used to search for documents containing either one of +two expressions.
    • +
  • Parentheses can be used to build up complicated search expressions. For +example, "(foo AND bar) OR (me AND you)"
    • +
  • Prefix a search term with "-" to avoid it from appearing in the results. +For example, "-discussion" will omit "discussion".
    • +
  • To search for a page with a given title, use "title:foo".
    • +
  • To search for pages that contain a "bar" link, use "link:bar".
    • +
+ + +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/subpage/index.html b/ikiwiki/subpage/index.html new file mode 100644 index 0000000..b40786c --- /dev/null +++ b/ikiwiki/subpage/index.html @@ -0,0 +1,141 @@ + + + + + + + +subpage + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ subpage + +

+ +
+ +
+ +
+ +
+

+ Posted Sáb 24 Abr 2010 01:55:09 BRT +

+

ikiwiki supports placing pages in a directory hierarchy. For example, +this page, SubPage has some related pages placed under it, like +LinkingRules. This is a useful way to add some order to your +wiki rather than just having a great big directory full of pages.

+ +

To add a SubPage, just make a subdirectory and put pages in it. For +example, this page is subpage.mdwn in this wiki's source, and there is also +a subpage subdirectory, which contains subpage/linkingrules.mdwn. Subpages +can be nested as deeply as you'd like.

+ +

Linking to and from a SubPage is explained in LinkingRules.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/subpage/linkingrules/index.html b/ikiwiki/subpage/linkingrules/index.html new file mode 100644 index 0000000..112e4f2 --- /dev/null +++ b/ikiwiki/subpage/linkingrules/index.html @@ -0,0 +1,160 @@ + + + + + + + +linkingrules + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ linkingrules + +

+ +
+ +
+ +
+ +
+

+ Posted Sáb 04 Out 2008 11:11:08 BRT +

+

To link to or from a SubPage, you can normally use a regular +WikiLink that does not contain the name of the parent directory of +the SubPage. Ikiwiki descends the directory hierarchy looking for a +page that matches your link.

+ +

For example, if FooBar/SubPage links to "OtherPage", ikiwiki will first +prefer pointing the link to FooBar/SubPage/OtherPage if it exists, next +to FooBar/OtherPage and finally to OtherPage in the root of the wiki.

+ +

Note that this means that if a link on FooBar/SomePage to "OtherPage" +currently links to OtherPage, in the root of the wiki, and FooBar/OtherPage +is created, the link will change to point to FooBar/OtherPage. On the +other hand, a link from BazBar to "OtherPage" would be unchanged by this +creation of a SubPage of FooBar.

+ +

You can also specify a link that contains a directory name, like +"FooBar/OtherPage" to more exactly specify what page to link to. This is +the only way to link to an unrelated SubPage.

+ +

You can use this to, for example, to link from BazBar to "FooBar/SubPage", +or from BazBar/SubPage to "FooBar/SubPage".

+ +

You can also use "/" at the start of a link, to specify exactly which page +to link to, when there are multiple pages with similar names and the link +goes to the wrong page by default. For example, linking from +"FooBar/SubPage" to "/OtherPage" will link to the "OtherPage" in the root +of the wiki, even if there is a "FooBar/OtherPage".

+ +

Also, if the wiki is configured with a userdir, you can link to pages +within the userdir without specifying a path to them. This is to allow for +easy linking to a user's page in the userdir, to sign a comment. These +links are checked for last of all.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + diff --git a/ikiwiki/toggle.js b/ikiwiki/toggle.js new file mode 100644 index 0000000..d190b73 --- /dev/null +++ b/ikiwiki/toggle.js @@ -0,0 +1,29 @@ +// Uses CSS to hide toggleables, to avoid any flashing on page load. The +// CSS is only emitted after it tests that it's going to be able +// to show the toggleables. +if (document.getElementById && document.getElementsByTagName && document.createTextNode) { + document.write(''); + hook("onload", inittoggle); +} + +function inittoggle() { + var as = getElementsByClass('toggle'); + for (var i = 0; i < as.length; i++) { + var id = as[i].href.match(/#(\w.+)/)[1]; + if (document.getElementById(id).className == "toggleable") + document.getElementById(id).style.display="none"; + as[i].onclick = function() { + toggle(this); + return false; + } + } +} + +function toggle(s) { + var id = s.href.match(/#(\w.+)/)[1]; + style = document.getElementById(id).style; + if (style.display == "none") + style.display = "block"; + else + style.display = "none"; +} diff --git a/ikiwiki/wikilink/index.html b/ikiwiki/wikilink/index.html new file mode 100644 index 0000000..3e79500 --- /dev/null +++ b/ikiwiki/wikilink/index.html @@ -0,0 +1,164 @@ + + + + + + + +wikilink + + + + + + + + + + + + + + +
+ +
+
+

+ + +
+
+ +
+ +
+
+
+

+ wikilink + +

+ +
+ +
+ +
+ +
+

+ Posted Qua 23 Jun 2010 15:23:09 BRT +

+

WikiLinks provide easy linking between pages of the wiki. To create a +WikiLink, just put the name of the page to link to in double brackets. +For example [[WikiLink]].

+ +

If you ever need to write something like [[WikiLink]] without creating a +wikilink, just prefix it with a \, like \[[WikiLink]].

+ +

There are some special LinkingRules that come into play when +linking between SubPages.

+ +

WikiLinks are matched with page names in a case-insensitive manner, so you +don't need to worry about getting the case the same, and can capitalise +links at the start of a sentence, and so on.

+ +

It's also possible to write a WikiLink that uses something other than the page +name as the link text. For example [[foo_bar|SandBox]] links to the SandBox +page, but the link will appear like this: foo bar.

+ +

To link to an anchor inside a page, you can use something like +[[WikiLink#foo]] .

+ +

If the file linked to by a WikiLink looks like an image, it will +be displayed inline on the page.

+ +
+ +

You can also put an url in a WikiLink, to link to an external page. +Email addresses can also be used to generate a mailto link.

+ +
+ +
+ + + + + +
+ + + +
+ +
+ + + +
+ +
+
+ + + -- cgit v1.2.3