Oracle® Universal Content Management 10g Release 4 (10.1.4) |
Contents |
Index |
Previous |
Next |
Site Studio Designer Guide > Working With Fragments > Editing Fragments > Editing a Fragment
After you (or another designer) adds a fragment to the Toolbox, you can start editing it right away.
Note: You cannot edit the fragments that come with Site Studio directly because they are read-only. |
To edit a fragment, perform these tasks:
In the Toolbox, click a fragment category: Navigation Fragments, Dynamic List Fragments, Static List Fragments, or Other Fragments.
Right-click the desired fragment and choose Edit.
The fragment opens in the Fragment Editor, where you can start making changes to the fragment (see Using the Fragment Editor).
When finished, click the Save icon (Figure) in the toolbar (or click File, then select Save).
On the Assign Info Form in the content server, enter the appropriate metadata for the library and then click Assign Info.
Note: When you edit a fragment in the Fragment Editor, the fragment library (that the fragment is stored in) is checked out of the content server, and it is checked back in when you close the Fragment Editor. (It is also checked out and checked in each time you save the fragment.) This prevents designers (assuming your organization has more than one) from encountering sharing violations or overriding each other's work. |
It may occasionally be necessaryto click the Refresh icon (Figure) in Designer to see the most current list of fragments in the Toolbox (which reads them from the content server).
In Site Studio, it is good practice to create a copy of a fragment and then edit that fragment instead of editing the original. There are several reasons for this:
You can quickly and easily revert to the original fragment if needed (in case anything goes wrong with the fragment you're editing).
You can quickly get started with your own fragment without re-creating everything in an existing fragment (much like creating a page template based on an existing page template).
You reduce the chances of overwriting another designer's work and consequently, creating unpredictable results on a Web site. The reason for this is that the fragments you create and edit in Designer are stored in one place in the content server. They appear in every instance of Designer that is connected to the same content server, and therefore, multiple designers can end up using the same fragment on different Web sites.