[MAGNOLIA-6520] App launcher configuration via Light Module Created: 28/Jan/16 Updated: 14/Nov/23 Resolved: 14/Nov/23 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4.4 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
A light module must be able to add an app tile to the app launcher at a specific location. The preferred mechanism would be via a YAML file - but if a groovy script or javascript supplied with a light module could accomplish the task that would be acceptable |
| Comments |
| Comment by Antti Hietala [ 03/May/18 ] |
|
In app launcher configuration you can define a defaultGroup today. Any newly registered apps are added to that group automatically and become available to editors. Is there need to do anything else here? Can we close this item? czimmermann |