In article <[EMAIL PROTECTED]>, Robert Spier <[EMAIL PROTECTED]> wrote:
> > 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. it can be the search thingy until we decide we've found something better. maybe just the find dialog in the browser is okay. > 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. i agree that another front page would be nice, but i also don't think we need to work on that right away. > > * a search facility > Will a restricted google search be good enough? probably not, but maybe. Google isn't POD aware, and perldoc is. > If not, is there a particular free search tool you like? nope, but we have a really simple problem - nine files. i don't think something like swish or whatever is necessary, > > 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? no thoughts yet. let's get other stuff done. > > * a list of alternate resources in case the faq didn't help > > This should be part of the FAQ. ;) but we can't put it in every answer, and the more ways we direct people to other resources, the more likely they'll be directed at other resources. :) but who knows. i haven't thought that far ahead. > > 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. maybe. we have other chickens to hatch first. :)
