I need a FAQ Application to add to my website. . . .

As the customer, this is what I have in mind:

• All FAQ entries need to belong to a (predefined) Category

• Required FAQ entry fields:
  • Valid Category
  • Question
  • Answer
  • Author
  • email
  • Date
  • { Links }
  • Maybe some other things

• All FAQ data should be managed in a database on a web server (hereafter called the FAQ-DB).

• There needs to be a web-based application for users to submit new (potential) Frequently Asked Questions (FAQs) to the FAQ-DB. The presentation for this will include text-fields, lists, etc. enabling all (question and answer) information to be entered.

• A successful FAQ question submission yields a FAQ-DB record in a "To be Reviewed" state.

• There must be a (password-protected) web-based FAQ Administration application that enables an administrator to review, edit and delete entries in the FAQ-DB. This application allows an administrator to edit all "To be Reviewed" records and change their states to "Accepted Entry" or "Rejected Entry" among other things.

• The web-based FAQ Administration application must support any necessary "building" of the FAQ web page(s).

• The built FAQ web-page entries must be categorized, adhere to a common look and feel, and use META tags for search engine use.

• The built FAQ web-page layout includes two sections: the index section (top) with questions (organized by category) each with a hyperlink to the corresponding detail. The bottom section contains the detail: question/answer pairs and any optional hyperlinks. (The index section could be implemented as an expandable/collapsible tree).

• The built FAQ web-page must have appropriate headers and footers (including an email link to the FAQ administrator); Example FAQ page

• There should be a visual indication for all "new" entries and "changed" entries since the last FAQ build/install (the build/install date should be visible on the page). Example FAQ page with visual indicators