[NPMCLI-217] Allow creating an empty content app Created: 23/Apr/19 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
The current _default prototype variant of the create-app command adds a few sample model properties that the user of mgnl CLI may first have to delete from the content type definition before any further customization. This ticket asks for an introduction of an empty prototype, similar to what is already available for pages: mgnl create-page foo -P empty The user could then setup a minimalistic app using: mgnl create-app foo -P empty and instantly start adding model properties rather than deleting them first. Alternatively, the _default prototype could be the empty one, with the current one transformed into a new comprehensive one, where we could showcase many more property types.
|
| Comments |
| Comment by Christopher Zimmermann [ 24/Apr/19 ] |
|
Good idea. I would not do: "Alternatively, the _default prototype could be the empty one, with the current one transformed into a new comprehensive one, where we could showcase many more property types."
The CLI is so helpful for beginners because the created definitions just work - and show all key patterns. Its easier to delete, then to look up how to do something. |