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 * A doctype should be added: do we want XHTML 1.0 or HTML 4.01 Trans as
12 Need to choose a doctype that corresponds to what [[MarkDown]]
13 generates. For example, it does generate <hr />
14 So xhtml seems a good fit and I'm going to add that to the
17 One consideration of course is that regular users might embed html
18 that uses deprecated presentational elements like <center>. At
19 least firefox seems to handle that mixture ok.
22 * If XHTML: In templates <hr> should become <hr /> etc.
26 * Image wikilinks should provide an alt text (maybe '$filname wiki-image'?).
28 Now it will be the text of the [[WikiLink]], which even allows
29 setting a custom alt text like this: \[[my_alt_text|image.png]]
32 * &'s in (cgi-)url's must be escaped as &amp;.
36 * [ [inlinepage] ] gets wrapped in <p>...</p> which has a high chance of invalidating the page.
38 Since markdown does this, the only way I can think to fix it is to
39 make the inlined page text start with </p> and end with
40 <p>. Ugly, and of course there could be problems with
41 markdown enclosing it in other spanning tags in some cases.
42 I've implemented this hack now. :-/ --[[Joey]]
44 I used this 'hack' myself, but yesterday I came up with a better idea:
45 <div class="inlinepage">
48 This prevents markdown enclosing and even adds a useful css identifier. --[[JeroenSchot]]
50 This page is now valid.
51 Test: [validate this page](http://validator.w3.org/check?url=referer)