From Fedora Project Wiki
< FWN
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
1) Define beat writer and editor roles in Zikula | 1) Define beat writer and editor roles in Zikula | ||
* beat writers should be able to: | * '''beat writers''' should be able to: | ||
* open a new article and mark up appropriately with an integrated WYSIWYG editor (using xinhua) | * open a new article and mark up appropriately with an integrated WYSIWYG editor (using xinhua) | ||
Line 13: | Line 13: | ||
* submit their article unpublished for editorial review | * submit their article unpublished for editorial review | ||
* editors should be able to: | * '''editors''' should be able to: | ||
* see a 'to do' list of the unpublished submitted articles in their categories, and be able to edit these | * see a 'to do' list of the unpublished submitted articles in their categories, and be able to edit these |
Revision as of 15:41, 6 December 2009
Zikula currently has a News module but we would like to implement PageMaster[1], which will generate a lot of the code needed to develop and implement a publications workflow.
Dale Bewley has documented[2] some of our initial discussions and thoughts.
Based on this, let's iterate over the proposed workflow:
1) Define beat writer and editor roles in Zikula
- beat writers should be able to:
- open a new article and mark up appropriately with an integrated WYSIWYG editor (using xinhua)
- apply appropriate categories for their beat, to associate it both with a specific FWN issue (for aggregation), as well as to flag it with their beat (also for aggregation)
- submit their article unpublished for editorial review
- editors should be able to:
- see a 'to do' list of the unpublished submitted articles in their categories, and be able to edit these
- publish the edited articles for publication onto Fedora Insight