Written by
Heather Floyd
For umbraco versions:
AllReference
What umbraco is, what you need, how to get started.
One of the advantages of using a CMS like umbraco for your web project is that each of the "pieces" can be developed independently of each other once the initial Document Types are defined. This, along with the the built-in user permissions capabilities can really speed up site development when different people are involved on different parts of the site development.
Here is an example of this "parallel development"
After the general site structure has been designed (information architecture and document types), the INFORMATION ARCHITECT can log in to umbraco and set up the various Document Types required for the site. S/he can also create the various Content Nodes, but without all the website copy.
As soon as this is done, the CONTENT EDITOR can begin adding the approved copy into the Content Nodes (or add additional Content Nodes as needed, etc).
At the same time that the copy is being added, the DESIGNER can work up the templates and stylesheets for the site and concurrently PROGRAMMERS can develop XSLTs and work on integrating more advanced stuff like custom user controls, etc.
Not having to wait for each department to finish work before the next department can begin theirs really helps speed up the site development for a web team, and the easy-to-use umbraco interface allows non-programmers like content editors and designers to work directly with the site, rather than having to push their work through programmers to get added to the project.
umbraco's Users & Permissions allow PROJECT MANAGERS to determine what various people should be able to change and publish on the site, so content writers can't publish new content until editors or managers have approved it, and designers can't edit content, etc.