This is a repost and modification of my previous project here:
http://www.scriptlance.com/projects/1235538536.shtml
This is SIGNIFICANTLY LESS COMPLICATED than the original posting.
The end client took a long time to decide on the project requirements so the previous posting got cancelled and some changes have been made to the specifications. I am ready to proceed with this project now. To everyone who posted a bid before, I am sorry for the delay and please feel free to post an updated bid here.
——————————————————————–
Overview:
I need to add certain functionality to a base Drupal installation. This can be done with module installation, configuration and customization. I do NOT need you to build an entire website – I need to configure the needed functionality in Drupal upon which a website can later be built.
I do NOT need any template/theme customization, and no real content will be required other than test content to verify functionality of modules.
Drupal 6.7 or later will already be installed for you with the default setup and the admin module installed:
http://drupal.org/project/admin_menu
as well as the TinyMCE editor which I have tested and works well.
I will provide FTP access, cPanel access, and the Drupal admin login.
I need you to determine which modules to use, install them, configure them and prove that the specified functionality has been acheived, and then explain to me exactly what was done in a step-by-step manner so I can replicate it later. I will need to be able re-create the installation later on a different server (same specs).
User Types:
There needs to be two types of users added. Content Managers and Content Editors. It should be possible to have multiple users of both types.
Demo Preparation:
To create a realistic testing environment, several levels of content pages (fake content) should be created. There sould be several main website sections, each having multiple sub-sections and pages. The content should be 3 levels deep.
Desired Functionality:
I need for the Content Managers to be able to assign content editing and adding priviledges to Content Editors. They should be able to assign content by specific pages, sections of the website, or types of pages based on taxonomy. There should be multiple ‘editors’ possible for any particular page. The exact method for assigning content is open for discussion, but I would like to be clear on the process prior to awarding this project. The managers should also be able to create a ‘placeholder’ page which is unpublished and assign it to an editor for editing.
The editors need to be able to edit their assigned content and submit it for approval. The existing version of the content should always remain published until a manager can review the new content and approve, edit, or reject with comments. If assigned a certain section or type of content, editors should be able to add new pages which are not published until approved by a manager. If a page is rejected, the editor should be notified and they should be able to log in and see the page with the manager’s comments. They should be able to continue editing and resumbit for approval again.
To keep everything organized, each manager and editor should have a place they can view their ‘to-do’ list. From what I understand, this can be accomplished with views, but I could be wrong. Any time an item is added to the user’s to-do list, they should also be notified by email if specified in their profile. It should be very easy for the editors and managers to understand what they can edit, any items waiting for them to edit or approve, and any rejected submissions.
The managers should be able to pull up a list of all content waiting to be approved, and view, approve or reject the changes with comments.
They should also be able to mark any page as needing editing and add comments. Once a page is marked as needing changes, all editors with permission to edit that page should be notified by email and in their ‘to do’ list.
The editors should be able to pull up a list of content they are responsible for editing, and see any edits which have been rejected by an admin.
It is important that once a revision is approved, any futher changes by the editor still require admin approval. The modules I found didn’t work this way. It is also important that new content pages can be created by the designated users of that section but not published until manager approval. This functionality is critical.
Please only bid on this project if you have read the requirements thoroughly and have a clear plan to implement each requirement. For this project, I want to work with someone with a solid understanding of Drupal and good feedback. Please provide links to drupal sites you have created.
Timeframe: This needs to be completed, submitted and replication instructions sent within 2 weeks of being awarded the project. If you will require more time, please specify how long in your bid.
This will be considered a work for hire and all rights to the code created will be retained by the end client.
Communication: The selected programmer shall communicate with me only by email (preferably) or the PMB. No contact will be made with the end client.
Payment: I will escrow 2 payments, each for 50% of the bid amount. The first payment will be released after 7 days and after installing the specified modules (base installation minimum). The second payment will be released after 14 days and after delivery of all required parts to my satisfaction.
Please ask any questions prior to bidding.
I will require a list of the modules to be used so I can review them for any potential problems prior to awarding the project.
Thanks,
Daniel
