[NPMCLI-65] Help users to choose areas and pages for their component Created: 17/Jan/17 Updated: 24/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Robert Kowalski | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| 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: | |||||||||
| Story Points: | 21 | ||||||||
| Description |
|
mgnl create-component foo --available myHome@main -p /path/to/module creates a component for the user. As a user I would like to know which pages and which areas are available to me, so I can get started in a fast and efficent way. Philip suggested a REST API endpoint to list all available areas. A low tech solution could be to provide link to magnolia system / docs where default areas are listed or simple list an excerpt of default areas. |
| Comments |
| Comment by Christopher Zimmermann [ 09/Feb/17 ] |
|
Adding relevant comment from tgregovsky "Not sure how doable it is but autocompletion for definitions, at least these which existed on file system (in existing light module), plus maybe 'hardcoded' definitions from mtk. |