[ProLinux] what is a wiki and other semantics

On Sat, Jun 5, 2010 at 2:03 PM, Ted Roche <tedroche@gmail.com> wrote:

> 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.

well, too many things are quick, so that's too broad. like posting a

comment on a blog. unless the blog is a wiki :)

>> 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?

If what you created is really a blog (which I have often wondered what

is/isn't) then it is both, and that's just fine: in both of our cases,

the wiki is the technology we used to implement something. In my case

a mostly static advertisement, in your case a dynamic "what is on my

mind" thing.

> 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!

> 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. .

Yeah, and if you forget to include a 404.html page, the 404 processing

breaks and you get a 500 server error before the flatpage code kicks

in, and you have no idea what is going on.

> But I'll bet there's an architechtural reason that that's the

> best flow

My guess is good enough is good enough.

Carl K

_______________________________________________

Post Messages to: ProLinux@leafe.com