> okay. what can i do to help? is there a to-do list, or is it already done?
Well, lets see. Getting some decent links in the rendered pod is task #1 and the blocker at the moment. > should we hook this up to 'perldoc -q'? unless someone else is working on > it, i'll write the script. Maybe a seperate perlfaq script? I'm not sure what the value of this is if we have a search facility. > and where does all of the tools you used live? should we put those in CVS? > i created a bin directory in the perlfaq repository and put a couple of my > tools in there. Right now it's just pod2html - which is lacking. > some near term things i wanted: > * most recent perlfaq at a stable URL (rather than a link to a viewcvs page) Done. (Pending proper htmlization. So I guess it's not really done.) But the url (lets not declare this stable yet) will be faq.perl.org. We may want to not have the (equivalent of) perlfaq.pod be the main page at faq.perl.org - in which case that front page needs to be designed. It should probably also have some information about perlfaq-workers and perl-documentation on it. > * a search facility Will a restricted google search be good enough? If not, is there a particular free search tool you like? > some short term things: > * a structured way to give feedback > * a way to ask "did you find this answer helpful" These should be part of the rendered html. Possibly links to a script, or some such. What kind of structure were you thinking, and where would the data go? > * a list of alternate resources in case the faq didn't help This should be part of the FAQ. ;) > long term: > * a way to score search results by collected helpfulness data Interesting idea. > * a list of alternate resources on a per-question basis (i.e. additional reading) This should be embedded in the FAQ somehow. =for alternate-answer See http://www.website.dom/how-to-use-scalar-variables-in-perl It almost sounds like we need a custom pod2html renderer, Pod::POM anyone? (Ziggy- Weren't you working on that?) -R
