* *item*
* item
-[[WikiLink]]
+[[ikiwiki/WikiLink]]
> The above examples are ambiguous, only worked due to a bug, and were
> never documented to work. So I'm not inclined to re-add support for them.
>
-> If you look at [[WikiLink]], it is clear that spaces cannot be used in
+> If you look at [[ikiwiki/WikiLink]], it is clear that spaces cannot be used in
> WikiLinks. It also shows how to use underscores in the link text if you
> want multiple words.
>
-A trailing slash on a [[wikilink]] breaks the link:
+A trailing slash on a [[ikiwiki/wikilink]] breaks the link:
`\[[todo/Gallery/]]` appears as [[todo/Gallery/]].
On <http://phd.martin-krafft.net/wiki/tag/factors/ideology/>, another symptom of this problem can be seen: the page collects pages linking to `tag/factors/ideology`, and `/factors/language` is one of those. However, the link points to `tag/factors/language`, which does *not* link to `tag/factors/ideology`.
-I think this is an artefact of the intersection of ikiwiki [[SubPage/LinkingRules]] with the use of a page's basename when its path relative to the wikiroot should be used.
\ No newline at end of file
+I think this is an artefact of the intersection of ikiwiki [[ikiwiki/SubPage/LinkingRules]] with the use of a page's basename when its path relative to the wikiroot should be used.
In [[ikiwiki/markdown]] syntax, none of the other special characters get processed
-inside a code block. However, in ikiwiki, [[wiki_links|wikilink]] and
+inside a code block. However, in ikiwiki, [[wiki_links|ikiwiki/wikilink]] and
[[preprocessor_directives|ikiwiki/preprocessordirective]] still get processed
inside a code block, requiring additional escaping. For example, `[links
-don't work](#here)`, but `a [[wikilink]] becomes HTML`. --[[JoshTriplett]]
+don't work](#here)`, but `a [[ikiwiki/wikilink]] becomes HTML`. --[[JoshTriplett]]
Indented lines provide a good way to escape a block of text containing
markdown syntax, but ikiwiki links like \[[this]] are still
[[template id=plugin name=camelcase author="[[Joey]]"]]
-This plugin makes words in CamelCase be treated as a [[WikiLink]]. That is
-to say, any two or more words capitalised and mashed together are assumed
-to be the name of some other page on the wiki, and so become a link.
+This plugin makes words in CamelCase be treated as a [[ikiwiki/WikiLink]].
+That is to say, any two or more words capitalised and mashed together are
+assumed to be the name of some other page on the wiki, and so become a
+link.
If this plugin is enabled, this will be a link: SandBox
html pages will still be wrapped in the same html template as any other
page, so for best results you should include only the page body in the html
file. Also, if the [[htmlscrubber]] plugin is enabled, the html pages will be
-sanitised like any other page. You can also use standard [[WikiLink]]s etc
-in the html pages.
+sanitised like any other page. You can also use standard
+[[WikiLinks|ikiwiki/WikiLink]] etc in the html pages.
This plugin is included in ikiwiki, but is not enabled by default.
[[tag type/chrome]]
This is an image handling plugin. While ikiwiki supports inlining full-size
-images by making a [[WikiLink]] that points to the image, using this plugin
-you can easily scale down an image for inclusion onto a page, providing a
-link to a full-size version.
+images by making a [[ikiwiki/WikiLink]] that points to the image, using
+this plugin you can easily scale down an image for inclusion onto a page,
+providing a link to a full-size version.
This plugin uses the [ImageMagick](http://www.imagemagick.org/) tools via
[PerlMagick](http://www.imagemagick.org/www/perl-magick.html).
\[[img image1.jpg size="200x200" alt="clouds"]]
The image file will be searched for using the same rules as used to find
-the file pointed to by a [[WikiLink]].
+the file pointed to by a [[ikiwiki/WikiLink]].
The `size` parameter is optional, defaulting to full size. Note that the
original image's aspect ratio is always preserved, even if this means
It would be useful (at least for me) if one could specify
-(using a [[WikiLink]]) where the image links to. For example,
+(using a [[ikiwiki/WikiLink]]) where the image links to. For example,
on <http://www.bddebian.com/~wiki/sidebar/> I'd like to have the
logo link to \[[hurd/logo]] / <http://www.bddebian.com/~wiki/hurd/logo/>
instead of linking to the PNG image file. --[[tschwinge]]
Specifies a link to another page. This can be used as a way to make the
wiki treat one page as linking to another without displaying a user-visible
- [[WikiLink]]:
+ [[ikiwiki/WikiLink]]:
\[[meta link=otherpage]]
--[[Paweł|ptecza]]
-> As with any other parameter in a [[preprocessordirective]], you can
+> As with any other parameter in a [[ikiwiki/preprocessordirective]], you can
> triple-quote, and then include quotation marks inside. --[[Joey]]
>> Thanks for the hint! Toggle plugin is probably my favourite ikiwiki
->> plugin, but I forget about that :D --[[Paweł|ptecza]]
\ No newline at end of file
+>> plugin, but I forget about that :D --[[Paweł|ptecza]]
ikiwiki. Limitations include:
* There are issues with inserting raw html into documents, as ikiwiki
- does with [[WikiLinks|WikiLink]] and many
+ does with [[WikiLinks|ikiwiki/WikiLink]] and many
[[PreprocessorDirectives|ikiwiki/PreprocessorDirective]].
So while you may find this useful for importing old files into your wiki,
\[[tag tech life linux]]
-The tags work the same as if you had put a (hidden) [[WikiLink]] on the page
-for each tag, so you can use a [[ikiwiki/PageSpec]] match all pages that are
-tagged with a given tag, for example. The tags will also show up on blog
-entries and at the bottom of the tagged pages, as well as in RSS and Atom
-feeds.
+The tags work the same as if you had put a (hidden) [[ikiwiki/WikiLink]] on
+the page for each tag, so you can use a [[ikiwiki/PageSpec]] match all
+pages that are tagged with a given tag, for example. The tags will also
+show up on blog entries and at the bottom of the tagged pages, as well as
+in RSS and Atom feeds.
-If you want a visible [[WikiLink]] along with the tag, use taglink instead:
+If you want a visible [[ikiwiki/WikiLink]] along with the tag, use taglink
+instead:
\[[taglink foo]]
\[[taglink tagged_as_foo|foo]]
-These plugins deal with [[WikiLinks|WikiLink]].
+These plugins deal with [[WikiLinks|ikiwiki/WikiLink]].
turn into the appropriate tags. Headers are matching equals signs around
the header text -- the more signs, the lesser the header.
-Links are standard [[WikiLinks|WikiLink]], although you can also enable
+Links are standard [[WikiLinks|ikiwiki/WikiLink]], although you can also enable
[[CamelCase]] links.
Lists are indented text, by one tab or four spaces. In unordered lists,
## Different sorts of links:
-* [[WikiLink]]
-* [[different_name_for_a_WikiLink|WikiLink]]
+* [[Features]]
+* [[different_name_for_a_WikiLink|ikiwiki/WikiLink]]
* <http://www.gnu.org/>
* [GNU](http://www.gnu.org/)
* [Email](mailto:noone@invalid)
This sandbox is also a [[ikiwiki/blog]]!
[[inline pages="sandbox/* and !*/Discussion" rootpage="sandbox" show="4" archive="yes"]]
-
-[[blubb]]
To change the supported smileys, just edit the lists on this page.
Note that the format is important; each list item should start with the
text that is turned into the smiley, escaped so that users can see what
-produces it, followed by a [[WikiLink]] to the image to display.
+produces it, followed by a [[ikiwiki/WikiLink]] to the image to display.
/!\ Bear in mind that the link to the image needs to be written in a way that
will work if it's copied to other pages on the wiki. So be sure to include the
\[[taglink mytag]]
-This tag will be displayed just like a regular [[WikiLink]].
+This tag will be displayed just like a regular [[ikiwiki/WikiLink]].
One way to use these tags is to create a [[ikiwiki/blog]] of pages that have a
particular set of tags. Or just look at the [[BackLinks]] to a tag page to
**URL** = http://some.nice/place/ (*etc.*)
-**WHITHER** = \[\[**[[wikilink]]**]] | **URL**
+**WHITHER** = \[\[**[[ikiwiki/wikilink]]**]] | **URL**
**D** = natural number (*meaning seconds*)
>> (How to qualify a valid target address?)
>> What is a *cyclic meta refresh loop*? Two pages in turn forwarding to each other?
>> I think it would be possible to implement such a guard when only in-wiki links
->> ([[wikilink]]s) are being used, but how to do so for external links? --[[tschwinge]]
+>> ([[ikiwiki/wikilink]]s) are being used, but how to do so for external links? --[[tschwinge]]
>>> This seems a lot more securely to do for in-wiki links, since we know
>>> that a link generated by a wikilink is safe, and can avoid cycles.
-Since `/` now works in [[WikiLink]]s to anchor links to the root of the site
+Since `/` now works in [[ikiwiki/WikiLink]]s to anchor links to the root of the site
(for instance, `\[[/index]]`), `/` alone should work as a reference to the
top-level index page (for instance, `\[[Home|/]]`). --[[JoshTriplett]]
-There's nothing in [[fileupload]] that suggests putting the file upload limit in the body of a page. That would indeed be a strange choice. Ikiwiki already uses [[PageSpecs|PageSpec]] in the Preferences page (for specifying locked pages, banned users, and subscriptions), and I had envisioned putting the file upload controls there, and possibly subsuming some of those other controls into them.
+There's nothing in [[fileupload]] that suggests putting the file upload limit in the body of a page. That would indeed be a strange choice. Ikiwiki already uses [[PageSpecs|ikiwiki/PageSpec]] in the Preferences page (for specifying locked pages, banned users, and subscriptions), and I had envisioned putting the file upload controls there, and possibly subsuming some of those other controls into them.
> Thanks for clarifying; I clearly misunderstood the original text. -- Ben
-It's not clear to me that the concept of attaching files to a page fits ikiwiki very well; unlike most wikis, ikiwiki supports subdirectories and [[SubPages|SubPage]], which allows for hierarchical placement of uploaded files, which is a much more flexible concept than simple attachment. Futhermore, the idea of listing all attached files at the bottom of a page seems somewhat inflexible. What if I want to make a podcast, using inline's existing support for that -- I won't want a list of every "attached" file at the bottom of my podcast's page then.
+It's not clear to me that the concept of attaching files to a page fits ikiwiki very well; unlike most wikis, ikiwiki supports subdirectories and [[SubPages|ikiwiki/SubPage]], which allows for hierarchical placement of uploaded files, which is a much more flexible concept than simple attachment. Futhermore, the idea of listing all attached files at the bottom of a page seems somewhat inflexible. What if I want to make a podcast, using inline's existing support for that -- I won't want a list of every "attached" file at the bottom of my podcast's page then.
> If a file was attached to _some-dir/some-page_, it would be stored in _some-dir/_ and linked from _some-page_. That would seem reasonably hierarchical to me. What do you suggest as an alternative?
> I did an proof of concept implementation of this idea [here](http://ng.l4x.org/brainstorm/gallery/) yesterday night, including the link to the source code. I'd really love to hear comments about this approach.
(note1: I'm really not interested in any kind of http interface to that thing, just testing ways of storing the meta
- data, note2: I'm no perl programmer)
\ No newline at end of file
+ data, note2: I'm no perl programmer)
-* reStructuredText does not allow raw html to be inserted into
- documents, but ikiwiki does so in many cases, including
-- [[WikiLinks|WikiLink]] and many
+- [[WikiLinks|ikiwiki/WikiLink]] and many
- [[PreprocessorDirectives|ikiwiki/PreprocessorDirective]].
+* Some bits of ikiwiki may still assume that markdown is used or embed html
+ in ways that break reStructuredText. (Report bugs if you find any.)
Pages could have a `linktitle` (perhaps via [[plugins/meta]]), and
-[[wikilinks|wikilink]] could use that title by default when linking to the
-page. That would allow pages to have a simple, easily linkable name
+[[wikilinks|ikiwiki/wikilink]] could use that title by default when linking
+to the page. That would allow pages to have a simple, easily linkable name
(without spaces, for instance), but use the proper title for links. For
example, [[ikiwiki/PreprocessorDirective]] could use the `linktitle`
"preprocessor directive", and pages for [[users]] could have `linktitle`s
Perhaps a powerful little UNDO feature on RecentChanges is all that is needed.
> Um, if you'll look at the [[mailnotification]] page, ikiwiki has
-> supported mail notifications for > 1 year, with a powerful [[PageSpec]]
+> supported mail notifications for > 1 year, with a powerful [[ikiwiki/PageSpec]]
> to allow chosing which pages you want to be notified about. --[[Joey]]
projects / ikiwiki.git / commitdiff