aboutsummaryrefslogtreecommitdiff
path: root/templates/page.tmpl
Commit message (Collapse)AuthorAge
* Have trail links at both beginning and end in the default templatesSimon McVittie2012-04-09
|
* trail: new plugin (3rd attempt)Simon McVittie2011-11-09
|
* Avoid showing 'Add a comment' link at the bottom of the comment post form.Joey Hess2010-07-22
| | | | | | | 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.
* Drop Cache-Control must-revalidate (Firefox 3.5.10 does not seem to have the ↵Joey Hess2010-07-14
| | | | caching problem that was added to work around). Closes: #588623
* I'm told that the pagebody div should be after the sidebar.Joey Hess2010-06-10
|
* page.tmpl: Add a div around the sidebar, page content, and comments, to aide ↵Joey Hess2010-06-10
| | | | | | | | | | | 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
* page.tmpl: Accidentially broke po plugin's otherlanguages list styling when ↵Joey Hess2010-05-16
| | | | modifying for html5; now fixed.
* allow misctemplate callers to pass params to suppress actions etcJoey Hess2010-05-14
| | | | | Suppress disiplay of small search for on search results page, and of Prefrences link on prefs page.
* avoid showing redundant search box on search results pageJoey Hess2010-05-14
|
* show search form on dynamic pagesJoey Hess2010-05-14
|
* put back recentchangesurlJoey Hess2010-05-14
| | | | | | 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.
* enable action bar on misctemplatesJoey Hess2010-05-14
| | | | | | So RecentChanges shows on the action bar there, convert recentchanges to use new pageactions hook, with compatability code to avoid breaking old templates.
* bugfixJoey Hess2010-05-05
|
* rename ispage variableJoey Hess2010-05-05
|
* add NEWS about template changeJoey Hess2010-05-05
|
* consistently drop NAME= in templatesJoey Hess2010-05-05
| | | | also add template syntax smoke test
* allow search form visibility to be controlled on the templateJoey Hess2010-05-05
| | | | hide extrafooter from misctemplate display per default
* on second thought, remove FOOTER variableJoey Hess2010-05-05
| | | | We always want a footer, just not a pagefooter when doing misctemplate.
* add the <base> setting as in misc.tmpl; only ever do it if not ispageJoey Hess2010-05-05
| | | | Also, add FOOTER, to allow disabling the footer.
* Add ACTIONS variable to page.tmpl, which allows plugins to add arbitrary ↵Joey Hess2010-05-03
| | | | | | | 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.)
* improve semantic markupJoey Hess2010-05-02
| | | | | | | | | | | | | | | 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.
* use html5 semantic markup in page.tmplJoey Hess2010-05-02
| | | | | | | | | | | | | 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.
* html5 optionJoey Hess2010-05-01
| | | | | | * Ikiwiki can be configured to generate html5 instead of the default xhtml 1.0. The html5 output mode is experimental, not yet fully standards compliant, and will be subject to rapid change.
* CSS and templates for sidebar changed to use a class, not an id.Joey Hess2010-04-15
| | | | | Multiple sidebars should be possible; also, I want to add a sidebar template.
* page.tmpl: Add Cache-Control must-revalidate to ensure that users ↵Joey Hess2010-03-31
| | | | | | | | | | | | | (especially of Firefox) see fresh page content. Since Firefox version 3, it's done aggressive caching of visited pages, and does not, by default, check if the cached content is still valid when reloading or revisiting a page. By default, Firefox seems to not re-contact the web server at all. Compare with eg, Epiphany and Chromium, which appear to always check, and get back a 304 when the page is unchanged. This header makes Firefox do the right thing, at least for html files. It still over-caches if css, javascript, images, etc, are changed.
* typoJoey Hess2009-11-09
|
* localstyle: New plugin, allows overrding the toplevel local.css with one ↵Joey Hess2009-11-09
| | | | | | | | | | | | | | | | | | | | 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.
* further otherlanguages list stylingJoey Hess2009-08-15
|
* getsource: in the default template, just say "Source"Simon McVittie2009-07-26
| | | | | | All the other actions are single words (apart from RecentChanges), and are nouns (apart from Edit); saying "Source" is consistent with "History", for instance.
* Add getsource pluginWill Uther2009-07-26
|
* page.tmpl: use OTHERLANGUAGES and PERCENTTRANSLATEDintrigeri2009-03-28
| | | | Signed-off-by: intrigeri <intrigeri@boum.org>
* repolist: New plugin to support the rel=vcs-* microformat.Joey Hess2009-01-07
| | | | | | * repolist: New plugin to support the rel=vcs-* microformat. * goodstuff: Include repolist by default. (But it does nothing until configured with the repository locations.)
* comments: Rename COMMENTURL to ADDCOMMENTURL to avoid confusion with ↵Simon McVittie2008-12-20
| | | | | | COMMENTAUTHORURL Also refactor page.tmpl to use if/else rather than unless/if.
* replace discussion links on pages with comments linkJoey Hess2008-12-19
| | | | | | | | | | | | | 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.)
* add Comments link when displaying a page inlineJoey Hess2008-12-17
| | | | | This link will supplant the usual Discussion link for pages that have comments enabled.
* page.tmpl: optionally include "add comment" linkSimon McVittie2008-12-11
|
* Add comments to page.tmplSimon McVittie2008-12-11
|
* fix relativedate timezone inclusionJoey Hess2008-10-19
| | | | | | The machine parseable date needs to include a timezone. Also, simplified the interface for date display.
* relativedate: New javascript-alicious plugin that makes all dates display ↵Joey Hess2008-10-17
| | | | relative, in a very nice way, if I say so myself.
* Oops, add missing </span>Simon McVittie2008-07-15
|
* More CSS hooks for page.tmpl.Simon McVittie2008-07-15
| | | | I notice madduck.net already has a similar change :-)
* Add more stylesheet hooks to the page templateSimon McVittie2008-07-13
| | | | | | | * Wrap header stuff, including actions, in <div class="pageheader"> (there is already a class="header", which is a subset of this, so using id="header" would be confusing) * Add class="pagefooter" to the existing <div id="footer">, for symmetry
* Add support for the universal edit buttonJoey Hess2008-06-21
| | | | | | <http://universaleditbutton.org/> Not forcing a rebuild on upgrade just for this.
* Add rel=nofollow to edit links. This may prevent some spiders from pounding ↵Joey Hess2008-05-28
| | | | on the cgi following edit links.
* * Page templates can now use CTIME to show when the page was created.Joey Hess2008-02-09
|
* Add xmlns attribute on html element in templates; pages can now validate.Josh Triplett2007-11-08
|
* * Fix copyright and licence styling.joey2007-09-20
|
* basic styling for license and copyrightjoey2007-09-15
|
* * meta: Support license and copyright information. The information willjoey2007-09-14
| | | | | | 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.
* * Make all templates have a footer div to ease themeing. Required templatejoey2007-05-11
| | | | | | | | 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.