Subject:
Re: PHPNuke HowTo
From:
Tabatha Persad ####@####.####
Date:
11 Jan 2003 02:33:16 -0000
Message-Id: <1042252642.10196.24.camel@mysticchild.dbsoftware.com>
Hi Chris,
You may already have done so (though I didn't notice it in the TOC), but
if not, have you considered a section that provides a general overview
of web log applications before you delve into the technical aspects of
using PHPNuke?
Here are my thoughts... a HOWTO is usually subject-specific, meant to
give detailed information on how to perform a task. If each web log
application had its own HOWTO, each could focus on the particular
aspects of installation, configuration and use of the application. This
group of HOWTOs could be categorically grouped together on the site.
Alternatively, a Guide may be more appropriate for a higher level topic,
such as Web Logs, with an overview each of the different flavors, but
with a broader approach to the subject of web logs overall.
My own opinion is to keep this the way you have it, unless there is
anyone who strongly objects. You have worked with people who've already
written for the application, consulted the Author Guide and adhered to
formatting guidelines, so I would say you've done your homework. Out of
curiosity, is this considered official documentation at PHPNuke?
Again, unless there are any objections, if your draft is complete, I'd
like to see you submit it to ####@####.#### for review and addition
to the collection. :)
Tabatha
On Fri, 2003-01-10 at 17:57, Chris Karakas wrote:
> Guylhem Aznar wrote:
> >
> > One quick suggestion: don't forget to talk about alternatives.
> > Ideally, it should be the "blog howto", talking about templeet, slashdot
> > engine, phpwebsite (...) besides the most widely used, php nuke.
> >
>
> I disagree. Nobody who has a problem with PHPNuke will ever go to Google
> and type "blog installation howto". They will all write "phpnuke
> installation howto". That's a k.o. criterion for me.
>
> Further, a "PHPNuke HowTo" would take, say 120 pages (the "PHPNuke book"
> as it now stands takes already 70-80 pages). It's just so much there to
> clarify, discuss, exemplify, that you need that many pages. Now imagine
> another 100 pages for slashdot, another 100 for phpwebsite and so on. We
> will end up with a monster that nobody will want to read, because it
> will look so blown up *and* it will be only to 1/5 interesting to each
> one of its prospective readers. Because one reader will be interested in
> PHPNuke, but not in the other stuff, the next will want to know
> everything on templeet, but will be totally indifferent to all the
> others and so on.
>
> And third, I only know PHPNuke and I know it well. I read about the
> others just now, in your message. The LDP Author Guide says we should
> concentrate on only one subject and explain *that* well - and I fully
> agree.
>
> So there is no way to go for a "blog HowTo" with me. Perhaps somebody
> else, after I have finished the PHPNuke HowTo and after somebody else
> has written a "templeet HowTo" and another one a "phpwebsite HowTo" and
> still another one perhaps a "phpCMS HowTo", then we could put all these
> together and publish it as a "Guide on blog systems" - but that's for
> the very far future.
--
Tabatha Persad
Web: www.merlinmonroe.com
Linux Documentation Project Review Coordinator (http://www.tldp.org)
Gnu Writing Movement Contributor (http://gwm.gnu.org)
Linux Counter Area Manager US:wa (http://counter.li.org)
