A full discussion of team development exceeds the scope of this blog; however, a brief mention of the relationship between team development and content tree design is worth mention. Typically, developers work in one of two ways: using a shared development database or a local database. In the former scenario, all changes are saved to a common system; in the latter scenario, data is changed locally and moved (using the Packager) to an integration server.
A simple rule of thumb in either scenario is to reduce the incidence of developers writing to the same item or subitems in the content tree. In the former scenario (a single development database), this can create unintended consequences due to the fact that most developers work as Administrator users. This means that common features such as item locking do not apply to them. Developers can easily overwrite each others' changes if they are working on the same part of the content tree simultaneously.
In the latter scenario (isolated development), challenges emerge when moving data to an integration server. Choosing the correct installation options in the Package Installer is often confusing and developers can end up overwriting each others’ changes.
In any case, communication and coordination between developers is essential to ensure that the data in the content tree is accurate.
Subscribe to:
Post Comments (Atom)
2 comments:
Great information provided. I appreciate your work. I like the way you write. Awesome, keep it up.
Web Design Services in Gravesend
Web Development in Gravesend
PHP Services in Gravesend
Nice and simple article about Web Design and if you want to know more about quality based Web Design Services Visit
Web Designers London
Post a Comment