| Age | Commit message (Collapse) | Author |
|---|
|
Fixes http://code.google.com/p/openid-selector/issues/detail?id=11#c3
|
|
I think originally, the page preview header was not displayed,
so diff was hacked in using it.
|
|
In particular, added <label> tags.
(However, could not find a good way to add a label tag for the main
page edit textarea.)
|
|
|
|
|
|
|
|
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.)
|
|
|
|
|
|
Needed to force tags to display inline, since <nav> is a block element.
|
|
Note that I put comment-header in a <header> despite it being
below the comment. Using a <footer> would be confusing given
the class name. Also, the content is semantically closer to
a header than a footer.
|
|
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.
|
|
|
|
More could be done to modernize this html, but I don't want to diverge
too far from the one in xapian.
|
|
* 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.
|
|
and other minor html improvement
|
|
|
|
With archive=yes, feeds default to including all, but that is expensive
for automatically created tag pages.
|
|
Whenever the DIV tag structure of page.tmpl has been changed, the DIV
tag structure of misc.tmpl must also change to reflect this, or else
any page which uses misc.tmpl will not look right. My intent is to
make ease parallel maintenance of these two files by eliminating
trivial/accidental difference between the two, so that duplicated
regions can be more readily identified (perhaps even mechanically).
(cherry-picked from commit 075980f94996e8f67d9632ae95b8bf41fdf09afa, but
without the changes to comments in page.tmpl)
|
|
|
|
|
|
Conflicts:
IkiWiki.pm
IkiWiki/Plugin/tag.pm
|
|
|
|
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.
|
|
This only affects people who don't use either htmltidy or htmlbalance.
Bug: http://ikiwiki.info/bugs/templateForRecentChangesMissingCloseSpan/
|
|
|
|
|
|
if "tag_autocreate=1" is set in the configuration. The pages will be created in
tagbase, if and only if they do not exist in the srcdir yet. Tag pages will be create from
"autotag.tmpl".
At this stage a second refresh is needed for the tag pages to be rendered.
Add autotag.tmpl template.
|
|
|
|
Add title span to misc.tmpl so that the title is styled consistently
with pages that use page.tmpl.
|
|
|
|
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.
|
|
search works correctly for wikis that are located in subdirectories of domains.
|
|
calendar plugin.
|
|
|
|
All the other actions are single words (apart from RecentChanges), and
are nouns (apart from Edit); saying "Source" is consistent with "History",
for instance.
|
|
|
|
Conflicts:
debian/changelog
debian/control
Signed-off-by: intrigeri <intrigeri@boum.org>
|
|
and document the comment directive syntax.
Rationalle: Comments need to be user-editable so that they can be posted
via git commit etc.
The _comment directive is still supported, for back-compat.
|
|
Conflicts:
debian/changelog
|
|
wish to, if the configuration makes signin optional for commenting.
|
|
Conflicts:
debian/changelog
debian/control
|
|
|
|
This won't change it normally, and is useful if using archive
format to display some aggregated feed titles.
|
