CMS for company that intermediates news authors to website owners that seek news

Some website-owners seek unique contents for their website. Mostly for SEO reasons. My company intermediates content-seekers (our clients) to participating authors. Website owners who wish to put news on their website can hire us to find a suitable author, who then (re)writes existing news for clients. We have a contract with both the client and the author. All communications between clients and authors goes through us and we also do all the billing. We have personally started creating a CMS to handle the overload of communications. Because of personal shortage in available time, we need a vWorker to finish this job. What we have written so-far is nothing fancy. An [login to view URL] shows "Welcome, username" and then includes global.php. There is also [login to view URL] that shows nothing before it includes [login to view URL] ([login to view URL] is used for in iframes) You can view [login to view URL] here: [login to view URL] As you can see, the [login to view URL] uses a request variable $_REQUEST['action']. Depending on what keyword (eg. "editArticle") is inside that variable, the script will do stuff. Sometimes additional variables are also sent (eg. a written article that an author has written). There is also a [login to view URL] for some generic functions and queries. So actually nothing fancy as you can see. Any novice PHP developer probably yawn a bit at this code. I would like the following to be implemented in the CMS: see below (This list may still grow a bit the coming days.) If you are interested in this job via vWorker, please let me know! Kind regards, Sales department ## Deliverables REQUEST CONTRACT ---------------- - Visitor (prospect client) needs not be logged in - Visitor may enter specific data to request a contract (offer): First name, Last name, Company name, Chamber of commerce, VAT-number if foreign, Phone number, e-mail address, etc OFFER CONTRACT -------------- IF user is an administrator - User may view any open contract_request ([login to view URL] = null) and create a new contract from them (or choose to decline the contract_request) On decline contract: - [login to view URL] = 'contract request declined' On create new contract: - a user account should be created for contract requestor. Username = e-mail address, Password = random - the contract, the current AV (terms and conditions) and the created credentials should be emailed to requestor (BCC to "sales@[login to view URL]") - [login to view URL] = 'contract offer active' There should be a scheduled task (cron job) that checks if offered contracts are not accepted within several days: - After 7 days notify "sales@[login to view URL]" - After 14 days, delete contract and set [login to view URL] = 'contract offer expired'. Notify requestor by e-mail (BCC to "sales@[login to view URL]") VIEW/EDIT CONTRACT ------------------ for all contracts: IF contract belongs to user OR user is an administrator - user may view contract IF user is an administrator AND contract has never been accepted "count(contract_accepted.contract_id) = 0" - user may edit contract IF contract belongs to user AND contract has never been accepted "count(contract_accepted.contract_id) = 0" - user may accept contract On accept/extend contract, user should receive e-mail notifying that contract is accepted/extended. The accepted contract and AV (terms and conditiond) should be e-mailed (BCC to "sales@[login to view URL]") IF contract belongs to user AND contract has been accepted before "count(contract_accepted.contract_id) > 0" - user should view the status and user may extend the contract On extend contract, user should receive e-mail notifying that contract is accepted/extended. The accepted contract and AV (terms and conditiond) should be e-mailed (BCC to "sales@[login to view URL]") REQUEST ARTICLE --------------- ??? (via e-mail?) WRITE ARTICLE ------------- IF user has an editor contract AND number of accepted/pending articles for that editor contract is less than "[login to view URL] * count(contract_accepted.contract_id)" AND contract is linked to a client contract AND number of accepted/pending articles for that client contract is less than "[login to view URL] * count(contract_accepted.contract_id)" AND number of accepted/pending articles for the link of contracts is less than [login to view URL] - User should see menu item "write article" in home screen (done) - User may write an article for that client contract (done) VIEW/EDIT ARTICLE ----------------- for all articles: IF article.client_contract_id belongs to user or is linked to user OR user is an administrator - User should see menu item "view articles" in home screen (done) - User should be able to view that article (done) for any existing article that is still pending ([login to view URL] = null AND [login to view URL] = null): IF user has written that article OR user is manager over that articles' client contract (same set of rules apply as with "write an article", but in stead of "editor contract" user must have a "manager contract") OR user is an administrator - User should also be able to edit that article for any existing article that is still pending ([login to view URL] = null AND [login to view URL] = null): IF user has NOT written that article AND user is manager over that articles' client contract (same set of rules apply as with "write an article", but in stead of "editor contract" user must have a "manager contract") OR user is an administrator - User may publish or reject that article - On publish or reject, user should be set as manager of article - On publish, client should be e-mailed the article (BCC to "artikelen@[login to view URL]") - On reject, editor should be e-mailed the reason of rejection (BCC to "artikelen@[login to view URL]") ADMINISTRATION -------------- - administrator may link incoming invoices to outgoing payments and link them to editor contract - administrator may link outgoing invoices to incoming payments and link them to client contract scheduled tasks (cron-jobs): - check for overdue outgoing invoices and send reminder (BCC to "sales@[login to view URL]")