In one
group, all the graphics may be handled by one person or department, whereas layout is handled by another,
and JavaScript coding by yet another. Or, one team may be given total responsibility over one section of a
Web site??”the products section, for example??”whereas another team handles the services division. No
matter how the responsibilities are shared, the danger of overlap always exists. Two or more team members
might unknowingly work on the same page, graphic, or other Web element??”and one person??™s work might
replace the other??™s when the work is transferred to the remote site. Suddenly, the oh-so-efficient division of
labor becomes a logistical nightmare.
Dreamweaver??™s core protection for team Web site development is its Check In/Check Out system. When
properly established and adhered to, the Check In/Check Out system stops files from being overwritten
improperly. It also lets everyone on the team know who is working on what file, and it provides a direct
method of contacting team members, right from within Dreamweaver.
As with any team effort, to get the most out of the Check In/Check Out system everybody must follow the
rules:
n Rule Number 1: All team members must have Check In/Check Out set up for their
Dreamweaver-defined sites.
Pages:
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611