1 Create some nice stylesheets. Make RecentChanges use table for
2 formatting, and images to indicate web vs svn commits and to link to diffs.
4 All of this should be doable w/o touching a single line of code, just
5 editing the [[templates]] and/or editing [[style.css]] BTW.
9 * Doctype is XHTML 1.0 Strict
11 One consideration of course is that regular users might embed html
12 that uses deprecated presentational elements like <center>. At
13 least firefox seems to handle that mixture ok.
16 * [ [inlinepage] ] gets wrapped in <p>...</p> which has a high chance of invalidating the page.
18 Since markdown does this, the only way I can think to fix it is to
19 make the inlined page text start with </p> and end with
20 <p>. Ugly, and of course there could be problems with
21 markdown enclosing it in other spanning tags in some cases.
22 I've implemented this hack now. :-/ --[[Joey]]
24 I used this 'hack' myself, but yesterday I came up with a better idea:
25 <div class="inlinepage">
28 This prevents markdown enclosing and even adds a useful css identifier. Problem is that this should be added to every page and not in the template(s). --[[JeroenSchot]]
30 I can make ikiwiki add that around every inlined page easily
31 enough. However, where is it docuemented? Came up dry on google.
34 This page is now valid.
35 Test: [validate this page](http://validator.w3.org/check?url=referer)