Coachella.com Beginning Stages
Working on major websites is always a challenge in a half. You have various things to take into consideration which includes server load, extensible coding, and a large array of other variables. With large conglomerates such as AEG and Goldenvoice, the numbers out weigh the general costs, but that's not to say to leave them out in the cold with a huge bill.
With coachella.com I was brought in to create a general system that would make things easier on their servers as well as add in new features created for the company that I was working for. Working with the talent at heavenspot.com, this made things extremely easy. This included a codebase that would allow us to have various other coders put their fingers into the project with little to no learning curve. We decided on a framework that would make things as easy as possible with separation between frontend, backend, and database.
While working on the project with the coders, we also learned that the UX and project managers were having issues displaying information as quickly as possible. Instead of going with more frontend developers that might slow down production, we came up with a pretty ingenious system that would allow a single front end developer the ability to layout css that would follow the designers layout in a pixel perfect format. It's not exactly built into symfony2 but we were able to use the templating system that was similar to mustach to get things up and running.
After that we were running into issues with outside calls for various vendors. This proved to be somewhat of an issue because even though we were working with a huge company we still had to worry about server health overall. Doing so allowed us to come up with a caching system that was similar to what facebook uses, but without the conglomerate overhaul.
Generally speaking the overall layout of the website was amazing and the backend allowed for a large array of expand-ability for managers, coders, designers, and client alike. Generally speaking, this is how I usually do project with everyone getting involved to make sure no one things someone is being left out. Can be tiring at times, and challenging, but overall once it all comes together, it makes for a great system overall.
Documentation for projects is definitely a must to make sure coders, managers, and company owners alike are interested in knowing exactly what they're getting themselves into instead of jumping in blindly. I'd recommend using a wikipedia for this, as it allows for users to place more information on the project, has a very organized layout and also allows for some very easy to read information structures.
Check out the link below for some of the best wiki's to use for documentation: