aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-08-26 21:41:49 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-08-26 21:41:49 +0000
commit02a2de8ead6d7afd828643397e2f68f0c63acb70 (patch)
tree63b4b9a67b0a2ccf1d5b31b7486b8d37dca187ac /doc
parent7022bf3cb143ecb7ce18fc6a7ae417c84df9e3c5 (diff)
downloadikiwiki-02a2de8ead6d7afd828643397e2f68f0c63acb70.tar
ikiwiki-02a2de8ead6d7afd828643397e2f68f0c63acb70.tar.gz
response
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/blogging.mdwn16
1 files changed, 15 insertions, 1 deletions
diff --git a/doc/todo/blogging.mdwn b/doc/todo/blogging.mdwn
index 095eb9eaf..fe35a567e 100644
--- a/doc/todo/blogging.mdwn
+++ b/doc/todo/blogging.mdwn
@@ -10,4 +10,18 @@ when make is used without PREFIX.
http://jameswestby.net/scratch/podcast.diff
--- JamesWestby \ No newline at end of file
+-- JamesWestby
+
+ Hmm. Not quite how I'd envisioned podcasts would work, my idea was
+ more that the sound files would be kept inside the wiki, and the
+ inline plugin could be told to eg, inline *.mp3, and would add
+ those to the rss feed as enclosures. Maybe you'd also inline some
+ regular blog pages to describe the files or the like.
+
+ Do you think that would work or that it's worth pursuing that
+ approach? I haven't looked at podcasts enough to know if that
+ method would be technically feasable; for one thing it would limit
+ the blog items for podcasts to just having an enclosure but no
+ description.
+
+ --[[Joey]]