Nick Reinking wrote:
Before I go on to make a page caching proposal, I was wondering - what parts of articles are currently dynamic and, as such, can't be used for logged in users who have special preferences? (Things such as whether to make a link red, or add a question mark).
In page text:
* show hoverbox over wiki links ???
* underline links this can be handled as an inserted CSS item
* red vs ? links these could be handled as CSS as in phase II, or could be postprocessed for people with the rarer option
* justify paragraphs this can be handled as an inserted CSS item
* auto-number headings could always add them in, with default style hidden, and insert CSS for those with the option enabled
* enable section editing via [edit] links could hide them by CSS
* enable section editing by right clicking on section titles hypothetically, the javascript handler could be inserted by javascript code, we'd only have to insert a single script section which calls it
* show table of contents could hide by inserting CSS
* edit pages on double-click a simple insertion of javascript code after retrieving the cached copy would do
* timezone offset may affect display of pages with {{CURRENTTIME}} etc, but that's another caching issue...
In the surrounding interface: * user, user talk links vary per user * 'watch this page' / 'stop watching' links vary per user * various options are present for only certain groups of users * skin option of course changes lots of stuff! * quickbar
-- brion