Firefox3/Web Based Help System: Difference between revisions
< Firefox3
Jump to navigation
Jump to search
No edit summary |
|||
Line 16: | Line 16: | ||
** Who gets to edit and publish? | ** Who gets to edit and publish? | ||
*** The issue of vandalism is very important here since the people viewing this content are coming for help so a link to goatse or some such would be very bad. | *** The issue of vandalism is very important here since the people viewing this content are coming for help so a link to goatse or some such would be very bad. | ||
= Possible Solutions = | |||
== Client Side Solutions == | |||
== Servers Side Solutions == | |||
The big worry for the server is whether it can scale since there is a potential for a lot of hits. | |||
=== Joomla & Joom!fish === | |||
=== Media Wiki === | |||
This is used for other moz sites, wikipedia, and others. It is very likely to scale. | |||
=== phpCake === | |||
[Remora] uses this. It is likely to scale. | |||
=== Webservice & backend with one of the above === |
Revision as of 19:42, 7 February 2007
Requirements
Client Side Requirements
These are the requirements for the parts of the system that will be part of FF.
- Must be usable by extensions
- extension help should show up just like "core" Firefox help.
- but they should be able to look a little different, right?
- extension help maybe on a server controlled by moz and should still be accessible
- extension help should show up just like "core" Firefox help.
- users must be able to give feedback on whethere a particular article was helpful.
- it would probably be helpful to track people over time somehow too
Server Side Requirements
- Must serve properly localized content based on browser's locale
- if content for that locale is missing then serve the content from another locale (e.g. if fr content is missing serve de content. if de content is missing serve en content).
- Content Management facilities.
- must be easy to add, edit, and organize content.
- full l10n and i18n support, ofcourse.
- Who gets to edit and publish?
- The issue of vandalism is very important here since the people viewing this content are coming for help so a link to goatse or some such would be very bad.
Possible Solutions
Client Side Solutions
Servers Side Solutions
The big worry for the server is whether it can scale since there is a potential for a lot of hits.
Joomla & Joom!fish
Media Wiki
This is used for other moz sites, wikipedia, and others. It is very likely to scale.
phpCake
[Remora] uses this. It is likely to scale.