Implementing the front end of your GUI extension
Implement the front end of your extension by referencing the .NET assembly of your extension from your web control or webpage, and then extending the specific GUI area you want to extend.
- Adding a .NET assembly reference to your web control or webpage
In your ASCX web controls and ASP.NET webpages, include a reference to the .NET assembly that contains the code-behind for the front end. - Extending a Ribbon toolbar
Both the Content Manager Explorer interface and the Experience Manager interface contain Ribbon toolbars. Ribbon toolbar appear in the main screen of each GUI, but also in some dialogs. You can add both organization elements and controls to any Ribbon toolbar. - Extending a context menu
Both the Content Manager Explorer interface and the Experience Manager interface contain a context menu. You can add both organization elements and controls to any context menu. - Extending tabs in a dialog
Add a tab to a dialog, such as a Component dialog or a Schema dialog, to populate it with controls and/or information. - Adding a slide to the Site Wizard
When you set up the Site Wizard to enable Web managers to create new sites quickly, you may want to add your own slides to the wizard to allow your users to supply, for example, metadata to apply to the new Publication that the Site Wizard creates. This task explains how to add a slide to the wizard, how to display some or all entered data in the wizard's summary screen, and how to hook up the slide's results to a back end for further processing. - Creating a custom area in the slide-out navigation Welcome screen
The slide-out navigation has a Welcome screen with a sidebar on the right. You can create an ASCX resource and refer to it from your Editor configuration to make its contents appear in the lower half of the sidebar.