Author: Ted Roche
Posted: 2010-06-05 at 15:03:40
On Sat, Jun 5, 2010 at 11:50 AM, Carl Karsten <carl@personnelware.com> wrote:
>
> I would like to throw in a question for discussion: What is the
> minimum set of features for something to be a wiki?
>
Great question!
Well, if the minimal definition of wiki is "quick" then any easily
editable web page might be considered a wiki.
cite: http://wiki.org/wiki.cgi?WhatIsWiki
> I added this to my Django flatpage* based site:
>
> {% if user.is_staff %}
> <a href="/admin/flatpages/flatpage/{{flatpage.id}}/">edit</a>
>
There you go! Role-Based Access Control!
> But there are no automatic links from camel case, to create a new page
> you have to hit the "new page" link in the Django admin, etc. So is
> it a wiki? Whatever it is, it made my client very happy.
It might be. I created my first blog by editing Wiki pages and naming
them with an appropriate chronological scheme, linking them to a
calendar-view page. Because I used Twiki, was it a wiki or a blog?
Few of these terms are well-defined at all. I bristle when I hear the
evening news anchors say, "Visit our blog at (A|B|C)BC.com for more"
-- that's not a blog, it's a CMS-driven website!
> [1] http://docs.djangoproject.com/en/dev/ref/contrib/flatpages/
Interesting process. I'm not happy that the default routing logic is
to try all applications, throw a 404, and finally search for a
flatpage as a last resort/rescue. Seems like flat-page retrieval and
rendering could be higher up in the event process to avoid the error
handler. But I'll bet there's an architechtural reason that that's the
best flow.
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
Post Messages to: ProLinux@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/prolinux
Searchable Archive: http://leafe.com/archives/search/prolinux
This message: http://leafe.com/archives/byMID/AANLkTimd0gqlJeCrja5FgPPQWLvTk53DYrNUGJxJY367@mail.gmail.com