Discussion Website

This project is a discussion website that is similar to a discussion forum such as vBulletin but much of the advanced features will be scrapped, such as bbcode text formatting, the adding of subforums, moderating of users, etc. This project will probably require someone who is familiar with PHP and MySQL development. As well, the ability to create better interfaces using AJAX and Javascript. You must also be able to convert the URL's produced by the script into fully SEO-friendly URL's. Each topic/discussion title is in the form of a question, which makes it fun for the users. The design and mock-up is already created by me, and can be viewed at the following URL: [url removed, login to view]~abcdefga/talkaphobe Now is just the question of making it fully operational.

## Deliverables

1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.

2) 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 Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.

b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.

3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer 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 buyer on the site per the coder's Seller Legal Agreement).

As a developer for this preliminary project, you are responsible for: - Creating the basic structure of the website. - Make sure that the mock-up design fully functions as it is. - Create a file where admin values can be edited. A fully featured admin interface is not required to keep costs down. - Incorporate a simple templating system for modifying the template. - All URL's are to be SEO friendly. - You must, and should provide a working demonstration before payment is released or payment can be met halfway. - You should code this from the ground up, as well, there should be some focus on security to prevent future hackers. --------------------------------- The following spec sheet will describe the project fully. You are welcome to suggest and make any ideas/improvements as long as you discuss it with me beforehand. I'm a fairly open person. A copy of the spec sheet below can be found at: [url removed, login to view]~abcdefga/talkaphobe/[url removed, login to view] ---------------------------------------- Front Page Every time a user comments on a topic, other than the author himself, that story will be moved or bumped up in order. The admin should be able to set the number of hours before a story cannot be bumped up any longer regardless of a new comment. As you can see, the size of the fonts are determined by the number of comments a topic has. The admin should be able to change how many comments determines its font size through the admin panel. Any story title highlighted in blue means that the current logged-in user has commented on that topic, or is the author of that topic. Advertisement links (in orange) can be inserted by the admin at any time. These advertisement links will appear in random order and will be hardcoded as

* . By random order, I mean that whenever a user refreshes the page, it could be at the top, middle, bottom, etc. These advertisement links will appear on every page on the front page (for example, page 1, page 2, etc.) as well as all 3 sections. The front page has 3 main sections: - All Activity: Basically all stories (popular+new) will appear here. Notice that if a story is new, it's HTML will be hardcoded as

* . After a user comments on a story labeled "new", it will show the number of comments it has, rather than the "new" label. - Popular: The administrator will be allowed to specify how many comments are required in order to be classified as a popular story. - New: All stories submitted will be gathered here. When a story becomes popular, it will be removed from the "new" section and moved to "popular". After a new story gets commented, it will display the number of comments rather than the "new" label beside it. Also, after a specific amount of hours, the "new" label will be replaced by "no comments". The administrator should be able to how many hours before this happens. All 3 sections must have a RSS feed available. Story The author is allowed to edit the story for a certain period of time. The admin will be allowed to set when the editing time period expires. Editing of the story (as well as comments) should be AJAX powered to avoid refreshing. RSS feed is available for the comments. Users can "quote" other comments by clicking "reply" button. Similar to the quick reply in vBulletin forum. When users reply a multiple quoted comment, only the current comment will be quoted, the rest of the previous quotes will not be included. Users can add images to their posts by simply entering the URL of the image when they submit the comment. The script should detect that it is an image and display the image, rather than display the URL. Any URL entered into the comment submit form will be automatically parsed and have the rel="nofollow" tag. Users will be allowed to edit their comments for a certain period of time. The admin will be allowed to set when the editing time period expires. Profiles The profile lists all the total stories that the user has posted in or created sorted by time of participation. When there is a new post, it is bumped up to the first story and highlighted in bold text. Once a user views that story, the story title will not be bolded and will return to normal text (similar to vBulletin). Users can upload their own avatar when they edit their profile. The image uploaded will be a size of 48x48 pixels and re-rendered/resized at the highest quality. A RSS feed is available on the profile page for subscription to keep track of new posts. Forms (Register, Login, etc.) If an error occurs during a form submission, the error will be printed out in the same page when the user submits the form, rather than being led to another page containing the errors and asking the users to go back to correct the changes. When a user is on the story page, and clicks login; after they login, they should be led back to the original page where they came from, in this case, story page. Registration verification during registration is by using CAPTCHA image verification. During submit process, the script will detect whether or not a "question mark" (?) is added to the end of the topic title, if not, it will add it automatically at the end. Regarding SEO, an example would be: Topic Title: Is this a topic title? URL: [url removed, login to view] In this case, this story is the 1923th story submitted.

## Platform

This script will probably be run on a Hostgator hosting account, which runs on Linux hosting. I'm not a programmer so I do not know what the huge deal between PHP version 4 and 5 is. But I would expect that you use PHP5 to keep up with the latest innovations.

Computer-Sicherheit Ingenieurwesen JavaScript MySQL PHP Softwarearchitektur Testen von Software Websicherheit

Projekt-ID: #3199706

Über das Projekt