Bill Moseley wrote:
http://domm.zsi.at/modperl-site-domm/mp_bg/
I forget, why isn't there aIt's not there by design :) I didn't think of having it. Do we really need it?
Home menu item?
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.
Of course it can. That's the presentation problem, (i.e. template, not DocSet). But the decision should be done not based on the number of sessions but their size. Consider that you have only two sections but they are huge.
So?
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.
OK, that was discussed already. We should split the menu in two, the second menu should be located under the first one (probably should look differently?) and there we put things like http://asf.apache.org/, take23.org, perl.org and others. (there should be just a few links there)
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.
Well, I was looking for some short title for the menu, but I couldn't find anything shouting, while still short, in English. 'Extraordinaire Technologie' does pull people's attention as something different from other items.
Of course better ideas are welcome.
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.
All these are going to be a part of the documentation project. Once you start doing this as a separate project like you suggest it's going to grow and become too big, then there will be duplications and annoying discrepancies between the two. There should be a good overview document(s), roadmap, with short notes and links to further reading.
We can always link to this (these) directly from the menu. There is no need to reserve blank pages for this.
- White Papers, which can be discussions (summaries from the mod_perl list) such as the eToys paper, and caching techniques.
I guess you didn't browse the site :) There is a whole new category for this kind of docs:
http://domm.zsi.at/modperl-site-domm/docs/2.0/world/index.html
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 ;)
Yup, all very good thoughts. I suggest that you simply start creating new pods and the moment we release the site, we start working on finding parents for these orhan documents. I plan to have a huge 'world' documentation section. People from many non-mod_perl projects will find themselves reading mod_perl site. That's the trap you and I are working on now :) Next stage would be to make a good bait.
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.
Sure, go ahead and send me the pods with abstracts you want.
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
