Mikio Template

The following pages can be either html files in the root of the template or a page in the namespace. Namespace pages take priority.

• topheader : content to include above the navbar
• header : content include below the navbar but above the page content
• contentheader : content to include above the page content
• contentfooter : content to include below the page content
• sidebarheader : content to include above the left sidebar content
• sidebarfooter : content to include below the left sidebar content
• rightsidebarheader : content to include above the right sidebar content
• rightsidebarfooter : content to include below the right sidebar content
• footer : content to include in the footer
• bottomfooter : content to include below the footer

The following images can be used to replace content in the template. Images can be in `TEMPLATE_ROOT/images/`, `TEMPLATE_ROOT/themes/THEME/images/`, or in the namespace. Images can be either png, jpg, gif or svg.

• logo : site logo in the navbar
• breadcrumb-prefix breadcrumb prefix
• breadcrumb-sep breadcrumb seperator
• hero hero image for hero element

Mikio now supports hiding elements using the ~~hide-parts (parts)~~ macro. Each element within the hide-parts macro is required to be separated by spaces. Currently, the following parts are supported:

• topheader : content above the navbar
• navbar : the main navigation bar
• header : content below the navbar but above the page content
• hero : the page hero bar
• contentheader : content above the page content
• contentfooter : content below the page content
• sidebarheader : content above the left sidebar content
• sidebarfooter : content below the left sidebar content
• rightsidebarheader : content above the right sidebar content
• rightsidebarfooter : content below the right sidebar content
• footer : content in the footer
• bottomfooter : content below the footer

To hide the topheader, navbar and hero, you would use the macro ~~hide-parts topheader navbar hero~~

Include Plugin

{{page>wiki:syntax#Tables}} will include the section about tables of the syntax page.

{{namespace>project_foo}} will include all pages in the project_foo namespace.

{{page>blog:mypage&tags&comments}} will include the page blog:mypage and show the tags from the Tag plugin and the number of comments from the discussion plugin. Both plugins need to be installed for this example.

{{tagtopic>testtag}} will include all pages with the tag testtag, the Tag plugin needs to be installed for this example.

Simply enclose the ID of the page to be included in double curly brackets:

{{page>[id]&[flags]}}
{{section>[id]#[section]&[flags]}}
{{namespace>[namespace]#[section]&[flags]}}
{{tagtopic>[tag]&[flags]}}

The plugin offers four syntaxes, {{page>...}} , {{section>...}} , {{namespace>...}} and {{tagtopic>...}}.

Section is aimed more at including sections, page at including whole pages and namespace at including whole namespaces. Tagtopic includes all pages with a tagtopic tag.

The plugin can be configured in the DokuWiki configuration manager available in the admin menu. These settings also affect the blog plugin which uses the include plugin to generate the blog page. For most settings there are flags that allow to override the setting. Some features are only available as flag.

Examples:

{{page>concept&firstseconly&footer}}
{{page>mypage&noindent}}
{{namespace>myns&order=modified}}
{{namespace>myns&exclude=/myns:subns:.+|myns:page/}}

Simple macros are possible to serve a page on a per user or per date base. These are:

<expr> in @DATE<expr>@ can be one of:

Examples:

{{page>@MONTH@:@DAY@:birthdays}}

includes the page birthdays in namespace <month>:<day>: eg. 10:15: birthdays for the 15th of october.

{{page>@USER@:message}}

includes the page message from the namespace <user> of the logged in user

{{page>foo@DATENWEEK@@YEAR@:@WEEK@}}

includes the page <weekno> from the namespace foo<year> with next week's date e.g. foo2012:01 for the 27th of december 2011