>>>http://domm.zsi.at/modperl-site-domm/mp_bg/
>> I forget, why isn't there a
>> Home menu item?
>
>It's not there by design :) I didn't think of having it. Do we really
>need it?
I keep looking for it. That's why I asked. Then I remember the breadcrumb.
Stas, can DocSet be smarter about the <top> widgets between sections and
not display them when there's only a small amount of content? Or maybe a
smaller widget or a simple arrow? Just anothe minor point.
Content:
Also, I'm not a big fan of having a menu item to Take23 because it's an
off-site link and it's one of the main menu items. Not to mention
"[EMAIL PROTECTED]" takes you to news that's from last June. I think all those
menu items should stay on-site. No reason the mod_perl site can't have
it's own news, even if it's just a paragraph about a new story at Take23.
Finally: Extraordinaire Technologie -- How about just "Success Stories" or
"mod_perl in action" or something that says "this link will tell you about
sites using mod perl, and stories about using it. I think mod_perl can
speak for itself, and we don't need to boast about it in menu titles.
I also think we need some blank pages (to add menu items) for the
following. Then find people that can fill in the blanks.
- "Getting Started" (which is "tutorial" but more friendly). Or maybe
better a little introduction that includes sub-sections:
a) what is mod_perl?
b) a non-biased comparison with PHP and Java and other server solutions
c) a very short (two screens?) of building mod_perl (five lines), and
a example of a handler (which can be done in a <perl> section)
d) a paper called "How to learn mod_perl" which points to tutorials
and the guide and discusses getting help from mod_perl list
e) a quick overview of related projects (Mason, TT, OI, Embperl....)
I know that's a menu item, but I'm thinking of more of an overview.
It would be hard, but something to help people narrow their choices.
- White Papers, which can be discussions (summaries from the mod_perl list)
such as the eToys paper, and caching techniques.
I'd also like to see a short description on putting together a basic
configuration that includes sessions, Apache::DBI, and the real standard
building blocks that are commonly used. In other words, follow these ten
steps and now you have a platform for building high-end, scalable
applications. Just something to cut down on the TIMTOWTDI confusion when
first starting out.
Just some random thoughts ;)
But I think if we setup the site with fill-in-the-blank pages, it would be
easier to get help from the mod_perl list for content.
Bill Moseley
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
