Support/Editor:PRD - Revision history

Kelimutu: category -> Support Archive

2021-07-14T09:25:20Z

category -> Support Archive

← Older revision		Revision as of 09:25, 14 July 2021
Line 103:		Line 103:
	* Re-arrange items in editor {{bug\|428073}}		* Re-arrange items in editor {{bug\|428073}}
	* Add links to best practices, style guide, and policies at the top of the editor {{bug\|446071}}		* Add links to best practices, style guide, and policies at the top of the editor {{bug\|446071}}

			[[Category:Support Archive]]

Djst at 15:50, 6 November 2009

2009-11-06T15:50:14Z

← Older revision		Revision as of 15:50, 6 November 2009
Line 1:		Line 1:
	Firefox Support Knowledge Base Editor Requirements Document		Firefox Support Knowledge Base Editor Requirements Document
			{{DRAFT}}

	=Overview=		=Overview=
	Intuitive and simplified Knowledge Base article editor.		Intuitive and simplified Knowledge Base article editor.

			==Note==
			This PRD needs updating and clarifications.
			* WYSIWYG will not happen
			* Buttons to add screenshots/screencasts missing
			* Edit area should be resizable
			* Left-side column for labels should go away as it wastes space (the mockups imply this, but doesn't specifically say it)

	==Permissions==		==Permissions==

TMZ at 17:34, 19 October 2009

2009-10-19T17:34:12Z

← Older revision		Revision as of 17:34, 19 October 2009
Line 8:		Line 8:
	* When creating a new article, all options are available.		* When creating a new article, all options are available.
	* After an article has been created, only an admin can change the language.		* After an article has been created, only an admin can change the language.
	* When editing an article only locale leaders and admins can change an article category. (Staging area, Knowledge Base, Live Chat, etc.)		* When editing an article only locale leaders, approvers and admins can change an article category. (Staging area, Knowledge Base, Live Chat, etc.)
	* When editing a staging copy, category cannot be changed.		* When editing a staging copy, category cannot be changed.

MarcLaporte: /* Technical Requirements */

2009-09-24T14:50:17Z

Technical Requirements

← Older revision		Revision as of 14:50, 24 September 2009
Line 90:		Line 90:
	* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.		* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.
	* Create or find icons for the editor toolbar that are easily interpretable.		* Create or find icons for the editor toolbar that are easily interpretable.
	* The image upload feature should be part of the editor toolbar, just like in Wordpress.		* The image upload feature should be part of the editor toolbar, just like in Wordpress. {{bug\|398767}}
	* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug\|446072}}		* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug\|446072}}
	* Get rid of the category selector on staging copies.		* Get rid of the category selector on staging copies.

Cilias at 03:23, 24 November 2008

2008-11-24T03:23:18Z

← Older revision		Revision as of 03:23, 24 November 2008
Line 79:		Line 79:

	=Mockups=		=Mockups=
			The top of the editor will contain a warning that content needs to be reviewed before being applied to the Knowledge Base, and provide links to best practices, style guide, and policies page.
	* [http://ilias.ca/sumo/creating_an_article.xhtml Creating a new article]		* [http://ilias.ca/sumo/creating_an_article.xhtml Creating a new article]
	* [http://ilias.ca/sumo/staging_copy_non-locale_leader.xhtml Editing a staging copy]		* [http://ilias.ca/sumo/staging_copy_non-locale_leader.xhtml Editing a staging copy]
Line 85:		Line 86:
	* WYSIWYG editor {{bug\|454131}}		* WYSIWYG editor {{bug\|454131}}
	* Adding and removing tags should not be part of the article editor		* Adding and removing tags should not be part of the article editor
	* Dynamic content blocks should be part of the editor toolbar as a quickpaste function.		* Dynamic content blocks should be part of the editor toolbar as a quickpaste function. {{bug\|446078}}
	* Buttons on the editor toolbar for applying SHOWFOR.		* Buttons on the editor toolbar for applying SHOWFOR. {{bug\|446076}}
	* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.		* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.
	* Create or find icons for the editor toolbar that are easily interpretable.		* Create or find icons for the editor toolbar that are easily interpretable.
	* The image upload feature should be part of the editor toolbar, just like in Wordpress.		* The image upload feature should be part of the editor toolbar, just like in Wordpress.
	* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug\|446072}}		* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug\|446072}}
			* Get rid of the category selector on staging copies.
			* Relabel "Edit Summary" in editor and add something to it about citing a reference. {{bug\|446070}}
			* Re-arrange items in editor {{bug\|428073}}
			* Add links to best practices, style guide, and policies at the top of the editor {{bug\|446071}}

Cilias at 03:10, 24 November 2008

2008-11-24T03:10:39Z

← Older revision		Revision as of 03:10, 24 November 2008
Line 83:		Line 83:

	=Technical Requirements=		=Technical Requirements=
	* WYSIWYG editor {bug\|454131}		* WYSIWYG editor {{bug\|454131}}
			* Adding and removing tags should not be part of the article editor
			* Dynamic content blocks should be part of the editor toolbar as a quickpaste function.
			* Buttons on the editor toolbar for applying SHOWFOR.
			* {SHOWFOR(spans=on)/} should be automatically applied to every article that uses the feature.
			* Create or find icons for the editor toolbar that are easily interpretable.
			* The image upload feature should be part of the editor toolbar, just like in Wordpress.
			* The width of the content area should be 100% of available space; and default height should fill up a large portion of the average screen space, only leaving room for the toolbar. {{bug\|446072}}

Cilias at 03:06, 24 November 2008

2008-11-24T03:06:00Z

@@ Line 3: / Line 3: @@
 =Overview=
 Intuitive and simplified Knowledge Base article editor.
 ==Permissions==
 * When creating a new article, all options are available.
 * After an article has been created, only an admin can change the language.
-* When editing an article only locale leaders and admins can change an article category. (Staging area, Knowledge Bae, Live Chat, etc.)
+* When editing an article only locale leaders and admins can change an article category. (Staging area, Knowledge Base, Live Chat, etc.)
+* When editing a staging copy, category cannot be changed.
 ==Fields that require entered data==
-* Lanugage
+* Language
 * Summarize your edit and cite a reference

Cilias: New page: Firefox Support Knowledge Base Editor Requirements Document =Overview= Intuitive and simplified Knowledge Base article editor. ==Permissions== * When creating a new article, all options ...

2008-11-24T02:30:18Z

New page: Firefox Support Knowledge Base Editor Requirements Document =Overview= Intuitive and simplified Knowledge Base article editor. ==Permissions== * When creating a new article, all options ...

New page

Firefox Support Knowledge Base Editor Requirements Document

=Overview=
Intuitive and simplified Knowledge Base article editor.

==Permissions==
* When creating a new article, all options are available.
* After an article has been created, only an admin can change the language.
* When editing an article only locale leaders and admins can change an article category. (Staging area, Knowledge Bae, Live Chat, etc.)

==Fields that require entered data==
* Lanugage
* Summarize your edit and cite a reference