[NPMCLI-11] Decide whether to keep bootstrap and watchBootstrap in CLI Created: 10/May/16  Updated: 22/Aug/16  Resolved: 20/May/16

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 0.0.1

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to NPMCLI-10 Refactor initial code Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

This is a follow up to NPMCLI-10.
Basically we need to decide whether we want to keep on copying bootstrap, using less and watch for changes in css.
My take is that for the plain create-light-module we should only create ftl and yaml files w/o adding resources one might not want to use in an actual project or add them independently of our cli tool.
However, bootstrap and the watch css thing could be kept as an option to the jumpstart command for instance.



 Comments   
Comment by Federico Grilli [ 20/May/16 ]

After quick consultation between Jan and Tomas it was decided to remove buildBootstrap and watchBootstrap. Still we're copying bootstrap files when creating a light module

Generated at Mon Feb 12 04:45:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.