This project focuses on the Wordpress CMS. Applicant should have experience in 1) Working with the Wordpress Database, 2) Cookie/Session Expertise 3) Knowledgeable in Wordpress Plugin Creation Standards. What this project aims to do is track ALL visitors and remember which single page items they have viewed. Each single page item will belong to a category. Whenever a single page item is accessed, it is marked as viewed; and removed from a count of unviewed/unread items associated with the parent category. Wherever the visitor is within the website that visitor naturally sees a listing of categories. This modification should embolden the categories that have unread items and at the same time, in parentheses, display the number of unread items within that category; as related to the visitor visiting the page. Visitor tracking should be via IP address,cookie, and logged in status; making use of the best information out of the bunch. If a user's ip shows that 90% of items are read; and then that same IP logs into their user account; the same record of viewed items will be displayed to the user when logged in just as it was when the user was not yet logged in. This project, overall, is designed to emulate the Google Reader feature that allows you to keep track of read / unread items. In addition to the above features... From within the Category display section, there is to be a button that reads 'Mark all items for this category read'. Google Reader Example: [url removed, login to view] Hope to find someone capable and interested in helping me bring about this project. Hudson
1) All deliverables will be considered "work made for hire" under U.S. Copyright law. Employer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the employer on the site per the worker's Worker Legal Agreement).
2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
3) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Employer's environment--Deliverables must be installed by the Worker in ready-to-run condition in the Employer's environment.
b) For all others including desktop software or software the employer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this project.