Table of Contents |
---|
Form Components
Info |
---|
Prio 1 components done: http://wcm.io/wcm/ui/granite/ and http://wcm.io/wcm/ui/extjs/ |
Checkbox form component that can remove "true" values and writes Data in JCR as BooleanStatus colour Green title Prio 1
Number textfield form component that validated for a valid number and writes Data in JCR as Integer or DoubleStatus colour Green title Prio 1
Path browser form component with separate touch-compatible browsing dialog using link wizward or miller clumns (hopefully Adobe will develop it), and with support for dynamically detecting the correct tree root (e.g. site root)Status colour Green title Prio 1
Slideshow form multifield componentStatus colour Yellow title Prio 2 - Should be possible to rearrange the slides
- Flexible configuration of the slide panel items in the component definition. Each slide should be able to contain all basic input widgets (selection, text, richtext, image, link...).
- Ideally it should be possible to define multiple links per slide, but this would probably make the dialog unusable
Rich Text: Custom Link Browse Dialog ExtensionStatus colour Yellow title Prio 2
Paragraph systems
Info |
---|
Parsys done: http://wcm.io/wcm/parsys/ - although partially obsolete when AEM template editor is used (but template editor does not properly support nested parsys that are no structure components, and not inheritance, only sharing of configuration through policies) |
Template def. Paragraph systemStatus colour Green title Prio 1 - Define in page component which components are allowed in which parsys on a page
- Allow inheritance via super resource type page components
- Support regular expressions for path matching
- Allow customizing of markup that is inserted before/after parsys, before/after each component
Refresh Parent X InfrastructureStatus colour Green title Prio 1 - Allow flexible definition which parts of the parent DOM elements have to be refreshed on a dialog edit event (not only parent or whole page)
DAM-related extensions
Info |
---|
open |
Media reference form componentStatus colour Green title Prio 1 - Assigning DAM assets via drag&drop from sidepanel
- Browsing DAM assets in the repository using path browser component (with browse dialog, see above)
- Filtering assets by media format
- Apply cropping based on media format ratios (or is this done directly in the asset?)
Customized image map form componentStatus colour Yellow title Prio 2 - Extension of the available forms, which can be applied to the image. Currently it is a square and a round regions, which dimensions can be changed. Most project require just a normal pin with predefined width and height (10x10 px)
- Extension of the edit panel for each map region/pin. The panel should be possible to specify the items of the edit panel in the component definition. Possible configurations should include text, link, image
- It should be possible to use the cropped image in the map definition
Enhanced asset side panelStatus colour Yellow title Prio 2 - Supports filtering by path/subtree
- Supports filtering by media format
Automatic assignment of matching media formats and extraction of size-related metadata when binaries are added to DAMStatus colour Yellow title Prio 2
Support multi-language metadata (as already possible for tag manager)Status title Later
Component Pool
Info |
---|
obsolete with content fragments (AEM 6.2) and experience fragments (AEM 6.3) |
Component pool extension - copy components to pool, inherit from pool, break inheritanceStatus title Later
Admin Console
Info |
---|
open |
Monitor for Sling Jobs (perhaps Adobe is already working on this)Status title Later - Show running jobs with
- Filter jobs by certain properties e.g. Site context
- Show job progress (for jobs that support reporting back its progress)
- Show job history (if supported by Job API)
- Ability to cancel running jobs
- Ability to reorder jobs in job queue or canceling them (if supported by Job API)
Development-related extensions
...