| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
| |
caching problem that was added to work around). Closes: #588623
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
modifying for html5; now fixed.
|
| |
|
|
|
| |
Suppress disiplay of small search for on search results page, and of
Prefrences link on prefs page.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
So RecentChanges shows on the action bar there,
convert recentchanges to use new pageactions hook,
with compatability code to avoid breaking old templates.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
also add template syntax smoke test
|
| |
|
|
| |
hide extrafooter from misctemplate display per default
|
| |
|
|
| |
We always want a footer, just not a pagefooter when doing misctemplate.
|
| |
|
|
| |
Also, add FOOTER, to allow disabling the footer.
|
| |
|
|
|
|
|
| |
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.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
* 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.
|
| |
|
|
|
| |
Multiple sidebars should be possible; also, I want to add a sidebar
template.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
All the other actions are single words (apart from RecentChanges), and
are nouns (apart from Edit); saying "Source" is consistent with "History",
for instance.
|
| | |
|
| |
|
|
| |
Signed-off-by: intrigeri <intrigeri@boum.org>
|
| |
|
|
|
|
| |
* repolist: New plugin to support the rel=vcs-* microformat.
* goodstuff: Include repolist by default. (But it does nothing until
configured with the repository locations.)
|
| |
|
|
|
|
| |
COMMENTAUTHORURL
Also refactor page.tmpl to use if/else rather than unless/if.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.)
|
| |
|
|
|
| |
This link will supplant the usual Discussion link for pages
that have comments enabled.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The machine parseable date needs to include a timezone.
Also, simplified the interface for date display.
|
| |
|
|
| |
relative, in a very nice way, if I say so myself.
|
| | |
|
| |
|
|
| |
I notice madduck.net already has a similar change :-)
|
| |
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
| |
<http://universaleditbutton.org/>
Not forcing a rebuild on upgrade just for this.
|
| |
|
|
| |
on the cgi following edit links.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|