summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-08 22:54:17 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-08 22:54:17 +0000
commit8b6575894290d35e94521ef9ef656cc3f71152ca (patch)
treee8032acada2f387f6583babfb5c2b8e2286919ab /doc/todo
parent7dcdea3410a98ea5f8969879292162020a2cd2e9 (diff)
web commit by ManojSrivastava
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/Calendar_plugin.mdwn9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/todo/Calendar_plugin.mdwn b/doc/todo/Calendar_plugin.mdwn
new file mode 100644
index 000000000..fd12bdefa
--- /dev/null
+++ b/doc/todo/Calendar_plugin.mdwn
@@ -0,0 +1,9 @@
+I am serving notice that I am starting work on a calendar plugin inspired by Blosxom's calendar plugin. The current plan is to create a plugin that looks through all the source files matching a certain pagespec, and optionally spit out a month view for the specified month (default to current), or spit out a year view for a given year (defaulting to the current year), of a list of year with posts in them. The output would be a table, with the same CSS directives that the Blosxom plugin used to use (so that I can just reuse my css file). The links would be created to a $config{archivedir}/$year or $config{archivedir}/$year-$month file, which can just have
+
+ \[[inline pages="blog/* and !*/Discussion and creation_year($year) and creation_month($month)" rss="no" atom="no" show="0"]]
+
+or some thing to generate a archive of postings.
+
+Roland Mas suggested a separate cron job to generate these archive indices automatically, but that is another thread.
+
+ManojSrivastava \ No newline at end of file