#304: write an article in Yorg mode

Type: FeatureItem Feature:   Tags:  
ScheduledFor:   Assigned to:   Sites:  
Priority: 0 Status: % finished: 0%  

Rationale

Requirements on the Features Multypass.5EN:

  1. Write and manage articles (public, private) with WYSIWYG features
  2. Submit an article for syndication on one or several communities
  3. Indicate the maturity status (Draft, Up to date, Mature, Out of date) and make this piece of information available.
  4. Choose the type of article in a list of available models (review, photo gallery, contact directory...): it will lead to a form with different number and type of fields (reference http://www.microformats.org)
  5. Add/remove authors for an article for collaborative writing.
  6. Ability for members to ask to another member to become one of the co-authors
  7. Ability for an author to invite other members (or non-members) to become co-authors of an article (the non members will have to subscribe before being able to become authors).
  8. Basic image manipulations (rotate, resize, crop) and easy insertion into articles
  9. Categories for articles (information type, themes, geographical area...). An article can be stored in several categories and the user can suggest to moderators the creation of a new category if necessary.
  10. Manage versions of articles and choose the one to display
  11. Generate a template for an article with fields (example : for subscription to an event), see example of this feature on Mayetic village
  12. Use an internal image database
  13. Save the data of a personal USB-key into a personal account
  14. Upload local files with « drag and drop » (with Ajax, Flash or any appropriate technology) with support of multiple simultaneous files if possible

Table:

Error: can't fetch image from 'http://www.colivre.coop.br/pub/Multypass/TableForFieldsInArticles/table_for_articles.png': 500 Can't connect to www.colivre.coop.br:80 (Bad hostname)

Details from Fields per type of article:

  1. Title: Field Text, free, xx Character
  2. Body:
    1. Link: field free text up to XX characters
    2. Blog: an article text, with WYSIWYG editor, and it can contain images, Youtube videos URL's.
    3. Image: an image (web formats: jpg, png, gif, etc ...)
    4. Wiki: a new wiki page , to be inserted in your Blog, or enterprise site community
    5. Forum Tread: field free text , up to XX characters
    6. Poll: fields for a insertion of a question, with up to 5 options of answer, and also the option to insert more answers.
    7. Agenda Item: the body of the agenda to serve the user insert a description of the event, however there will be other options of selection, such as: data (a mini-calendar should appear), place, participants (which can be chosen between contacts), if the event is regular or not (if so, define the periodicity), links to relevant items, alarms by email, defined by the user for X hours before the event.
    8. Formulary: similar to poll, the user can create a small formulary, using free texts fields . Each field can be a question / issue / requirement for insertion, and each answer can be a selection radio button (as in the polls), a checkbox, or a free field for fullfilling with text or image (WYSIWYG)
    9. The field body will be the ticket description .
  3. WYSIWYG: a visual text editor , which standard options,with the possibility of inserting images directly to an container (without having to set the URL of image),uploading the image, or selecting an image in the user image bank, a container(Gallery of images).
  4. Author: The author of the article may determine if his name will be, or not, presented as an author of the article.
  5. Multi-Author: The author can specify if the article will be written by him, only, or by other users, in collaboration. If the user chooses to write a multi-author article , he should select among his contacts / friends, people who should be invited to organize the article.
  6. Subtitle / description: A field of free text (small) for insertion of a short description of the article. Common for pictures and article introductions.
  7. Description Field: Allowing user to write a introduction to his article, being it any type or article.
  8. Allow Comments: a question with two answer options , yes or no. If the answer is yes, the authors should receive emails and moderate every comment, BEFORE, it be published.
  9. Private: a question, with two answer options , yes or no. If the answer is YES, only the user can publish the article, in his blog or his community site . If the answer is NO, everyone can publish the article.
  10. Tags: the user should select, among the tags available in the system, tags that categoryze his article, by centre of interest, subject, territory, etc. ...
  11. Who can view?: A question to be answered to user A (as checkboxes I think). This option allow another users to see and monitoring his content and RSS feed. The next two intens are related, 12 and 13.
  12. If user A want allow to another users to see his profile content/RSS, he need to select if his content is available to his friends and communities, or...
  13. If will be available to all web users (even if anonymous).
  14. Post on: This option is similar to the previous question (allowing users to see his profile), but the difference is that this question asks user A about to POST the article, the options are, only my blog,...
  15. My communities, or my selected communities.
  16. Show date of creation? A simple question that (also a checkbox I think) allow to display when the article was inputed in the system.
  17. Show last modification? A simple question that (also a checkbox I think) allow to display when the article was modified last time in the system.
  18. A question asking user A if this article will be moderated by you alone (in his blog) or togheter all moderators (in his communities)

Quality Assurance checklist

All the items below must be "Yes" or "N/A" in order to consider this requirement as done.

Ready? Item Percent
No Source Code 40%
No Unit tests for all models and libs related to this requirement 10%
No Functional tests for all controllers related to this requirement 10%
No Integration test for the requirement (user story or not) 10%
No All tests pass? 5%
No User documentation for every possible user action 10%
No Developer documentation for all methods everywhere 10%
No Non-developer user test 2%
No Customer test 3%

-- GuilhermeRocha - 15 Apr 2008
Add comment
You need to login to be able to comment.
 

Topic revision: r5 - 18 Nov 2009, AntonioTerceiro

irc Talk with Devs Now!

 
Translations: English
Search on Docs:
   
ActionItem Search:

Copyright © 2007-2018 by the Noosfero contributors
Colivre - Cooperativa de Tecnologias Livres