[NPMCLI-87] Help new users where to put light modules and how to create symlinks Created: 30/Jan/17 Updated: 30/Jan/17 |
|
| Status: | Open |
| Project: | Magnolia CLI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | 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 | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
Its hard for new users to figure out where they have to put their light modules to start development. The CLI should give hints where and how they have to put their light modules, so a new user isn't stuck and has to google it. |
| Comments |
| Comment by Robert Kowalski [ 30/Jan/17 ] |
|
czimmermann what do you think? |
| Comment by Robert Kowalski [ 30/Jan/17 ] |
|
We just chatted: the way to go should stay one magnolia instance per project. Using symlinks can be explained by mgnl to keep users on the happy path The sharing / trying out shared modules problem scope stays interesting, but should use the same semantics now. |