Author: Ted Roche
Posted: 2010-06-05 11:28:50 Link
The monthly meeting of the Central New Hampshire Linux Group,
http://www.centralug.org, takes place as usual on the first Monday of
the month. We're meeting at our summer location, the Hopkinton Public
Library (http://www.hopkintontownlibrary.org), which never fails to
baffle Ben by being located in Contoocook. We typically start at 7 PM,
and close up around 9 PM. Early arrival (6:30ish) is encouraged for
Q&A. There are many fine dining establishments in beautiful downtown
Contoocook (Dmitri's - pizza, Riverside - sit-down American, Louie's
Pizza, and Red Star Restaurant - Asian) should you choose to dine before
the meeting, and one of the finest examples of an all-wood covered
railroad bridge survives in downtown.
The topic of the month is Wikis. "Wiki Wiki!" is Hawaiian for "quick,
quick!" and is a pattern of presenting a read-write web site. There are
more variations and implementations than grains of sand in the universe.
but we'll look at a couple of them, specifically:
Twiki, written in Perl, running gnhlug.org (http://twiki.org)
MediaWiki, written in PHP, storage in MySQL, which runs Wikipedia.org
Dokuwiki, also in PHP (http://www.dokuwiki.org/)
Redmine, written in Ruby, which includes a wiki module.
We'll talk a little bit about the range of markup languages, the
technology behind the wiki, the social and community aspects of how a
wiki works (or doesn't), and how Free/Open Source has played into the
success of wikis.
Recommended Reading: "The Wiki Way, Quick Collaboration on the Web" by
Ward Cunningham (inventor of the wiki) and Bo Leuf, Addison-Wesley,
2001, ISBN 0-201-71499-X and http://wiki.org/. We'll have a copy there
for your browsing.
Hope to see you there!
--
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/AANLkTikY1-yf9ELMGf5bS1wvJ7VR79nni4tNXR8EIdZ6@mail.gmail.com
Author: Carl Karsten
Posted: 2010-06-05 11:50:56 Link
On Sat, Jun 5, 2010 at 10:28 AM, Ted Roche <tedroche@gmail.com> wrote:
> The monthly meeting of the Central New Hampshire Linux Group,
> http://www.centralug.org, takes place as usual on the first Monday of
> the month. We're meeting at our summer location, the Hopkinton Public
> Library (http://www.hopkintontownlibrary.org), which never fails to
> baffle Ben by being located in Contoocook. We typically start at 7 PM,
> and close up around 9 PM. Early arrival (6:30ish) is encouraged for
> Q&A. There are many fine dining establishments in beautiful downtown
> Contoocook (Dmitri's - pizza, Riverside - sit-down American, Louie's
> Pizza, and Red Star Restaurant - Asian) should you choose to dine before
> the meeting, and one of the finest examples of an all-wood covered
> railroad bridge survives in downtown.
>
> The topic of the month is Wikis. "Wiki Wiki!" is Hawaiian for "quick,
> quick!" and is a pattern of presenting a read-write web site. There are
> more variations and implementations than grains of sand in the universe.
I would like to throw in a question for discussion: What is the
minimum set of features for something to be a wiki?
I added this to my Django flatpage* based site:
{% if user.is_staff %}
<a href="/admin/flatpages/flatpage/{{flatpage.id}}/">edit</a>
Which lets my client click around his web site, and if he sees
something he wants to change, click the edit link, make change, hit
save, refresh page, see change.
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.
[1] http://docs.djangoproject.com/en/dev/ref/contrib/flatpages/
--
Carl K
_______________________________________________
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/AANLkTilgzCwHCyGveV6CBNo3aowAtNSmkrzq2b9gtPxB@mail.gmail.com
Author: Ted Roche
Posted: 2010-06-05 15:03:40 Link
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