Stas has implemented a hierarchical way of limiting searches to parts of the doc tree. It's not done, but you can preview at:
http://hank.org:5000/search/swish.cgi - Also, I haven't really liked how the hover menu items work -- they seem to fade away for the hover instead of standing out more. On my site I changed the menu hover to be just an underline. What do people think? - Along those lines, but a minor point, I think the selected menu item doesn't need to be a link. - "What's mod_perl" seems like it should be "About mod_perl" or "What is mod_perl". Don't ask me why. (AFAIK, I might have recommended What's mod_perl" instead of "About mod_perl"!!). Is the plan to add more content to the "What's mod_perl" page? I could try to work on that, but the rest of my week is shot. - Should the Documentation page give some hints what beginners should read to get started? - I'm never sure which mod_perl archive to search. Can the site offer suggestions? How about a form for each search engine right on that page? Kind of a meta-search page. (Maybe if the search/swish.cgi page returns no results we could do a meta search on a few of the list archives?? -- kind of like, "Nope, not here. Want to try Google?" kind of thing. - How about a cog graphic at the start of the paragraph on the main page. Be nice to jazz up the home page a bit. The first two paragraphs start out lower case m (mod_perl) so maybe that's what it looks a little odd to me. - What's the thinking about writing in the third person? The home page says "you" a lot. For example, instead of "You can use Perl to manage Apache" one might say "Manage Apache with Perl" (although "manage" is a bit vague in this example). I don't think one way is better than another, but it's less formal saying "you" and a bit more professional in the third person. -- Bill Moseley mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
