aboutsummaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-28 20:49:30 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-28 20:49:30 +0000
commit08e9c427a9be88b43866cff1aa1c1ed6381a93f5 (patch)
tree14fa2e849150276842830788cd30a7f9108f654f /doc/todo
parentc9e07b583bb730a7697cbbeb8b1b7d912d8a1780 (diff)
downloadikiwiki-08e9c427a9be88b43866cff1aa1c1ed6381a93f5.tar
ikiwiki-08e9c427a9be88b43866cff1aa1c1ed6381a93f5.tar.gz
removed some cruft from index/discussion, and moved some parger bits out
into individual todo items
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/ACL.mdwn22
-rw-r--r--doc/todo/canonical_feed_location.mdwn14
-rw-r--r--doc/todo/recentchanges.mdwn15
3 files changed, 44 insertions, 7 deletions
diff --git a/doc/todo/ACL.mdwn b/doc/todo/ACL.mdwn
new file mode 100644
index 000000000..dea933d53
--- /dev/null
+++ b/doc/todo/ACL.mdwn
@@ -0,0 +1,22 @@
+How about adding ACL? So that you can control which users are allowed
+to read, write certain pages. The moinmoin wiki has that, and it is
+something, that I think is very valuable.
+
+> ikiwiki currently has only the most rudimentary access controls: pages
+> can be locked, or unlocked and only the admin can edit locked pages. That
+> could certianly be expanded on, although it's not an area that I have an
+> overwhelming desire to work on myself right now. Patches appreciated and
+> I'll be happy to point you in the right directions.. --[[Joey]]
+
+>> I'm really curious how you'd suggest implementing ACLs on reading a page.
+>> It seems to me the only way you could do it is .htaccess DenyAll or something,
+>> and then route all page views through ikiwiki.cgi. Am I missing something?
+>> --[[Ethan]]
+
+>>> Or you could just use apache or whatever and set up the access controls
+>>> there. Of course, that wouldn't integrate very well with the wiki,
+>>> unless perhaps you decided to use http basic authentication and the
+>>> httpauth plugin for ikiwiki that integrates with that.. --[[Joey]]
+
+>>>> Which would rule out openid, or other fun forms of auth. And routing all access
+>>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]
diff --git a/doc/todo/canonical_feed_location.mdwn b/doc/todo/canonical_feed_location.mdwn
new file mode 100644
index 000000000..32135f237
--- /dev/null
+++ b/doc/todo/canonical_feed_location.mdwn
@@ -0,0 +1,14 @@
+Any way to use `inline` but point the feed links to a different feed on the
+same site? I have news in news/*, a news archive in news.mdwn, and the
+first few news items on index.mdwn, but I don't really want two separate
+feeds, one with all news and one with the latest few articles; I'd rather
+point the RSS feed links of both to the same feed. (Which one, the one
+with all news or the one with the latest news only, I don't know yet.)
+
+> Not currently. It could be implemented, or you could just turn off the
+> rss feed for the index page, and manually put in a wikilink to the news
+> page and rss feed. --[[Joey]]
+
+>> That wouldn't use the same style for the RSS and Atom links, and it
+>> wouldn't embed the feed link into `<head>` so that browsers can automatically
+>> find it.
diff --git a/doc/todo/recentchanges.mdwn b/doc/todo/recentchanges.mdwn
index 7337c3d49..6817d3298 100644
--- a/doc/todo/recentchanges.mdwn
+++ b/doc/todo/recentchanges.mdwn
@@ -2,18 +2,19 @@
seems like it could be beneficial to have it rendered in the post-commit
hook, just like everything else in the wiki.
- I hope to statically generate it eventually, currently the problem is
- that it takes at least several seconds to generate the recentchanges
- page, and adding several seconds to every page edit is not desiriable. If
- the time can be reduced it could be done, I'm also not adverse to
- adding an optional way to statically render it even at the current speed.
+ > I hope to statically generate it eventually, currently the problem is
+ > that it takes at least several seconds to generate the recentchanges
+ > page, and adding several seconds to every page edit is not desiriable. If
+ > the time can be reduced it could be done, I'm also not adverse to
+ > adding an optional way to statically render it even at the current
+ > speed. --[[Joey]]
* 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.
- This is used by various interwiki type things, I think, so should be
- done..
+ > This is used by various interwiki type things, I think, so should be
+ > done.. --[[Joey]]
* 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