1 The `inline` directive is supplied by the [[!iki plugins/inline desc=inline]] plugin.
3 This is a directive that allows including one wiki page inside another.
4 The most common use of inlining is generating blogs and RSS or Atom feeds.
8 \[[!inline pages="blog/* and !*/Discussion" show="10" rootpage="blog"]]
10 Any pages that match the specified [[PageSpec]] (in the example, any
11 [[SubPage]] of "blog") will be part of the blog, and the newest 10
12 of them will appear in the page. Note that if files that are not pages
13 match the [[PageSpec]], they will be included in the feed using RSS
14 enclosures, which is useful for podcasting.
16 The optional `rootpage` parameter tells the wiki that new posts to this
17 blog should default to being [[SubPages|SubPage]] of "blog", and enables a
18 form at the top of the blog that can be used to add new items.
20 If you want your blog to have an archive page listing every post ever made
21 to it, you can accomplish that like this:
23 \[[!inline pages="blog/* and !*/Discussion" archive="yes"]]
25 You can even create an automatically generated list of all the pages on the
26 wiki, with the most recently added at the top, like this:
28 \[[!inline pages="* and !*/Discussion" archive="yes"]]
30 If you want to be able to add pages to a given blog feed by tagging them,
31 you can do that too. To tag a page, just make it link to a page or pages
32 that represent its tags. Then use the special `link()` [[PageSpec]] to match
33 all pages that have a given tag:
35 \[[!inline pages="link(life)"]]
37 Or include some tags and exclude others:
39 \[[!inline pages="link(debian) and !link(social)"]]
43 There are many parameters you can use with the `inline`
44 directive. These are the commonly used ones:
46 * `pages` - A [[PageSpec]] of the pages to inline.
47 * `show` - Specify the maximum number of matching pages to inline.
48 Default is 10, unless archiving, when the default is to show all.
49 Set to 0 to show all matching pages.
50 * `archive` - If set to "yes", only list page titles and some metadata, not
52 * `description` - Sets the description of the rss feed if one is generated.
53 Defaults to the name of the wiki.
54 * `skip` - Specify a number of pages to skip displaying. Can be useful
55 to produce a feed that only shows archived pages.
56 * `postform` - Set to "yes" to enable a form to post new pages to a
58 * `postformtext` - Set to specify text that is displayed in a postform.
59 * `rootpage` - Enables the postform, and allows controling where
60 newly posted pages should go, by specifiying the page that
61 they should be a [[SubPage]] of.
63 Here are some less often needed parameters:
65 * `actions` - If set to "yes" add links to the bottom of the inlined pages
66 for editing and discussion (if they would be shown at the top of the page
68 * `rss` - controls generation of an rss feed. If the wiki is configured to
69 generate rss feeds by default, set to "no" to disable. If the wiki is
70 configured to `allowrss`, set to "yes" to enable.
71 * `atom` - controls generation of an atom feed. If the wiki is configured to
72 generate atom feeds by default, set to "no" to disable. If the wiki is
73 configured to `allowatom`, set to "yes" to enable.
74 * `feeds` - controls generation of all types of feeds. Set to "no" to
75 disable generating any feeds.
76 * `emptyfeeds` - Set to "no" to disable generation of empty feeds.
77 Has no effect if `rootpage` or `postform` is set.
78 * `template` - Specifies the template to fill out to display each inlined
79 page. By default the `inlinepage` template is used, while
80 the `archivepage` template is used for archives. Set this parameter to
81 use some other, custom template, such as the `titlepage` template that
82 only shows post titles or the `microblog` template, optimised for
83 microblogging. Note that you should still set `archive=yes` if
84 your custom template does not include the page content.
85 * `raw` - Rather than the default behavior of creating a blog,
86 if raw is set to "yes", the page will be included raw, without additional
87 markup around it, as if it were a literal part of the source of the
89 * `sort` - Controls how inlined pages are [[sorted|pagespec/sorting]].
90 The default is to sort the newest created pages first.
91 * `reverse` - If set to "yes", causes the sort order to be reversed.
92 * `feedshow` - Specify the maximum number of matching pages to include in
93 the rss/atom feeds. The default is the same as the `show` value above.
94 * `feedonly` - Only generate the feed, do not display the pages inline on
96 * `quick` - Build archives in quick mode, without reading page contents for
97 metadata. This also turns off generation of any feeds.
98 * `timeformat` - Use this to specify how to display the time or date for pages
99 in the blog. The format string is passed to the strftime(3) function.
100 * `feedpages` - A [[PageSpec]] of inlined pages to include in the rss/atom
101 feeds. The default is the same as the `pages` value above, and only pages
102 matched by that value are included, but some of those can be excluded by
103 specifying a tighter [[PageSpec]] here.
104 * `guid` - If a URI is given here (perhaps a UUID prefixed with `urn:uuid:`),
105 the Atom feed will have this as its `<id>`. The default is to use the URL
106 of the page containing the `inline` directive.
107 * `feedfile` - Can be used to change the name of the file generated for the
108 feed. This is particularly useful if a page contains multiple feeds.
109 For example, set "feedfile=feed" to cause it to generate `page/feed.atom`
110 and/or `page/feed.rss`. This option is not supported if the wiki is
111 configured not to use `usedirs`.
112 * `pagenames` - If given instead of `pages`, this is interpreted as a
113 space-separated list of links to pages (with the same
114 [[SubPage/LinkingRules]] as in a [[ikiwiki/WikiLink]]), and they are inlined
115 in exactly the order given: the `sort` and `pages` parameters cannot be used
116 in conjunction with this one.
118 [[!meta robots="noindex, follow"]]
projects / ikiwiki / blob