The Booki software used to write FLOSS Manuals is an interesting approach to a Wiki. Anyone can edit a page, just like any other Wiki, but you can also publish a separate, static version of the pages and you can control who gets to publish these pages. This gives you both worlds: a static page that is endorsed by an editor and a collaborative environment to create and edit pages. As a bonus you can generate a PDF of your site in a suitable format for print on demand publishing.<br>
<br>This would be overkill for a lot of things, but it there was a subset of the wiki that would benefit from tighter control on content then Booki gives you a pretty good way of achieving that.<br><br>James Simmons<br><br>
<div class="gmail_quote">On Sat, Feb 2, 2013 at 9:54 PM, Ron Feigenblatt <span dir="ltr"><<a href="mailto:docdtv@gmail.com" target="_blank">docdtv@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 2/2/13, Frederick Grose <<a href="mailto:fgrose@gmail.com">fgrose@gmail.com</a>> wrote:<br>
<br>
> Be assured that all changes saved in a wiki can be recovered from the 'View<br>
> history' tab for a page.<br>
<br>
</div>Indeed. But sometimes one has worthy reasons for assigning pre-emptive<br>
editorial power over a page to an individual. For example, shouldn't<br>
the current leader of the Marketing Team have exclusive write-control<br>
over the Marketing Team page? That need not prevent petitioners from<br>
making change suggestions on its Discussion page, as you noted<br>
immediately below.<br>
<div class="im"><br>
> While one is reconstructing an existing page, it is often best to copy it<br>
> to a separate page as content details are worked out. Open discussion (on<br>
> the associated 'Discussion' page) with other interested authors will<br>
> generally lead to improvements.<br>
<br>
</div>Having a "watch" set on a page is not the same as having the time to<br>
respond to changes every week, much less every hour.<br>
<br>
I think it would be useful if everyone with wiki login credentials had<br>
a quota of space for creating content they ALONE can write. Not only<br>
could they create NEW content they alone control, but they could also<br>
create and nominate full-blown REVISIONS of content OTHER people alone<br>
control for linking from the respective Discussion page of the latter.<br>
<br>
The Wikipedia article on the Wiki at <a href="http://en.wikipedia.org/wiki/Wiki" target="_blank">http://en.wikipedia.org/wiki/Wiki</a><br>
interprets Wiki creator Ward Cunningham's book so: "A wiki is not a<br>
carefully crafted site for casual visitors." If one accepts this, then<br>
it might be useful for a heading on EVERY page of the wiki to state<br>
just that and link to a conjugate non-Wiki Website for such casual<br>
visitors. That way, e.g., Sean Daly's prospective wiki-illiterate<br>
teachers would not be denied the chance to peruse the wiki, but at the<br>
same time would be properly served by immediate referral to the<br>
material intended for their eyes.<br>
<br>
I hope you will also consider the Wiki education suggestion I made on<br>
your personal page.<br>
<br>
For about a third decade, between summer 2005 and late 2008, I tried<br>
to seed wiki literacy in my literacy-phobic rural USA community. It<br>
started with a digital technology course I gave at a new local public<br>
library, whose remarks about wikis lie within the lesson on<br>
asynchronous groupware at<br>
<a href="http://www.rootsweb.ancestry.com/~gahchs/BHPL/FOTL/DigTech/Chapter4/" target="_blank">http://www.rootsweb.ancestry.com/~gahchs/BHPL/FOTL/DigTech/Chapter4/</a><br>
<br>
I only managed to get two people to attempt wiki writing. One was a<br>
woman in her 30's with a Bachelor's degree in Russian who commuted to<br>
work in India, and had experience as an exchange student in Russia.<br>
The other woman, in her 40's, was a non-degreed engineer who manages a<br>
state highway construction crew, and whom I think recently became a<br>
member of the county development authority. Both gave up almost<br>
immediately due to the challenge, rather than their disbelief in the<br>
utility of wiki-writing. (I had them try using Wikispaces.)<br>
<br>
The first public evidence of wiki literacy in this part of the state I<br>
encountered was a link to a staff-only wiki on a public Web page of<br>
the regional public library system within the last couple of years.<br>
(Aside: I must say that I was shocked that as C-SPAN's BookTV<br>
programming celebrated its fifth anniversary some years ago, I<br>
discovered that the assistant director of this regional system had<br>
never heard of its existence.)<br>
<br>
Let me close by assuring you that my previous inquiry was not<br>
rhetorical: Frederick, is it possible to give an individual user the<br>
exclusive power to write a particular wiki page within the MediaWiki<br>
system we use here at Sugar Labs? Thanks.<br>
<br>
Ron<br>
_______________________________________________<br>
IAEP -- It's An Education Project (not a laptop project!)<br>
<a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br>
</blockquote></div><br>