X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/680e06e52bebb3782ad234bce424cdea0cc6fb9d..df112ed89e2e8fc5c4c449758968ccd21a10ad30:/doc/todo/tagging_with_a_publication_date.mdwn

diff --git a/doc/todo/tagging_with_a_publication_date.mdwn b/doc/todo/tagging_with_a_publication_date.mdwn
index 044ba2e8a..80240ec5a 100644
--- a/doc/todo/tagging_with_a_publication_date.mdwn
+++ b/doc/todo/tagging_with_a_publication_date.mdwn
@@ -1,7 +1,7 @@
 Feature idea: I'd like to be able to tag pages in an ikiwiki blog with a
 publication date, and have the option of building a blog that excludes
 publication dates in the future.  (meta pubdate= ?)
- 
+
 I'm using ikiwiki on git for a "tip of the day" RSS feed, and I'd like to
 be able to queue up a bunch of items instead of literally putting in one
 tip per day.  In the future I think this will come in handy for other
@@ -12,6 +12,29 @@ on vacation".
 > is a wiki compiler, if something causes content to change based on the
 > date, then the wiki needs to be rebuilt periodically. So you'd need a
 > cron job or something.
-> 
-> Implemeting this feature probably needs 
-> [[todo/plugin_dependency_calulation]] to be implemented. --[[Joey]]
+>
+> Thinking about this some more, if you're going to have a cron job, you
+> could just set up a branch containing the future post. The branch could
+> have a name like 20080911. Then have the cron job git merge the day's
+> branch, if any, into master each day. And voila, post is completly hidden
+> until published. You'd want to avoid merge conflicts in your cron job ..
+> but they'd be unlikely if you limited yourself to just adding new
+> pages. Alternatively, for larger organisations wishing to deploy more
+> sweeping changes on a given date, replace cron job with intern.. ;-)
+> --[[Joey]]
+
+> > Good approach if you have one day on which a big change goes through, but
+> > often the reason for tagging with a publication date is so that you can
+> > dribble out articles one per day when you're gone for a week.  Branches are easy
+> > in git, but it would still be an extra step to switch branches every time
+> > you edit a different day's article.
+> >
+> > And just to make it a little harder, some sites might want an internal 
+> > copy of the wiki that _does_ build the future pages, just tags them with the publication
+> > date, for previewing.
+> > 
+> > One more reason to have publication date: if you move a page from your old CMS to ikiwiki
+> > and want to have it show up in the right order in RSS feeds.
+> >
+> > I no longer have the original wiki for which I wanted this feature, but I can
+> > see using it on future ones. -- [[DonMarti]]