[DOCU-673] Light development cans and can'ts Created: 10/Feb/16 Updated: 14/Mar/16 Resolved: 05/Mar/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Ruth Stocks |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: | |
| Sprint: | Docu Sprint 7 |
| Description |
|
List typical Magnolia project tasks and show which can and cannot be done with light development. The goal is to set the correct expectations. A developer should be able to make an educated decision whether light development is the right approach for them. Before you board the train you want to know how far it will go. Examples:
Light development is not just MTE + YAML. Light development is a modern development approach that doesn't require Java skills or even an IDE. You can't do everything but 80% is plenty. Beside the term Light development we also should have a section (or even a page?) explaining |
| Comments |
| Comment by Ruth Stocks [ 05/Mar/16 ] |
|
Documented at https://documentation.magnolia-cms.com/display/DOCS/Light+development+in+Magnolia |
| Comment by Christoph Meier [ 11/Mar/16 ] |
|
I was reviewing this page. (Just because we ususaly do that.) Generally i really like the page, it's good to have it. However, i'm gonna close ticket, and it's okday for me to keep it as it is. But again ... DOCS is not the place for roadmap (as far as i understand it). |
| Comment by Christopher Zimmermann [ 14/Mar/16 ] |
|
Christoph - good point. I think the key idea of that section is that it tells people what is not supported in Light modules. So that they know. |