How do Internet based companies organize/manage building their websites which is normally built by more than one person some of who are front-end designers and some are back-end developers?

Building large websites, portals (for example for a large company or university) or advanced web-applications is a complex activity that coordinates many skilled people working in unison, usually organized as a project. There are plenty more people involved than the few you have listed, usually from several different organizations and companies. Copywriters, designers, project managers, hosting people, different types of stakeholders. This is why projects like this tend to need many meetings, dedicated project managers, project management tools, and usually a project management process. Is your question mostly about the technical aspect and tools? This differs as much as the other parts between companies. There are a ton of good development practices out there, but the sad truth is that most companies manage this rather badly and get by by putting an extra effort every time. A sensible setup for professional development would be: All content lives separately from technical implementation and code. All code and all content lives in some sort of version control system. They don't have to be the same. Every developer has a complete development environment running on his local computer. The developer knows how to set this up and tear it down at will and does so regularily. He can work on it in isolation without impacting others. All (or at least most) code has automated tests of some kind. All technical features should have automated functional tests of some kind. Developers work on branches in the VCS, merging work back to the test or deployment branch when complete and tested by at least one other person. Developers never work completely alone. Every branc should be owned by two people, or at least have a person desginated for peer-review. Some sort of system for continous integration should be in place. A good example is Jenkins. Whenever a branch is merged with the main branch, all automated tests should be run. (first by the developer locally, then also by the CI system.) If the main branch is broken, the tests will discover and warn everyone. Big drama in the office. Someone has to buy beer. Work is managed in a project management tool, with a process everyone agrees on. This is often Scrum, but doesn't need to. Team meeting every day. This can be videoconference, audio, chat, whavever, depending on your setup. It is not clear from the question if "Internet based companies" mean geographically distributed. If it does, all of this gets a bit harder to do — and also a bit more important. There is probably a bunch of stuff i forgot already. This is a big subject. But if you do the stuff above, you are off for a good start compared to many web companies out there.