I am looking for someone to provide me with a [url removed, login to view] clone and a [url removed, login to view] clone - and merge them into one website. The merged site would have all of the look and feel as if the two sites were made for each other - the user would not know there was two sites merged into one. A common style and layout, using CSS for the master presentation. The registration system would allow a person wo register once for both sides of the system.
If there are questoins let me know.
In addition, there is a 10 day requirement on this project.
I have merged sites like this before, so a 10 day dealine I know is very reasonable. It is basicaly saying fit it in over the 10 days as you can. The amount of time needed is not a lot if you are familiar with the scripts you are merging (worked on them before). The scripts would not be required to be "merged" just the look and feel. The scripts can stay in separate folders (sub from main) on the server - to make coding the front end interaction easier and less time intensive.
The site will basically work like this:
1. User comes to the site to see that there is 4 different offerings (job post, job seek, code needed, code provider).
2. They log in (after generic registration) and can then visit whatever they would like.
3. If they have not been to a particular side before (say never looked for a job) they would need to compelte the rest of the job search registration in order to post to listings.
4. From a link they can get to any of the 4 portions they would like.
I am looking for a pretty much canned, but slightly modified solution - not a complete re-write. I will put all of the bells and whistles on when I get the product. I just have no time to merge the two together right now.
As far as costs... A person who already has these scripts, and is only merging the layouts (one site is changed to look like the other site) and merging the registration script (common username shared for both with different sub areas for both sides - a sub registration would be needed for full functionality on both sides). To me I think it would be 3 tables, one for master login which would taken them through the full reg (table 2 - say freelance side) for one side - while the other side has access to table 1 (master account info)for when they wish to complete table 3 (say jobsite) registration.
If a CSS option would take too long (if canned scripts do not already use them) then a fast way for me to change colors and fonts (and sizes) would be the only real need.