Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Navigation [hide]
[expand]
- Add-ons
- Architecture
- BLOB providers
- Caching
- Client resources
- Configuration
- Configuring episerver
- Configuring episerver.dataStore
- Configuring episerver.framework
- Configuring episerver.packaging
- Configuring episerver.search
- Configuring episerver.shell
- Configuring module.config
- Configuring staticFile
- Configuring episerver.basicAuthentication
- Configuring .NET SignalR
- Configuring Image Service
- Configuring link validation
- Reading application settings programmatically
- Content
- IContentRepository/DataFactory interface
- Persisting IContent instances
- Synchronization
- Selecting content
- Validation
- ContentType attribute
- Grouping content types and properties
- Page types and templates
- Creating page templates and block controls
- Block types and templates
- EditHint in MVC
- Creating a page programmatically
- Converting page types for pages
- Refactoring content type classes
- Multilingual content
- Properties
- Built-in property types
- Restricting content types in properties
- Writing custom attributes
- Single or multiple list options
- Built-in auto-suggestion editor
- Property settings
- Property attributes
- Property controls
- Custom properties
- Links
- Assets and media
- Content assets and folders
- Custom editing preview for media
- Media types and templates
- Working with media
- Providers
- Deployment
- About the database
- Automatic schema updates
- Content Delivery Network
- Setting up multiple sites
- Planning deployments
- Deployment Center
- Deployment scenarios
- Mirroring
- Dynamic content
- Configuring dynamic content
- Using the interfaces
- Creating UI settings for dynamic content
- Creating a plug-in
- Creating a Hello World dynamic content
- Dynamic data store
- Editing
- Event management
- Globalization
- Determining languages
- Globalization scenarios
- Adding languages
- Localization service
- Localizing the user interface
- Configuring a custom localization provider
- Initialization
- Logging
- Personalization
- Rendering
- Selecting template based on tag
- Template descriptor
- Using data source controls
- Adding edit hints without using Property web control
- Navigation menus and listings
- Creating a main menu
- Creating a submenu
- Display channels
- Display options
- Reports
- Routing
- Scheduled jobs
- Search
- Search integration
- Searching and filtering
- Installing and deploying Search Service
- About EPiServer Full-Text Search Client
- About EPiServer Full-Text Search Service
- Configuring EPiServer Full-Text Search Client
- Configuring EPiServer Full-Text Search Service
- Searching for pages based on page type
- Adding search providers
- Security
- Authentication and authorization
- Virtual roles
- Configuring Active Directory membership provider
- Recommendations for ASP.NET security settings
- Securing edit and admin user interfaces
- AspNet Identity OWIN authentication
- Federated security
- Forms authentication
- OWIN authentication
- Mixed mode OWIN authentication
- Permissions to functions
- Protecting users from session hijacking
- Managing cookies on the website
- User interface
- Context-sensitive components
- Service locator
- Describing content in the UI
- Dialogs
- Shell profile
- Store architecture
- Drag-and-drop
- Message service pool
- Publish and subscribe messaging system
- Introduction to Dojo
- Using jQuery
- Extending edit view
- Creating a component
- Extending the navigation
- Developing gadgets
- Command Pattern
- Object editing
- Views
- Virtual path providers
- Workflows
- XForms
Area:
Optimizely CMS
Extending edit view
Note: This topic has no later version.
This document provides a description on how to plug in gadgets and components to the EPiServer editorial interface.
Plugging in gadgets to the panes
To extend the editorial interface, you are recommended to plug in customized gadgets to the navigation pane and assets pane with information related to the content. These gadgets can have their own tab on the tab toolbar.
When creating a plug-in for the edit view, the PlugInAreas attribute decides the rendering location set by the EPiServer.Cms.Shell.PlugInArea string constant:
- AssetsPanel adds the plug-in as a gadget in the asset pane
- DefaultAssetsGroup adds the plug-in as a tab in the asset pane
- DefaultNavigationGroup adds the plug-in as a tab in the navigation pane
- NavigationPanel adds the plug-in as a gadget in the navigation pane
See also
Last updated: Feb 23, 2015
