1 Seems like there should be a page for you to post your thoughts about
2 ikiwiki, both pro and con, anything that didn't work, ideas, or whatever.
5 Note that for more formal bug reports or todo items, you can also edit the
6 [[bugs]] and [[todo]] pages.
12 How about adding ACL? So that you can control which users are allowed
13 to read, write certain pages. The moinmoin wiki has that, and it is
14 something, that I think is very valuable.
16 > ikiwiki currently has only the most rudimentary access controls: pages
17 > can be locked, or unlocked and only the admin can edit locked pages. That
18 > could certianly be expanded on, although it's not an area that I have an
19 > overwhelming desire to work on myself right now. Patches appreciated and
20 > I'll be happy to point you in the right directions.. --[[Joey]]
24 Some questions about the RecentChanges function.
26 * Why isn't it statically-genereated, but generated dynamically by CGI? It seems like it could be beneficial to have it rendered in the post-commit hook, just like everything else in the wiki.
27 * Also, is it planned/desired that recent changes generate the same information in RSS feed format? This seems like it could be a useful way to keep track of the wiki as a whole.
28 * Lastly, would it be possible to use the recent changes code with a pagespec? I understand this sort of infringes on territory covered by the inline plugin, but the inline plugin only puts a page in the RSS feed once, when it's created, and I imagine some people -- some deranged, obsessive-compulsive people like myself -- would like to know about the changes made to existing pages as well as newly-created pages.
30 Thanks for your time. -- Ethan
34 Also, I'd like to request another template parameter which is just $config{url}. That way you won't have to hard-code the URL of the wiki into the template. -- Ethan