ArticleLive Snippet Changes

What I need done: Basically we have installed articlelive on our website, but we need to add certain features to it. We are not very sure probably it already has those features built in, but somehow we have no clue about them. If incase it does not have those features then the same needs to be programmed in it. Features like - Comprehensive sorting/browsing of articles, Featured Content (Top Rated, Most Popular, Author Ratings), Changes to the Admin panel so that it appears like a dashboard where the admin can know what are the things he needs to concentrate on. What I already have versus what the provider will build: The provider is only required to do the programming part to integrate the features which we want. Moreover since designing in article requires you to edit the same in HTML, we would give you the design and you would need to bring it out using the HTML programming. Something like what we do while making appearence changes to vBulletin Forums. Other context/requirements that providers will need to know: You would also be supposed to add certain features to the admin interface. We would give you complete details of what we want and how we want it, hence the logical reasoning part we would take up. You would just be required to make changes to the ArticleLive code and make sure the changes we want do appear. Specific expertise that I am seeking: You should be a professional in what article live is and how it runs. We would really want you to have some experience in article live. Timeframe for delivery: We can easily negotiate a time frame. Something upto 4-6 weeks for such minor changes is acceptable for us. Features which we want other than the ones in Article Live already: I. Additons to the User Interface Design - User sign-up / login : Presently, the Article Live shows user login as a link & the option to enter login details (username/password) comes up only on the next page. The developer is required to provide an interface to type in the username/password for login on the main/home page itself instead of a link to another page for login. - User profile : The user profile shall include the following o User picture/avatar which will be a picture file uploaded by the user o Name o Age o Location (City, Country etc.) o About me : A textual description of him/herself provided by the user (limited to 100 words) o Homepage / Blog URL Apart from the name (which shall always be shown whenever the profile is visited by another user), the user shall be able to choose whether to allow his/her other details to be displayed for other viewers. In addition to the user’s details listed above, the following shall also be displayed on the user’s profile: o Number of articles published (This shall take into account ONLY articles submitted by the user which have been published, rejected articles shall be considered null & not counted) o Avg. Rating of articles (which shall be the arithmetic mean of the rating of all published articles which have been rated by users) o View all articles published by o Number of posts in Forum - “Track my Submissions” : Following the submission of an article by user, the same shall be subjected to a 3-stage approval process by the administrators (which shall be discussed in a subsequent section). “Track my submissions” should link to a page showing the user the status of his/her submitted article(s) viz. the stage at which the article is pending for approval. In the case of articles which have been approved & published , the status should indicate “approved & published”. For rejected articles, the status shall indicate “Rejected. Reason : _______” For non-registered users, as described, the publishing of the article shall be subject to the results of the approval user. However, the site shall allow even non-registered users to Track their submissions. This shall be done by meand of mapping the user’s IP address to the article(s) submitted by him/her and the status of approval as it shows up for registered users shall also show up for non-registered users. Apart from this, we also envisage a points whereby a certain number of points can be awarded to users (ONLY registered users, this privilege shall not be extended to non-registered users). As the points accumulate, these could then be redeemed by the users for certain discounts/privileges. We haven’t yet ascertained the details for this. However, the developer is required to provide a provision for integrating a points system with one or more of the user’s ranking, avg rating of posts and number of posts. The details of the point system (that is, the algorithm to arrive at the number of points to be awarded) shall also be made customizable so that the same can be changed depending on the prevailing circumstances and user pool. II. Admin Interface Design : Upon login, the Administrator interface is required to display a summary of all pending actions. For example, • Changes (Edits to an existing article) by registered Users to be approved : AAA • New articles submitted by registered users to be approved : BBB • Changes (Edits to an existing article) by non-registered users to be approved : CCC • New articles submitted by non-registered users to be approved : DDD The approval of articles shall typically follow a 3-stage process: 1) Technological / Format compatibility 2) Copyright check and check for redundancy due to repeat from an already-published article 3) Editorial check for grammar / use of language and for sorting based on category/topic The typical priority of the approval processes in the workflow shall be as follows: Priority 1: Changes (Edits to an existing article) by registered Users Priority 2: New articles submitted by registered users. Priority 3: Changes (Edits to an existing article) by non-registered users Priority 4: New articles submitted by non-registered users. The notifications sent to the administrator(s) shall display the corresponding priority of the pending approval. Also, if no action is taken on a pending approval, the same shall get cascaded to either another (set of) administrator of either the next stage of approval process, or to administrator(s) with superior privileges. The time-frame for such a cascading of approval actions shall be customizable. III. Article Design - Contents/layout of Article Page : The following shall be indicated and/or provided for each article page o The name of the original author of the article as well as the names of all users who have subsequently edited the article. The date/time of each publishing (either as a new article or as an edit to an existing article) shall be indicated. The author’s details shall link to the author’s profile. o A counter to count & update the number of times the article has been viewed, rated and favourited. The same shall be indicated along with the title of the article as described above for the average rating. o Time required to read the article : This shall be based on a reading speed of 3.7 words per second. So, for example, for an article having 370 words, the following should be displayed “Time required to read this article : 1 minute, 40 seconds” (As time required = 370/3.7 = 100 seconds = 1 minute, 40 seconds ) o Copyright information is required to be below each article which either the user can paste in a separate column titled references or the moderator/admin who is working on the copyright aspect should do it. - Edit Article: The “Edit Article” link provided on each article page shall link to an interface which shall be similar to the one for submitting new articles. The only addition shall be in terms of an additional option which will ask the user the reason for editing the article. It will provide options such as “Incorrect Information” , “Obsolescence of Article”, “Update based on latest info” etc etc. The same shall be used as a guide by the administrators for approving edits. This list shall be fully customizable to allow updation by Admins. In addition, the developer shall note that, in the present Article Live system, the privilege to edit articles is limited only to select users granted such privileges by the Administrator. This feature is required to be available to all users without requiring any admin approval IV. Home Page Design As part of the Scope of Work for the Home page design, the developer shall provide all elements and the associated design required for the features as listed in the “Summary of Scope of Work” section. With regards to implementation of the same, the developer is expected to provide a homepage design, which in appearance, looks elegant and wholesome (that is, displays lot of details on the home page and utilizes all available space on the home/main page in the best possible manner). V. Donate (via pay pal) Mailing Lists / Subscriptions : An option to join mailing lists and/or to subscribe to newsletters/mails shall be provided on the home page of the user interface by means of a provision to directly type in email & name (Similar to the user login details described elsewhere in this document) In addition, an option for “Email” or “Newsletters” shall appear on the Admin Interface/Control Panel whereby the Administrator shall be able to choose which emails/newsletters to send to specified user groups (The provision to classify users into user groups has already been provided in the Article Live Admin Control Panel, and thus, the same is excluded from the developer’s scope. The above details make look damn complicated but trust me they aren't at all. They have directly been copied from our description document.