urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ikiwiki/templates/page.tmpl

223 lines
5.9 KiB
Cheetah
Raw Normal View History

Always produce HTML5 doctype and new attributes, but not new elements According to caniuse.com, a significant fraction of Web users are still using Internet Explorer versions that do not support HTML5 sectioning elements. However, claiming we're XHTML 1.0 Strict means we can't use features invented in the last 12 years, even if they degrade gracefully in older browsers (like the role and placeholder attributes). This means our output is no longer valid according to any particular DTD. Real browsers and other non-validator user-agents have never cared about DTD compliance anyway, so I don't think this is a real loss.
2014-10-16 12:04:53 +02:00
<!DOCTYPE html>
Emit vestigial xmlns so people can still pass ikiwiki output through XSLT
2014-10-16 12:25:28 +02:00
<html xmlns="http://www.w3.org/1999/xhtml">
css support
2006-03-29 09:24:03 +02:00
<head>
rename ispage variable
2010-05-06 04:36:50 +02:00
<TMPL_IF DYNAMIC>
add NEWS about template change
2010-05-06 03:51:03 +02:00
<TMPL_IF FORCEBASEURL><base href="<TMPL_VAR FORCEBASEURL>" /><TMPL_ELSE>
<TMPL_IF BASEURL><base href="<TMPL_VAR BASEURL>" /></TMPL_IF>
add the <base> setting as in misc.tmpl; only ever do it if not ispage Also, add FOOTER, to allow disabling the footer.
2010-05-06 00:18:50 +02:00
</TMPL_IF>
bugfix
2010-05-06 04:44:08 +02:00
</TMPL_IF>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><meta charset="utf-8" /><TMPL_ELSE><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /></TMPL_IF>
the real bug turned out to be in the meta plugin
2007-03-21 07:46:06 +01:00
<title><TMPL_VAR TITLE></title>
page.tmpl: tell mobile browsers we have a responsive layout, unless told not to Mobile browsers typically assume that arbitrary web pages are designed for a "desktop-sized" browser window (around 1000px) and display that layout, zoomed out, in order to avoid breaking naive designs that assume nobody will ever look at a website on a phone or something. People who are actually doing "responsive design" need to opt-in to mobile browsers rendering it at a more normal size.
2014-11-26 01:02:55 +01:00
<TMPL_IF RESPONSIVE_LAYOUT><meta name="viewport" content="width=device-width, initial-scale=1" /></TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF FAVICON>
fix mime type
2006-09-17 19:46:51 +02:00
<link rel="icon" href="<TMPL_VAR BASEURL><TMPL_VAR FAVICON>" type="image/x-icon" />
* Reorganised the doc wiki's todo/* pages, using a link/tag to flag * Allow pagetemplate plugins to override *anything* in the template. * Add a meta plugin, which allows specifying various metadata about pages, like license and author. It also allows for inserting html link and meta tags into html, overriding the title, and adding hidden WikiLinks, which can be useful when using link-based globbing for page categorisation. * Remove preprocessor directives from inlined pages. * Allow simple preprocessor directive values to be specified w/o quotes.
2006-06-02 06:49:12 +02:00
</TMPL_IF>
* Reorder the icon in the template above the stylesheets, to avoid icon flashing during page load.
2007-04-06 19:31:00 +02:00
<link rel="stylesheet" href="<TMPL_VAR BASEURL>style.css" type="text/css" />
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF LOCAL_CSS>
localstyle: New plugin, allows overrding the toplevel local.css with one that is closer to a page. I chose not to have it override style.css, because style.css is not really intended to be edited; the one from the underlay is intended to be used as a base that local.css overrides. I chose to use a plugin rather than changing the default behavior, both because I didn't want to have to worry about possibly breaking backwards compatability (though this seems unlikely), and because it seemed cleaner to not include style template parameters in the main page template code. I suppose someone might want a way to not override the toplevel local.css, but instead include it as well as foo/local.css. Probably the best way to do that would be to have foo/local.css @import ../local.css (modulo browser compatability issues). Alternatively, edit page.tmpl to always include the toplevel local.css, or swap out this plugin for another one.
2009-11-09 19:32:08 +01:00
<link rel="stylesheet" href="<TMPL_VAR BASEURL><TMPL_VAR LOCAL_CSS>" type="text/css" />
<TMPL_ELSE>
* Reorder the icon in the template above the stylesheets, to avoid icon flashing during page load.
2007-04-06 19:31:00 +02:00
<link rel="stylesheet" href="<TMPL_VAR BASEURL>local.css" type="text/css" />
localstyle: New plugin, allows overrding the toplevel local.css with one that is closer to a page. I chose not to have it override style.css, because style.css is not really intended to be edited; the one from the underlay is intended to be used as a base that local.css overrides. I chose to use a plugin rather than changing the default behavior, both because I didn't want to have to worry about possibly breaking backwards compatability (though this seems unlikely), and because it seemed cleaner to not include style template parameters in the main page template code. I suppose someone might want a way to not override the toplevel local.css, but instead include it as well as foo/local.css. Probably the best way to do that would be to have foo/local.css @import ../local.css (modulo browser compatability issues). Alternatively, edit page.tmpl to always include the toplevel local.css, or swap out this plugin for another one.
2009-11-09 19:32:08 +01:00
</TMPL_IF>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
<TMPL_UNLESS DYNAMIC>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF EDITURL>
Add support for the universal edit button <http://universaleditbutton.org/> Not forcing a rebuild on upgrade just for this.
2008-06-21 22:56:47 +02:00
<link rel="alternate" type="application/x-wiki" title="Edit this page" href="<TMPL_VAR EDITURL>" />
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF FEEDLINKS><TMPL_VAR FEEDLINKS></TMPL_IF>
<TMPL_IF RELVCS><TMPL_VAR RELVCS></TMPL_IF>
<TMPL_IF META><TMPL_VAR META></TMPL_IF>
trail: new plugin (3rd attempt)
2011-11-04 20:32:41 +01:00
<TMPL_LOOP TRAILLOOP>
<TMPL_IF PREVPAGE>
<link rel="prev" href="<TMPL_VAR PREVURL>" title="<TMPL_VAR PREVTITLE>" />
</TMPL_IF>
<link rel="up" href="<TMPL_VAR TRAILURL>" title="<TMPL_VAR TRAILTITLE>" />
<TMPL_IF NEXTPAGE>
<link rel="next" href="<TMPL_VAR NEXTURL>" title="<TMPL_VAR NEXTTITLE>" />
</TMPL_IF>
</TMPL_LOOP>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
</TMPL_UNLESS>
css support
2006-03-29 09:24:03 +02:00
</head>
use template for page rendering
2006-03-12 04:11:30 +01:00
<body>
improve semantic markup Now the toplevel layout is: <article> <section><header><nav></section> <aside>sidebar</aside> <section>content</section> <section>comments</section> <footer> </article> And I managed to preserve all CSS ids and names in their prior structure, so CSS should not need changed.
2010-05-02 21:41:12 +02:00
<TMPL_IF HTML5><article class="page"><TMPL_ELSE><div class="page"></TMPL_IF>
<TMPL_IF HTML5><section class="pageheader"><TMPL_ELSE><div class="pageheader"></TMPL_IF>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><header class="header"><TMPL_ELSE><div class="header"></TMPL_IF>
* The page name and parent links has switched from using a <h1> to a styled <span>, so pages can use <h1> internally instead of needing to use <h2>. * Updated all of ikiwiki's own wiki pages for that. * Add pagetemplate hook, which can be used by plugins that want to mess around with adding new stuff to the page template. * Remove headercontent; the search plugin now adds the search box to the header by registering a pagetemplate hook, and other plugins should do similarly.
2006-05-26 03:10:58 +02:00
<span>
More CSS hooks for page.tmpl. I notice madduck.net already has a similar change :-)
2008-07-15 01:56:19 +02:00
<span class="parentlinks">
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_LOOP PARENTLINKS>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<a href="<TMPL_VAR URL>"><TMPL_VAR PAGE></a>/
use template for page rendering
2006-03-12 04:11:30 +01:00
</TMPL_LOOP>
More CSS hooks for page.tmpl. I notice madduck.net already has a similar change :-)
2008-07-15 01:56:19 +02:00
</span>
<span class="title">
forgot to revert this
2007-03-21 07:39:01 +01:00
<TMPL_VAR TITLE>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF ISTRANSLATION>
&nbsp;(<TMPL_VAR PERCENTTRANSLATED>%)
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
</TMPL_IF>
* The page name and parent links has switched from using a <h1> to a styled <span>, so pages can use <h1> internally instead of needing to use <h2>. * Updated all of ikiwiki's own wiki pages for that. * Add pagetemplate hook, which can be used by plugins that want to mess around with adding new stuff to the page template. * Remove headercontent; the search plugin now adds the search box to the header by registering a pagetemplate hook, and other plugins should do similarly.
2006-05-26 03:10:58 +02:00
</span>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
</span>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
<TMPL_UNLESS DYNAMIC>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF SEARCHFORM>
* The page name and parent links has switched from using a <h1> to a styled <span>, so pages can use <h1> internally instead of needing to use <h2>. * Updated all of ikiwiki's own wiki pages for that. * Add pagetemplate hook, which can be used by plugins that want to mess around with adding new stuff to the page template. * Remove headercontent; the search plugin now adds the search box to the header by registering a pagetemplate hook, and other plugins should do similarly.
2006-05-26 03:10:58 +02:00
<TMPL_VAR SEARCHFORM>
</TMPL_IF>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
</TMPL_UNLESS>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></header><TMPL_ELSE></div></TMPL_IF>
use template for page rendering
2006-03-12 04:11:30 +01:00
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF HAVE_ACTIONS>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><nav class="actions"><TMPL_ELSE><div class="actions"></TMPL_IF>
css support
2006-03-29 09:24:03 +02:00
<ul>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF EDITURL>
Add rel=nofollow to edit links. This may prevent some spiders from pounding on the cgi following edit links.
2008-05-28 09:09:04 +02:00
<li><a href="<TMPL_VAR EDITURL>" rel="nofollow">Edit</a></li>
use template for page rendering
2006-03-12 04:11:30 +01:00
</TMPL_IF>
put back recentchangesurl On second thought, misctemplate can use pagetemplate hooks to provide it, so it's better to keep back-compat, and allow full customisation of how it's displayed via the template.
2010-05-15 02:38:08 +02:00
<TMPL_IF RECENTCHANGESURL>
<li><a href="<TMPL_VAR RECENTCHANGESURL>">RecentChanges</a></li>
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF HISTORYURL>
css support
2006-03-29 09:24:03 +02:00
<li><a href="<TMPL_VAR HISTORYURL>">History</a></li>
use template for page rendering
2006-03-12 04:11:30 +01:00
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF GETSOURCEURL>
getsource: in the default template, just say "Source" All the other actions are single words (apart from RecentChanges), and are nouns (apart from Edit); saying "Source" is consistent with "History", for instance.
2009-07-26 17:49:48 +02:00
<li><a href="<TMPL_VAR GETSOURCEURL>">Source</a></li>
Add getsource plugin
2009-07-26 17:22:56 +02:00
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF PREFSURL>
css support
2006-03-29 09:24:03 +02:00
<li><a href="<TMPL_VAR PREFSURL>">Preferences</a></li>
prefs page implemented
2006-03-21 03:38:17 +01:00
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF ACTIONS>
<TMPL_LOOP ACTIONS>
Add ACTIONS variable to page.tmpl, which allows plugins to add arbitrary links to the action bar without modifying the template further. (COMMENTSLINK and DISCUSSIONLINK could be folded into this, but are kept separate for now to avoid breaking modified templates.)
2010-05-03 18:15:40 +02:00
<li><TMPL_VAR ACTION></li>
</TMPL_LOOP>
</TMPL_IF>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF COMMENTSLINK>
Add ACTIONS variable to page.tmpl, which allows plugins to add arbitrary links to the action bar without modifying the template further. (COMMENTSLINK and DISCUSSIONLINK could be folded into this, but are kept separate for now to avoid breaking modified templates.)
2010-05-03 18:15:40 +02:00
<li><TMPL_VAR COMMENTSLINK></li>
replace discussion links on pages with comments link The thinking here is that having both a Discussion page and comments for the same page is redundant, and certianly not what you want if you enable comments for a page. At first I considered making configurable via pagespec what pages got discussion links. But that would mean testing a new pagespec for every page, and a redundant config setting to keep in sync. So intead, take a lead from my previous change to make inlined pages have a comments link, and change the discussion link at the top of regular pages to link to their comments. (Implementation is a bit optimised to avoid redundant pagespec checking.)
2008-12-19 19:55:41 +01:00
<TMPL_ELSE>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF DISCUSSIONLINK>
Add ACTIONS variable to page.tmpl, which allows plugins to add arbitrary links to the action bar without modifying the template further. (COMMENTSLINK and DISCUSSIONLINK could be folded into this, but are kept separate for now to avoid breaking modified templates.)
2010-05-03 18:15:40 +02:00
<li><TMPL_VAR DISCUSSIONLINK></li>
* Allow discussion links on pages to be turned off with --no-discussion.
2006-05-05 20:20:52 +02:00
</TMPL_IF>
replace discussion links on pages with comments link The thinking here is that having both a Discussion page and comments for the same page is redundant, and certianly not what you want if you enable comments for a page. At first I considered making configurable via pagespec what pages got discussion links. But that would mean testing a new pagespec for every page, and a redundant config setting to keep in sync. So intead, take a lead from my previous change to make inlined pages have a comments link, and change the discussion link at the top of regular pages to link to their comments. (Implementation is a bit optimised to avoid redundant pagespec checking.)
2008-12-19 19:55:41 +01:00
</TMPL_IF>
css support
2006-03-29 09:24:03 +02:00
</ul>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></nav><TMPL_ELSE></div></TMPL_IF>
better fix for empty actions list issue
2006-05-26 17:18:12 +02:00
</TMPL_IF>
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF OTHERLANGUAGES>
page.tmpl: Accidentially broke po plugin's otherlanguages list styling when modifying for html5; now fixed.
2010-05-16 06:03:35 +02:00
<TMPL_IF HTML5><nav id="otherlanguages"><TMPL_ELSE><div id="otherlanguages"></TMPL_IF>
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
<ul>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_LOOP OTHERLANGUAGES>
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
<li>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<a href="<TMPL_VAR URL>"><TMPL_VAR LANGUAGE></a>
<TMPL_IF MASTER>
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
(master)
<TMPL_ELSE>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
&nbsp;(<TMPL_VAR PERCENT>%)
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
</TMPL_IF>
</li>
</TMPL_LOOP>
</ul>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></nav><TMPL_ELSE></div></TMPL_IF>
page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATED Signed-off-by: intrigeri <intrigeri@boum.org>
2009-03-28 11:41:21 +01:00
</TMPL_IF>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
<TMPL_UNLESS DYNAMIC>
trail: new plugin (3rd attempt)
2011-11-04 20:32:41 +01:00
<TMPL_VAR TRAILS>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
</TMPL_UNLESS>
trail: new plugin (3rd attempt)
2011-11-04 20:32:41 +01:00
improve semantic markup Now the toplevel layout is: <article> <section><header><nav></section> <aside>sidebar</aside> <section>content</section> <section>comments</section> <footer> </article> And I managed to preserve all CSS ids and names in their prior structure, so CSS should not need changed.
2010-05-02 21:41:12 +02:00
<TMPL_IF HTML5></section><TMPL_ELSE></div></TMPL_IF>
- Add Discussion links to the button bar, these will automatically create /Discussion subpages. - Fix linking to DNE pages in some edge cases. - Fix --rebuild (oops) - Fix propigation of "from" field trru the login process when creating a new page.a - Ideas for change notification.
2006-03-13 01:52:57 +01:00
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
<TMPL_UNLESS DYNAMIC>
* Add a tail fin^W^Wsidebar plugin by Tuomo Valkonen. * If a page links to itself, mark up the link text in a span with class="selflink" so that it can be styled. I don't have a useful style defined for that though.
2006-08-18 02:24:22 +02:00
<TMPL_IF SIDEBAR>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><aside class="sidebar"><TMPL_ELSE><div class="sidebar"></TMPL_IF>
* Add a tail fin^W^Wsidebar plugin by Tuomo Valkonen. * If a page links to itself, mark up the link text in a span with class="selflink" so that it can be styled. I don't have a useful style defined for that though.
2006-08-18 02:24:22 +02:00
<TMPL_VAR SIDEBAR>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></aside><TMPL_ELSE></div></TMPL_IF>
* Add a tail fin^W^Wsidebar plugin by Tuomo Valkonen. * If a page links to itself, mark up the link text in a span with class="selflink" so that it can be styled. I don't have a useful style defined for that though.
2006-08-18 02:24:22 +02:00
</TMPL_IF>
page.tmpl: omit searchform, trails, sidebar and most metadata in CGI These all seem somewhat inappropriate (searchform and sidebar are arguable either way). I've left actions and languages enabled, since they seem more reasonable for CGI-generated pages. Bug: http://ikiwiki.info/bugs/trail_shows_on_cgi_pages/ Signed-off-by: Simon McVittie <smcv@debian.org>
2013-03-02 19:11:07 +01:00
</TMPL_UNLESS>
* Add a tail fin^W^Wsidebar plugin by Tuomo Valkonen. * If a page links to itself, mark up the link text in a span with class="selflink" so that it can be styled. I don't have a useful style defined for that though.
2006-08-18 02:24:22 +02:00
I'm told that the pagebody div should be after the sidebar.
2010-06-10 21:15:44 +02:00
<div id="pagebody">
Always produce HTML5 doctype and new attributes, but not new elements According to caniuse.com, a significant fraction of Web users are still using Internet Explorer versions that do not support HTML5 sectioning elements. However, claiming we're XHTML 1.0 Strict means we can't use features invented in the last 12 years, even if they degrade gracefully in older browsers (like the role and placeholder attributes). This means our output is no longer valid according to any particular DTD. Real browsers and other non-validator user-agents have never cared about DTD compliance anyway, so I don't think this is a real loss.
2014-10-16 12:04:53 +02:00
<TMPL_IF HTML5><section<TMPL_ELSE><div</TMPL_IF> id="content" role="main">
use template for page rendering
2006-03-12 04:11:30 +01:00
<TMPL_VAR CONTENT>
improve semantic markup Now the toplevel layout is: <article> <section><header><nav></section> <aside>sidebar</aside> <section>content</section> <section>comments</section> <footer> </article> And I managed to preserve all CSS ids and names in their prior structure, so CSS should not need changed.
2010-05-02 21:41:12 +02:00
<TMPL_IF HTML5></section><TMPL_ELSE></div></TMPL_IF>
use template for page rendering
2006-03-12 04:11:30 +01:00
Make [[!meta enclosure=foo.mp3]] "work" for HTML.
2013-02-18 22:24:22 +01:00
<TMPL_IF ENCLOSURE>
Don't add enclosure divs unless we have enclosures.
2013-06-27 02:17:17 +02:00
<TMPL_IF HTML5><section id="enclosure"><TMPL_ELSE><div id="enclosure"></TMPL_IF>
Genericize download link for more use cases.
2013-06-27 02:21:33 +02:00
<a href="<TMPL_VAR ENCLOSURE>">Download</a>
Make [[!meta enclosure=foo.mp3]] "work" for HTML.
2013-02-18 22:24:22 +01:00
<TMPL_IF HTML5></section><TMPL_ELSE></div></TMPL_IF>
Don't add enclosure divs unless we have enclosures.
2013-06-27 02:17:17 +02:00
</TMPL_IF>
Make [[!meta enclosure=foo.mp3]] "work" for HTML.
2013-02-18 22:24:22 +01:00
Avoid showing 'Add a comment' link at the bottom of the comment post form. Since misctemplate is called with a page context, the comments plugin thinks it should add that, as well as the comment link in the actionbar. I kept the comment link because a quick link back to the comments to a page is sorta useful.
2010-07-22 21:02:04 +02:00
<TMPL_UNLESS DYNAMIC>
Add comments to page.tmpl
2008-11-22 20:01:28 +01:00
<TMPL_IF COMMENTS>
Always produce HTML5 doctype and new attributes, but not new elements According to caniuse.com, a significant fraction of Web users are still using Internet Explorer versions that do not support HTML5 sectioning elements. However, claiming we're XHTML 1.0 Strict means we can't use features invented in the last 12 years, even if they degrade gracefully in older browsers (like the role and placeholder attributes). This means our output is no longer valid according to any particular DTD. Real browsers and other non-validator user-agents have never cared about DTD compliance anyway, so I don't think this is a real loss.
2014-10-16 12:04:53 +02:00
<TMPL_IF HTML5><section<TMPL_ELSE><div</TMPL_IF> id="comments" role="complementary">
Add comments to page.tmpl
2008-11-22 20:01:28 +01:00
<TMPL_VAR COMMENTS>
comments: Rename COMMENTURL to ADDCOMMENTURL to avoid confusion with COMMENTAUTHORURL Also refactor page.tmpl to use if/else rather than unless/if.
2008-12-18 21:01:08 +01:00
<TMPL_IF ADDCOMMENTURL>
page.tmpl: optionally include "add comment" link
2008-11-23 18:07:07 +01:00
<div class="addcomment">
comments: Rename COMMENTURL to ADDCOMMENTURL to avoid confusion with COMMENTAUTHORURL Also refactor page.tmpl to use if/else rather than unless/if.
2008-12-18 21:01:08 +01:00
<a href="<TMPL_VAR ADDCOMMENTURL>">Add a comment</a>
page.tmpl: optionally include "add comment" link
2008-11-23 18:07:07 +01:00
</div>
comments: Rename COMMENTURL to ADDCOMMENTURL to avoid confusion with COMMENTAUTHORURL Also refactor page.tmpl to use if/else rather than unless/if.
2008-12-18 21:01:08 +01:00
<TMPL_ELSE>
<div class="addcomment">Comments on this page are closed.</div>
Add comments to page.tmpl
2008-11-22 20:01:28 +01:00
</TMPL_IF>
improve semantic markup Now the toplevel layout is: <article> <section><header><nav></section> <aside>sidebar</aside> <section>content</section> <section>comments</section> <footer> </article> And I managed to preserve all CSS ids and names in their prior structure, so CSS should not need changed.
2010-05-02 21:41:12 +02:00
<TMPL_IF HTML5></section><TMPL_ELSE></div></TMPL_IF>
add Comments link when displaying a page inline This link will supplant the usual Discussion link for pages that have comments enabled.
2008-12-18 01:38:02 +01:00
</TMPL_IF>
Avoid showing 'Add a comment' link at the bottom of the comment post form. Since misctemplate is called with a page context, the comments plugin thinks it should add that, as well as the comment link in the actionbar. I kept the comment link because a quick link back to the comments to a page is sorta useful.
2010-07-22 21:02:04 +02:00
</TMPL_UNLESS>
Add comments to page.tmpl
2008-11-22 20:01:28 +01:00
page.tmpl: Add a div around the sidebar, page content, and comments, to aide in styling. http://bzed.de/posts/2010/05/new_css_for_bzed.de/ smcv: [10:59:01] is the logical thing you want a <div> whose meaning is "the bits the sidebar is allowed to accompany"? bzed: [10:59:14] yeah bzed: [10:59:58] then you could just ensure that this part is as high as the sidebar smcv: [11:02:44] wrapping a <div> around the sidebar, content and comments seems like the way forward, then
2010-06-10 19:16:35 +02:00
</div>
Always produce HTML5 doctype and new attributes, but not new elements According to caniuse.com, a significant fraction of Web users are still using Internet Explorer versions that do not support HTML5 sectioning elements. However, claiming we're XHTML 1.0 Strict means we can't use features invented in the last 12 years, even if they degrade gracefully in older browsers (like the role and placeholder attributes). This means our output is no longer valid according to any particular DTD. Real browsers and other non-validator user-agents have never cared about DTD compliance anyway, so I don't think this is a real loss.
2014-10-16 12:04:53 +02:00
<TMPL_IF HTML5><footer<TMPL_ELSE><div</TMPL_IF> id="footer" class="pagefooter" role="contentinfo">
rename ispage variable
2010-05-06 04:36:50 +02:00
<TMPL_UNLESS DYNAMIC>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><nav id="pageinfo"><TMPL_ELSE><div id="pageinfo"></TMPL_IF>
* Move the footer div to enclose tags and links too. * More style sheet updates, remove the hack that used the tags div to create the footer border.
2007-04-26 21:33:28 +02:00
Have trail links at both beginning and end in the default templates
2012-04-09 17:12:07 +02:00
<TMPL_VAR TRAILS>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF TAGS>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><nav class="tags"><TMPL_ELSE><div class="tags"></TMPL_IF>
Hope encrico doesn't mind, but I changed the location and layout of the tags on the templates. This way seems to fit better with the links. Also some css cleanup, avoid hardcoded <i> etc.
2006-07-28 02:21:13 +02:00
Tags:
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_LOOP TAGS>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<TMPL_VAR LINK>
Hope encrico doesn't mind, but I changed the location and layout of the tags on the templates. This way seems to fit better with the links. Also some css cleanup, avoid hardcoded <i> etc.
2006-07-28 02:21:13 +02:00
</TMPL_LOOP>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></nav><TMPL_ELSE></div></TMPL_IF>
* Minor template improvements by Alessandro.
2007-04-19 01:35:48 +02:00
</TMPL_IF>
Hope encrico doesn't mind, but I changed the location and layout of the tags on the templates. This way seems to fit better with the links. Also some css cleanup, avoid hardcoded <i> etc.
2006-07-28 02:21:13 +02:00
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF BACKLINKS>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5><nav id="backlinks"><TMPL_ELSE><div id="backlinks"></TMPL_IF>
css support
2006-03-29 09:24:03 +02:00
Links:
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_LOOP BACKLINKS>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<a href="<TMPL_VAR URL>"><TMPL_VAR PAGE></a>
use template for page rendering
2006-03-12 04:11:30 +01:00
</TMPL_LOOP>
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_IF MORE_BACKLINKS>
* Hide excess backlinks and expand using CSS trick; control quantiy via the numbacklinks setting.
2007-03-31 10:48:10 +02:00
<span class="popup">...
use popup balloon for more backlinks, rather than expanding on hover, since in some cases it's not possible to move the mouse over the more backlinks using the old method
2007-04-07 00:30:51 +02:00
<span class="balloon">
consistently drop NAME= in templates also add template syntax smoke test
2010-05-06 03:08:41 +02:00
<TMPL_LOOP MORE_BACKLINKS>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<a href="<TMPL_VAR URL>"><TMPL_VAR PAGE></a>
* Hide excess backlinks and expand using CSS trick; control quantiy via the numbacklinks setting.
2007-03-31 10:48:10 +02:00
</TMPL_LOOP>
</span>
</span>
</TMPL_IF>
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></nav><TMPL_ELSE></div></TMPL_IF>
* Minor template improvements by Alessandro.
2007-04-19 01:35:48 +02:00
</TMPL_IF>
use template for page rendering
2006-03-12 04:11:30 +01:00
* meta: Support license and copyright information. The information will be shown in the page footer. HTML will also be inserted that should support the rel=license microformat as well as the HTML spec's rel=copyright.
2007-09-14 20:11:10 +02:00
<TMPL_IF COPYRIGHT>
* Fix copyright and licence styling.
2007-09-20 20:06:55 +02:00
<div class="pagecopyright">
basic styling for license and copyright
2007-09-15 02:38:30 +02:00
<a name="pagecopyright"></a>
* meta: Support license and copyright information. The information will be shown in the page footer. HTML will also be inserted that should support the rel=license microformat as well as the HTML spec's rel=copyright.
2007-09-14 20:11:10 +02:00
<TMPL_VAR COPYRIGHT>
</div>
</TMPL_IF>
<TMPL_IF LICENSE>
* Fix copyright and licence styling.
2007-09-20 20:06:55 +02:00
<div class="pagelicense">
basic styling for license and copyright
2007-09-15 02:38:30 +02:00
<a name="pagelicense"></a>
* meta: Support license and copyright information. The information will be shown in the page footer. HTML will also be inserted that should support the rel=license microformat as well as the HTML spec's rel=copyright.
2007-09-14 20:11:10 +02:00
License: <TMPL_VAR LICENSE>
</div>
</TMPL_IF>
* Make all templates have a footer div to ease themeing. Required template and style sheet updates, and unless you're using customised versions, you'll want to rebuild wikis on upgrade to this version to avoid inconsistencies. * Allow WIKINAME to to used in footers, as an example of something to put there.
2007-05-11 22:09:58 +02:00
<div class="pagedate">
fix relativedate timezone inclusion The machine parseable date needs to include a timezone. Also, simplified the interface for date display.
2008-10-20 01:13:40 +02:00
Last edited <TMPL_VAR MTIME>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<!-- Created <TMPL_VAR CTIME> -->
Changes from StefanoZacchiroli: - Use div for inlinepage actions, not a span - Add an enclosing "trailer" div Also, change pageinfo span into a div, since it now can include <p>
2006-12-28 21:32:51 +01:00
</div>
* Move the footer div to enclose tags and links too. * More style sheet updates, remove the hack that used the tags div to create the footer border.
2007-04-26 21:33:28 +02:00
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></nav><TMPL_ELSE></div></TMPL_IF>
more footer improvements
2007-04-26 21:49:06 +02:00
<TMPL_IF EXTRAFOOTER><TMPL_VAR EXTRAFOOTER></TMPL_IF>
bugfix
2010-05-06 04:44:08 +02:00
</TMPL_UNLESS>
relativedate: New javascript-alicious plugin that makes all dates display relative, in a very nice way, if I say so myself.
2008-10-18 02:47:32 +02:00
<!-- from <TMPL_VAR WIKINAME> -->
use html5 semantic markup in page.tmpl This is a first pass, it avoids needing to change style.css except where it refers to tag types. This goes a bit off the rails at the pageheader with its nested header. Semantically, there should be an article around the whole page header, content, and footer. Just as there will be an article around a whole comment or inlined page header, content, and footer. But that will mean changing the css that currently refers to pageheader to refer to the enclosing article instead.
2010-05-02 21:09:33 +02:00
<TMPL_IF HTML5></footer><TMPL_ELSE></div></TMPL_IF>
- use templates for signin form, error messages - use FormBuilder for edit page forms (also use template) - print debug to stderr in cgi mode to avoid breaking http headers - fix links to page in parentlinks if $url is unset - reorganise how wikilink is used in templates - only make recentchanes link if svn is enabled - change session id cookie to something we control - add support for logging committer name for web commits from signed in users (untested) - probably more changes I forgot
2006-03-12 17:37:26 +01:00
improve semantic markup Now the toplevel layout is: <article> <section><header><nav></section> <aside>sidebar</aside> <section>content</section> <section>comments</section> <footer> </article> And I managed to preserve all CSS ids and names in their prior structure, so CSS should not need changed.
2010-05-02 21:41:12 +02:00
<TMPL_IF HTML5></article><TMPL_ELSE></div></TMPL_IF>
use template for page rendering
2006-03-12 04:11:30 +01:00
</body>
</html>