[magnolia-dev] [JIRA] (NPMCLI-119) Multiple prototypes for creating pages and components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopening because the prototypes directory could get cluttered if people dont name things correctly. And if they do name things correctly - then they have to enter a long name to specify their prototype. create-component myComp -P component-empty To determine: Which option: 
 
Keep current directory structure, but user only has to enter -P empty and code interpolates the correct directory name. 
Add level of directories to prototypes directory components / pages. 
  
 

  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-119  
 
 
  Multiple prototypes for creating pages and components   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 
 
Assignee: 
 Robert Kowalski  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

  

[magnolia-dev] [JIRA] (NPMCLI-119) Multiple prototypes for creating pages and components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-119  
 
 
  Multiple prototypes for creating pages and components   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Fix Version/s: 
 2.2.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (JSMODELS-5) Way to get the data structure of an object - JS and NON-JS objects

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-5  
 
 
  Way to get the data structure of an object - JS and NON-JS objects   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Some way for a templater to output the structure and content of an object within a template for development purposes.Why: It  can be hard to work with content objects in a template because you do not know the structure of the content. It can be especially hard to understand the actual structure of the objects returned from _javascript_ models. Ideally a simple method in cmsfn would give a templater a string representation of the object.It 's difficult to work with the objects that are passed into the methods of a JS model from the templating script, because its hard to know the structure of the object. For example the object returned by cmsfn.children is an object of objects, so it cannot be iterated as a _javascript_ array.If you return an array from a model, then pass that array  Its not possible  to  another model function  use something like JSON . * It cannot be iterated with for(var item stringify  in  input) {* It cannot be iterated with or each (item in input){* it does not have  a  length  JS model . It would be useful if the developer could determine its structure.-Maybe there should be method which outputs a string representation of the data structure.  I tried using JSON.stringify, but it always returns undefined.http://codereview.stackexchange.com/questions/91184/java-json-stringifier-with-the-nashorn-apihttp://mail.openjdk.java.net/pipermail/nashorn-dev/2013-September/002012.html -  If there is an existing method in Java or JS that solves this problem, then we should simply document that. --- Implementation:  Dumper can be used to describe objects (for example in FTLs). User can choose how deep it should go in the object hierarchy when describing objects (using depth parameter) and if the output should in plain text or HTML formatted.   Example usage:{code}String result = Dumper.newBuilder().withDepth(3).withUseHtml(true).dump(myObject);{code}Users can also provide custom describers for certain object types by implementing {{AbstractDescriber}} class:{code}String result = Dumper.newBuilder().withAdditionalDescriber(myCustomDescriber).dump(object);{code}Describers for following types are provided out of the box:* Null* Scalars* Dates* Calendar* Arrays* Collections* Maps* ContentMaps* Nodes* Properties* Objects (this one describes only the object class to avoid generating huge hierarchies)* _javascript_ Objects (objects implementing JSObject interface)Node:{noformat}Node (/magnolia-travels/Vietnam--Tradition-and-Today)  author = "Magnolia Travels" (String)  body = "Vietnam is one of the worlds most exotic and culturally rich destinations. A gem..." (String)  body_de = "Vietnam ist eine der exotischsten und kulturreichsten Destinationen weltweit. Als Juwel unt..." (String)  description = "Discover the culture and everyday treasures of a rising phoenix" (String)  description_de = 

[magnolia-dev] [JIRA] (MGNLDEMO-217) Rest access to primary content for Superuser and anonymous users

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-217  
 
 
  Rest access to primary content for Superuser and anonymous users   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 12/Jun/17 6:09 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 To assist evaluators, particularly those interested in headless and frontend frameworks, it should be possible to retrieve the primary content via the default REST endpoints without any additional configurtion. For example - the samples on this page should work OOTB. https://documentation.magnolia-cms.com/display/DOCS/How+to+get+content+as+JSON+-+an+overview curl -H "Accept: application/json" http://localhost:8080/magnoliaAuthor/.rest/nodes/v1/tours/magnolia-travels/Kyoto Workspaces they should have read-only access to: dam website tours categories articles (possibly renamed to stories?) To determine - best way to configure the security. Maybe create a new ROLE, travel-demo-rest?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[magnolia-dev] [JIRA] (DOCU-1035) Document creating a custom REST endpoint

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1035  
 
 
  Document creating a custom REST endpoint   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 08/Jun/17 10:20 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Documentation page and tutorial, which would explain how to create a custom Java based endpoint.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 
  

[magnolia-dev] [JIRA] (DOCU-1035) Document creating a custom REST endpoint

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1035  
 
 
  Document creating a custom REST endpoint   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Documentation page and tutorial, which would explain how to create a custom Java based endpoint. Ideal would be to have the documentation page by July 1st when the Headless marketing motif starts, as this is a key component.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (JSMODELS-5) Way to get the data structure of an object - JS and NON-JS objects

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-5  
 
 
  Way to get the data structure of an object - JS and NON-JS objects   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Way to get the  JS  data structure of an  argument  object - JS and NON-JS objects  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (JSMODELS-6) Bad type when passing a returned js object to another js function

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-6  
 
 
  Bad type when passing a returned js object to another js function   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (JSMODELS-6) Bad type when passing a returned js object to another js function

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-6  
 
 
  Bad type when passing a returned js object to another js function   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 If you pass returned _javascript_ object (array, json) to the model, it's type gets changed and it does not behave as it should if you pass it again to another model function.To reproduce:# Return an JS array from a model function.# Pass the returned array to another model function. (Problem is not just with arrays though.) Result:* It cannot be iterated with for(var item in input) {* It cannot be iterated with or each (item in input){* it does not have a length.From Jaroslav:It's something related to freemarker template object wrapping, so fixing it might be a little bit tricky.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, 

[magnolia-dev] [JIRA] (JSMODELS-6) Bad type when passing a returned js object to another js function

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-6  
 
 
  Bad type when passing a returned js object to another js function   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jaroslav Simak  
 
 
Created: 
 17/May/17 12:44 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 If you pass returned _javascript_ object (array, json) to the model, it's type gets changed and it does not behave as it should if you pass it again to another model function. To reproduce: 
 
Return an JS array from a model function. 
Pass the returned array to another model function. 
 Result: 
 
It cannot be iterated with for(var item in input) { 
It cannot be iterated with or each (item in input){ 
it does not have a length. 
 From Jaroslav: It's something related to freemarker template object wrapping, so fixing it might be a little bit tricky.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[magnolia-dev] [JIRA] (JSMODELS-4) Provide samples of how to use JS models

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-4  
 
 
  Provide samples of how to use JS models   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Assignee: 
 Jaroslav Simak  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (JSMODELS-5) Way to get the JS data structure of an argument

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-5  
 
 
  Way to get the JS data structure of an argument   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jaroslav Simak  
 
 
Created: 
 16/May/17 4:28 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It's difficult to work with the objects that are passed into the methods of a JS model from the templating script, because its hard to know the structure of the object. For example the object returned by cmsfn.children is an object of objects, so it cannot be iterated as a _javascript_ array. If you return an array from a model, then pass that array to another model function. 
 
It cannot be iterated with for(var item in input) { 
It cannot be iterated with or each (item in input){ 
it does not have a length. 
 It would be useful if the developer could determine its structure. - Maybe there should be method which outputs a string representation of the data structure. I tried using JSON.stringify, but it always returns undefined. http://codereview.stackexchange.com/questions/91184/java-json-stringifier-with-the-nashorn-api http://mail.openjdk.java.net/pipermail/nashorn-dev/2013-September/002012.html - If there is an existing method in Java or JS that solves this problem, then we should simply document that.  
 

  
 
 
 
 

 
 
 

 
  

[magnolia-dev] [JIRA] (JSMODELS-4) Provide samples of how to use JS models

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia _javascript_ Models /  JSMODELS-4  
 
 
  Provide samples of how to use JS models   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jaroslav Simak  
 
 
Created: 
 16/May/17 4:12 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 We should provide samples of how to work with Magnolia FTL data-structures in JS models.  They can be tricky to work with because one needs to know the data structure that is passed in to a JS function from the FTL. Samples will help with this and give developers a good starting point. Samples can also help to illustrate possible use cases for the feature. (Initiative validation: https://wiki.magnolia-cms.com/display/PMTEAM/Template+model+LDV) Use cases to demonstrate: 
 
Keep templates simpler by moving logic into model. 
Processing the post of a frontend form. 
Communicating with Magnolia internals. 
Making a REST GET or POST 
 Probably the samples can best be delivered as one light module. I created a few samples while testing the feature that may be useful as a starting point: https://git.magnolia-cms.com/users/czimmermann/repos/js-model-samples/browse/light-modules/js-model-samples There are some notes here: https://wiki.magnolia-cms.com/display/PMTEAM/LD+Testing+-+JS+Models The samples should be documented with a README in the project, and should also be mentioned in Magnolia docs.  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (DOCU-1006) Overview "How to get json"

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1006  
 
 
  Overview "How to get json"
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 h4. TaskGive an overview about how to get {{json}} of (JCR based) content - showing all possible approaches:- Using the standard endpoints for nodes and properties- Using custom endpoints- freemarker based json-provider (typically using jsonfn, but all templating features are available.)- using jsonfnPlus providing hints , such as:- combining an ftl/template based json provider with virtual URI mappings to create a REST-full API- localize content / i18n: How to set the locale to get the content in the appropriate language- Same-origin policy issue & using CORS filter- Creating rest endpoints that deliver pure json, vs outputting required json directly in the page that uses it.- Using template variant to output json specifically for one component - then using DCR to access it. (Ask Schulte or Gregovsky)h4. Resources- [REST API|https://documentation.magnolia-cms.com/display/DOCS/REST+API]- [Accessing content on the client side|https://documentation.magnolia-cms.com/display/DOCS/Accessing+content+on+the+client+side]- [mgnl-conf 2016 workshop - dive into content pools with Magnolia|https://wiki.magnolia-cms.com/display/WIKI/mgnl-conf+2016+workshop+-+dive+into+content+pools+with+Magnolia]- [jsonfn|https://documentation.magnolia-cms.com/display/DOCS/jsonfn] Examples- https://github.com/magnolia-cms/angular-travel-demo- https://github.com/magnolia-cms/react-demos h4. Timing(!) According to [~czimmermann]  - this task should be finished before Q3 starts - e.g. must be finished before 1st of July.h4. Reason & AudienceMore and more people want to use frontend frameworks with a CMS or have other headless scenarios. for many this will be one of the first steps in evaluation. So the approaches should be clear  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[magnolia-dev] [JIRA] (DOCU-1006) Overview "How to get json"

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-1006  
 
 
  Overview "How to get json"
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 h4. TaskGive an overview about how to get {{json}} of (JCR based) content - showing all possible approaches:- Using the standard endpoints for nodes and properties- Using custom endpoints- freemarker based json-provider  (typically using jsonfn, but all templating features are available.) - using jsonfnPlus providing hints , such as:- combining an ftl/template based json provider with virtual URI mappings to create a REST-full API- localize content / i18n: How to set the locale to get the content in the appropriate language- Same-origin policy issue & using CORS filter - Creating rest endpoints that deliver pure json, vs outputting required json directly in the page that uses it.  - Using template variant to output json specifically for one component - then using DCR to access it. (Ask Schulte or Gregovsky) h4. Resources- [REST API|https://documentation.magnolia-cms.com/display/DOCS/REST+API]- [Accessing content on the client side|https://documentation.magnolia-cms.com/display/DOCS/Accessing+content+on+the+client+side]- [mgnl-conf 2016 workshop - dive into content pools with Magnolia|https://wiki.magnolia-cms.com/display/WIKI/mgnl-conf+2016+workshop+-+dive+into+content+pools+with+Magnolia]- [jsonfn|https://documentation.magnolia-cms.com/display/DOCS/jsonfn]h4. Timing(!) According to [~czimmermann]  - this task should be finished before Q3 starts - e.g. must be finished before 1st of July. h4. Reason & AudienceMore and more people want to use frontend frameworks with a CMS or have other headless scenarios. for many this will be one of the first steps in evaluation. So the approaches should be clear  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[magnolia-dev] [JIRA] (NPMCLI-130) Messages: mgnl create-page doesn't create a page but messages says it does

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-130  
 
 
  Messages: mgnl create-page doesn't create a page but messages says it does   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Messages: mgnl create-page doesn't create a page but messages says it does  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-129) jumpstart set relative path for magnolia.resources.dir

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-129  
 
 
  jumpstart set relative path for magnolia.resources.dir   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 jumpstart set relative path for  magnoila  magnolia .resources.dir  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-120) Jumpstart can download and use webapps instead of bundles

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-120  
 
 
  Jumpstart can download and use webapps instead of bundles   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Jumpstart should support grabbing a magnolia webapp and a tomcat and putting them together in a working setup that functions the same as a bundle.Reason:Magnolia provides more useful webapps than it provides bundles. For example: several of these webapps are more useful for starting actual projects than the bundles because they do not include demo projects.When starting a real project, a demo project often has to be removed which can be complicated.Info on existing bundles and webapps:https://documentation.magnolia-cms.com/display/DOCS/Bundles+and+webapps I guess that once we support webapps and getting the tomcat -  that we dont need to support the bundles anymore. -- - To specify - what the  command  options are : .  Possibility:  *Behaviour with no options*   {{mgnl jumpstart}} Default becomes: It prompts you on which version you want (empty, community, ee, eepro)With or without demo (y/n) Possible options *Options*  One could just specify the full webapp name, but this is very verbose. mgnl jumpstart - d  - webapp mgnl jumpstart - -bundle But the webapp names are long - is there a way that they can ask what webapps are available?One could specify which edition one wants, and whether you want the demo  (magnolia .mgnl jumpstart - community - edition  (with no demo  by default)mgnl jumpstart - webapp -edition  --demo (with demo included ) Can user ask which editions are available? Or is it listed by default in the help text? mgnl jumpstart - -listOr we could provide commands for the most common bundle/webapps?Possible optionsmgnl jumpstart - c --community-edition (magnolia-community-webapp)mgnl jumpstart -ee --enterprise-edition-standard (magnolia‑enterprise‑standard‑webapp)mgnl jumpstart -eepro --enterprise-edition-pro (magnolia‑enterprise‑standard‑webapp)mgnl jumpstart -em --empty (magnolia-empty-webapp) OrCombinations: mgnl jumpstart - np - edition  (This is elegant now  -  but hard to use plusmgnl jumpstart  -  which values do you use there?) n --now   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[magnolia-dev] [JIRA] (NPMCLI-129) jumpstart set relative path for magnoila.resources.dir

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-129  
 
 
  jumpstart set relative path for magnoila.resources.dir   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 04/Apr/17 4:34 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Currently the jumpstart sets an absolute path in magnolia.properties for magnolia.resources.dir. This then causes problems if the whole directory (containing the tomcat and the light-modules) is moved somewhere else. The link to light-modules will be wrong. So lets use a relative path instead.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
   

[magnolia-dev] [JIRA] (NPMCLI-125) Improve search texts

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-125  
 
 
  Improve search texts   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Mar/17 5:16 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Update texts:  From: "search a light module." To: "search for a light module on npm." From: "Searches light modules with given query." To: "Search for light modules on the npm repository with the provided query. Query can contain multiple terms separated with commas and no spaces. When no query is provided, returns a list of all light modules."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
   

[magnolia-dev] [JIRA] (DOCU-979) Update Mag Frontend Development section

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-979  
 
 
  Update Mag Frontend Development section   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Update section to match the latest CLI version, and ensure smoothest possible hour-1 learning experience. * Motivation * With our booth at the React London conference, our main "call to action" for visitors will be to get devs to "try it in 1 hour" by visiting the new frontend section with this handy link http://magnolia-cms.com/start-ld * Details * On On https://documentation.magnolia-cms.com/display/DOCS/Install+Magnolia*Change message to make sure user experience matches the CLI*Change: If you already installed Magnolia CLI and want to update to the latest stable version, use:To: If you already installed Magnolia CLI, update to the latest version:*Update help output*{{mgnl help}} has different output now.*Update the  jumpstart output* to:info Magnolia has been successfully setup for light development!info You can now open a new terminal tab or window and start it up with the CLI command 'mgnl start'info Magnolia will be ready after a few seconds at localhost:8080/magnoliaAuthor. Username and password is superuser*Simplify Start*Start Magnolia section can be very reduced because of introduction of {{mgnl start}} command.* Remove tip bullet: "Remember the path to the bin directory."* Remove all the details under "Start Magnolia", because not necessary anymore. * Add "Execute the Magnolia CLI start command:" {{mgnl start}}* Add "On the first start, Magnolia will run the "web update" and automatically install all modules."*Update "Install Magnolia" section*Just remove the whole section - they can go straight to the Login step.*Remove or simplify tip about "light modules" directory.*Suggestion "The jumpstart command automatically creates a light-modules directory for you. If you already have a different directory that you want to use for light modules, edit the magnolia.resources.dir property in your magnolia.properties file to point to it." On: https://documentation.magnolia-cms.com/display/DOCS/Hello+Magnolia+for+front-end+developers*Conclusion*There should be a bit more of a concrete end. They have finished the intro section and the tutorial, and now understand the basics and could create their own componnts. Right before the "Go further" section.Suggestion:CongratulationsYou have finished the "Get Started" section for front end developers, and have learned the key Magnolia concepts.*Go Further*Add two bullet point to the top:Hello Magnolia - A step by step walkthrough of creating the Hello Magnolia light module.CLI Overview - Watch the CLI Video to learn how to quickly create modules, and page and component templates  
 

  
 
 
 
 
  

[magnolia-dev] [JIRA] (DOCU-979) Update Mag Frontend Development section

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-979  
 
 
  Update Mag Frontend Development section   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Update section to match the latest CLI version, and ensure smoothest possible hour-1 learning experience. Details as sub-tasks. MotivationWith our booth at the React London conference, our main "call to action" for visitors will be to get devs to "try it in 1 hour" by visiting the new frontend section with this handy link http://magnolia-cms.com/start-ld DetailsOn On https://documentation.magnolia-cms.com/display/DOCS/Install+Magnolia*Change message to make sure user experience matches the CLI*Change: If you already installed Magnolia CLI and want to update to the latest stable version, use:To: If you already installed Magnolia CLI, update to the latest version:*Update help output*{{mgnl help}} has different output now.*Update the  jumpstart output* to:info Magnolia has been successfully setup for light development!info You can now open a new terminal tab or window and start it up with the CLI command 'mgnl start'info Magnolia will be ready after a few seconds at localhost:8080/magnoliaAuthor. Username and password is superuser*Simplify Start*Start Magnolia section can be very reduced because of introduction of {{mgnl start}} command.* Remove tip bullet: "Remember the path to the bin directory."* Remove all the details under "Start Magnolia", because not necessary anymore. * Add "Execute the Magnolia CLI start command:" {{mgnl start}}* Add "On the first start, Magnolia will run the "web update" and automatically install all modules."*Update "Install Magnolia" section*Just remove the whole section - they can go straight to the Login step.*Remove or simplify tip about "light modules" directory.*Suggestion "The jumpstart command automatically creates a light-modules directory for you. If you already have a different directory that you want to use for light modules, edit the magnolia.resources.dir property in your magnolia.properties file to point to it."  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[magnolia-dev] [JIRA] (DOCU-979) Update Mag Frontend Development section

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-979  
 
 
  Update Mag Frontend Development section   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Mar/17 10:21 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Update section to match the latest CLI version, and ensure smoothest possible hour-1 learning experience. Details as sub-tasks. Motivation With our booth at the React London conference, our main "call to action" for visitors will be to get devs to "try it in 1 hour" by visiting the new frontend section with this handy link http://magnolia-cms.com/start-ld  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
   

[magnolia-dev] [JIRA] (NPMCLI-120) Jumpstart can download and use webapps instead of bundles

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-120  
 
 
  Jumpstart can download and use webapps instead of bundles   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Jumpstart should support grabbing a magnolia webapp and a tomcat and putting them together in a working setup that functions the same as a bundle.Reason: Magnolia provides more useful webapps than it provides bundles.  Several  For example: several  of these webapps are more useful for starting actual projects than the bundles because they do not include demo projects.  When starting a real project, a demo project often has to be removed which can be complicated. Jumpstart should support grabbing a magnolia webapp Info on existing bundles  and  a tomcat and putting them together in a working setup that functions the same as a bundle  webapps:https://documentation . magnolia-cms.com/display/DOCS/Bundles+and+webapps   ---  To specify - what the options are:Possibility: {{mgnl jumpstart}} Default becomes: It prompts you on which version you want (empty, community, ee, eepro)With or without demo (y/n) mgnl jumpstart Possible options mgnl jumpstart -d --demo (magnolia-community-demo-webapp)mgnl jumpstart -c --community-edition (magnolia-community-webapp)mgnl jumpstart -ee --enterprise-edition-standard (magnolia‑enterprise‑standard‑webapp)mgnl jumpstart -eepro --enterprise-edition-pro (magnolia‑enterprise‑standard‑webapp)mgnl jumpstart -em --empty (magnolia-empty-webapp)OrCombinations:mgnl jumpstart --edition   (This is elegant - but hard to use - which values do you use there?)  Info on existing bundles and webapps:https://documentation.magnolia-cms.com/display/DOCS/Bundles+and+webapps  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[magnolia-dev] [JIRA] (NPMCLI-120) Jumpstart can download and use webapps instead of bundles

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-120  
 
 
  Jumpstart can download and use webapps instead of bundles   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 20/Mar/17 10:49 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Magnolia provides more useful webapps than it provides bundles. Several of these webapps are more useful for starting actual projects than the bundles because they do not include demo projects. When starting a real project, a demo project often has to be removed which can be complicated. Jumpstart should support grabbing a magnolia webapp and a tomcat and putting them together in a working setup that functions the same as a bundle. — To specify - what the options are: Possibility: Default becomes:  It prompts you on which version you want (empty, community, ee, eepro) With or without demo (y/n) mgnl jumpstart mgnl jumpstart -d --demo (magnolia-community-demo-webapp) mgnl jumpstart -c --community-edition (magnolia-community-webapp) mgnl jumpstart -ee --enterprise-edition-standard (magnolia‑enterprise‑standard‑webapp) mgnl jumpstart -eepro --enterprise-edition-pro (magnolia‑enterprise‑standard‑webapp) mgnl jumpstart -em --empty (magnolia-empty-webapp) Or Combinations: mgnl jumpstart --edition  Info on existing bundles and webapps: https://documentation.magnolia-cms.com/display/DOCS/Bundles+and+webapps  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
  

[magnolia-dev] [JIRA] (MTE-71) Simple MTK template demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-71  
 
 
  Simple MTK template demo
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-specify  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MTE-71) Simple MTK template demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-71  
 
 
  Simple MTK template demo
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 There should be a demo for MTK  module shall contain sample bootstraps  which demonstrate typical use cases for each page and component template included in the kit. The main page should have a single instance of each component.Where necessary, a sub A  pages exists for each component to demonstrate alternative usages. For example a video subpage should show at least these permutations: asset+ fullwidth, asset+fixedwidth, embed+fullwidth, embed+fixedwidth, plus versions which include captions and not, etc.Consider that  these samples will  this demo could  eventually used for integration tests. This ticket could have subtasks for each component.This ticket could be split into multiple tickets.Samples should be included in MTK module via sample bootstraps. For now these will not be installed by the light module version - as it is not supported by light modules, but will be included in the maven version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

[magnolia-dev] [JIRA] (NPMCLI-119) Multiple prototypes for creating pages and components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-119  
 
 
  Multiple prototypes for creating pages and components   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Option to define multiple 'prototypes' (currently there is one for page and one for component) and then be able to create new page or component from (optionally) given template. still use default one if there is no attribute.Current default component template with 5-6 most used fields is super useful, but sometimes I am missing option to create empty component without dialog. simply just component definition and empty ftl...maybe command like:mgnl create-component something --prototype emptyTo specify:Exact syntax. Note - eventually it would also be nice to have a prototype for light-modules, but that can come later.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: 

[magnolia-dev] [JIRA] (NPMCLI-119) Multiple prototypes for creating pages and components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-119  
 
 
  Multiple prototypes for creating pages and components   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 17/Mar/17 8:05 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Option to define multiple 'prototypes' (currently there is one for page and one for component) and then be able to create new page or component from (optionally) given template. still use default one if there is no attribute. Current default component template with 5-6 most used fields is super useful, but sometimes I am missing option to create empty component without dialog. simply just component definition and empty ftl... maybe command like: mgnl create-component something --prototype empty To specify: Exact syntax.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[magnolia-dev] [JIRA] (NPMCLI-119) Multiple prototypes for creating pages and components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-119  
 
 
  Multiple prototypes for creating pages and components   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-specify  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-97) Copy command

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy command   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Command to copy  entities.{{mgnl copy}}Features:* Copy  light module including changing all old references  (within the module)  in yaml  and ,  ftl , i18n  files from original module name to new one. mgnl copy-light-module * Copy component (copies template definition, ftl, dialog definition)  Not sure what the arguments would be * Copy page template .  To specify.  (copies template definition, ftl, dialog definition)   This would be a helpful timesaver. In designing the command UX, consider that it could be useful To specify:* Command syntax.* How  to  copy other  reference  things  as well  not in the immediate directory2 ideas* Specify type: copy light  -  like module oldname newname, copy  component  templates and pages.  oldname newname* Do not specify type: copy oldname newname  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (NPMCLI-97) Copy command

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy command   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Copy  light module  command  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-98) Get a light-module package from npm repository

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-98  
 
 
  Get a light-module package from npm repository   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Provide a command to get  one package  packages  by supplying  its name  their names as arguments . Maybe  {{mgnl  get  install  [package -  name -1 package-name-2 ]}} The name {{install}} connotates that it will be ready to use (as in the npm command), so it should attempt to install them to the current magnolia.resources.dir.If successful it should output where it installed the module.It should offer an option to install to the current location with --here or -h.* Rationale * Magnolia is promoting npm as the place to share light-modules. It should be easy and clean to get those modules. There are other more sophisticated approaches - such as via the "build" command. But there should be a way to just  easily  get a specific  module  modules .The  {{  npm install }}  command does this, but has the downside of downloading it into a node_modules directory, this is clunky and could be confusing. Additional notes and rationale:https://wiki.magnolia-cms.com/display/PMTEAM/Getting+LM+packages+from+npm  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
  

[magnolia-dev] [JIRA] (NPMCLI-98) Get a light-module package from npm repository

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-98  
 
 
  Get a light-module package from npm repository   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Provide a command to get packages by supplying their names as arguments.{{mgnl install [package-name-1 package-name-2]}}The name {{install}} connotates that it will be ready to use (as in the npm command), so it should attempt to install them to the current magnolia.resources.dir.If successful it should output where it installed the module.It should offer an option to install to the current location  or another location,  with -- here or -h path .*Rationale*Magnolia is promoting npm as the place to share light-modules. It should be easy and clean to get those modules. There are other more sophisticated approaches - such as via the "build" command. But there should be a way to just easily get a specific modules.The {{npm install}} command does this, but has the downside of downloading it into a node_modules directory, this is clunky and could be confusing.Additional notes and rationale:https://wiki.magnolia-cms.com/display/PMTEAM/Getting+LM+packages+from+npm  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 
   

[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-99  
 
 
  Search for magnolia light-module packages on npm   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-98) Get a light-module package from npm repository

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-98  
 
 
  Get a light-module package from npm repository   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-109) Best practice or command to process local light module build

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-109  
 
 
  Best practice or command to process local light module build   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Feb/17 11:45 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Based on other work we recommend the source control project for a sharable light module to be buildable with 'npm run build'. Additionally we recommend using .npmignore to remove all of the files not required for the production light module - such as the _dev directory and various config files. This works great for packages a developer gets directly from npm - but how should a developer work which has the source control project locally - how can they easily get their built version without the dev specific files. Of course they can run 'npm run build' locally - but how to get rid of the .npmignore files? They could build the tar.gzip locally and then unpack that.  Is there something more handy? could we provide a CLI command to do this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[magnolia-dev] [JIRA] (NPMCLI-97) Copy light module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy light module   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-specify  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-97) Copy light module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy light module   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Command to copy light module including changing all old references in yaml and ftl files from original module name to new one.mgnl copy-light-moduleNot sure what the arguments would be. To specify. This would be a helpful timesaver.In designing the command  api  UX , consider that it could be useful to copy other things as well - like component templates and pages.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-97) Copy light module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy light module   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Command to copy light module including changing all old references in yaml and ftl files from original module name to new one.mgnl copy-light-moduleNot sure what the arguments would be. To specify. This would be a helpful timesaver. In designing the command api, consider that it could be useful to copy other things as well - like component templates and pages.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-100) Existing magnolia.zip lets jumpstart ignore -m and -e option

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-100  
 
 
  Existing magnolia.zip lets jumpstart ignore -m and -e option   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-specify  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-108) Improve README prototype to make modules easier to understand

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-108  
 
 
  Improve README prototype to make modules easier to understand   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 23/Feb/17 12:00 PM  
 
 
Fix Versions: 
 2.0  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 The readme should include some comments and more suggestions in order to guide devs to make more useful and consistant readme files. In particular this will encourage better reuse and sharing of modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (NPMCLI-107) tab-completion should give success message stating where it has been installed.

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-107  
 
 
  tab-completion should give success message stating where it has been installed.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 21/Feb/17 1:21 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 tab-completion command should give success message stating where it has been installed. Also ensure that the help message is accurate. "install tab autocomplete feature for Bash, zsh or PowerShell"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

[magnolia-dev] [JIRA] (MTE-71) Simple MTK template demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This will be very helpful for newcomers to Magnolia. Travel demo has a different purpose and does not offer clear overview of MTK. I have a draft version produced. For me the main outstanding question is how it should be delivered - I'm leaning towards another node at the root of the website tree.  
 

  
 
 
 
 

 
 Magnolia Templating Essentials /  MTE-71  
 
 
  Simple MTK template demo
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Resolution: 
 Won't Do  
 
 
Status: 
 Closed Reopened  
 
 
Assignee: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 
   

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from other npm packages in one module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from other npm packages in one module   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It should be easy to setup a  single  light module so that it uses web resources from other npm packages. For example if I want to create a light module which provides a component which provides a carousel based on "slick-carousel" (https://www.npmjs.com/package/slick-carousel), my new component should not need to copy and include the web resources of this other module - it should be able to simply depend on this other package, and somehow specify which of its resources it needs.Reasoning:A key benefit and principle of npm, is that a package can depend on others so that it does not duplicate what is already available elsewhere. If we do not adhere to this principle, developers will be confused and dissapointed.Example of a light module that could use this: https://www.npmjs.com/package/responsive-image-componentIt includes the lazySizes.js file - but it should not. It should simply depend on the lazy-sizes npm package.(https://www.npmjs.com/package/lazysizes)Background: Previously this was solved with the lightDevCopyResources configuration - but that has issues now that mgnl is installed globally. See linked ticket.Note:resfn (available since Magnoila 5.5.1) makes it easy for a template to include resources in the light modules. It may be part of the solution here, but by itself it does not address the issue of resources from other npm packages. *Conclusion:*Use standard frontend build tool such as webpack to bundle dependent resources and place them in webresources.This is done with pre-publish hook so that the npm package has all resources necessary - ready to go.We provide advice on which common large libraries should rather not be automatically bundled in the interest of saving space (but the downside of additional complexity for consumer of package.) (We are not talking about the project here.)If that is too complicated, users can grab the dependency manually.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from other npm packages in one module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from other npm packages in one module   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Use resources from other npm packages  in one module  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-104) Open browser once server is started with start command

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-104  
 
 
  Open browser once server is started with start command   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 14/Feb/17 1:40 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 When user uses "mgnl start" once the magnolia server is fulling running - a browser should be opened with the proper url. This will help a developer get started and is convenient. Some CLI's automatically open a browser with the correct URL once the server has started.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 

[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-99  
 
 
  Search for magnolia light-module packages on npm   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Provide a command to search for light-module packages on npm.The search should only return packages which have the keyword "magnolia-light-module".{{mgnl search [search fragment ] }}*Rationale*Magnolia is promoting npm as the place to share light-modules. It should be easy to find packages on npm that are relevant  based on a search term.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-99) Search for magnolia light-module packages on npm

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-99  
 
 
  Search for magnolia light-module packages on npm   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 09/Feb/17 4:03 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Provide a command to search for light-module packages on npm. The search should only return packages which have the keyword "magnolia-light-module". mgnl search [search fragment Rationale Magnolia is promoting npm as the place to share light-modules. It should be easy to find packages on npm that are relevant based on a search term.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  

[magnolia-dev] [JIRA] (NPMCLI-98) Get a light-module package from npm repository

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-98  
 
 
  Get a light-module package from npm repository   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 09/Feb/17 3:57 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Provide a command to get one package by supplying its name. Maybe mgnl get [package name] Rationale Magnolia is promoting npm as the place to share light-modules. It should be easy and clean to get those modules. There are other more sophisticated approaches - such as via the "build" command. But there should be a way to just get a specific module. The npm install command does this, but has the downside of downloading it into a node_modules directory, this is clunky and could be confusing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

   

[magnolia-dev] [JIRA] (NPMCLI-97) Copy light module

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-97  
 
 
  Copy light module   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 09/Feb/17 2:51 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Command to copy light module including changing all old references in yaml and ftl files from original module name to new one. mgnl copy-light-module Not sure what the arguments would be. To specify.  This would be a helpful timesaver.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 The [handle prefix|https://demopublic.magnolia-cms.com/.magnolia/admincentral#app:site:browser;/travel/mappings/website@handlePrefix:null:] can't contain the {{/travel}} prefix if the domain is correctly configured since  MAGNOLIA-6882. Not sure if we want to fix it generally in the demo itself or just for https://demopublic.magnolia-cms.com. h4. Suggested solutionFix seems to be relatively easy: adjust VirtualURIMapping in tours module.{{toUri=forward:/tour?tour=$1}}Basically removing the site-suffix from the {{toUri}}!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To 

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Fix Version/s: 
 1.1.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-61) Jumpstart should allow getting bundle without travel demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-61  
 
 
  Jumpstart should allow getting bundle without travel demo   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-95) Help users with outdated Node versions

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-95  
 
 
  Help users with outdated Node versions   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Fix Version/s: 
 1.0.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-775) Symlinks can be used in magnolia.resources.dir

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-775  
 
 
  Symlinks can be used in magnolia.resources.dir   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It would be good to mention that one can use symlinks to link to other directories from the magnolia.resources.dir where the light modules are.This question comes up naturally because it is a common scenario that I may have one module that I want to use on multiple projects. A developer or company may have a library of modules that they reuse on different projects. So it would be convenient to just create symlinks from the light modules directory to that module.And we have specifically recieved this question a few times at conference or via forums.Maybe on this include https://documentation.magnolia-cms.com/display/DOCS/_What+is+magnolia.resources.dir  ( Note: I  wonder if there is an equivalent  have confirmed that symlinks work  on windows ? shortcuts?)  Vista and greater.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   

[magnolia-dev] [JIRA] (NPMCLI-90) start command option for --ignore-open-files-limit

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-90  
 
 
  start command option for --ignore-open-files-limit   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Fix Version/s: 
 1.0.8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-90) start command option for --ignore-open-files-limit

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-90  
 
 
  start command option for --ignore-open-files-limit   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 31/Jan/17 11:22 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 The start command should accept an argument to ignore the open files limit. The argument should be short or provide a one letter alias. For consistency, using the same "--ignore-open-files-limit" option as magnolia accepts would be a good choice. A possible alias would be "-i". This feature is important for demos, testing, workshops where it can be cumbersome to actually raise the open file limit on the system.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[magnolia-dev] [JIRA] (NPMCLI-81) Identify best practice for files not used by magnolia

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-81  
 
 
  Identify best practice for files not used by magnolia   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 26/Jan/17 5:27 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 There are several instances of files that are related to a light module, that are not directly used by magnolia. Where should they be stored? How should these files be handled?  While we must preserve the freedom for developers to handle the files however they want - we should provide a convention so that light modules can be easily shared, understood, and used. To keep in mind is both the case of companies developing a library of modules for in-house use, and in particular of developers sharing components in places like github and npm. Some questions: 
 
Should all the files be stored in the light module? Or should some of the files be stored in a separate location? 
Where should tests be stored? 
Where are examples stored? 
Where are files to be processed - like less, sass, ES6, TS stored? 
If all the files are in the light module - should something be done to remove them when using them in production - for security, tidiness, and to minimize resource consumption of the file watcher? 
  
 

  
 
 
 
 

 
 
 
   

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from other npm packages

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from other npm packages   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Use resources from  other  npm packages  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-80) CLI: Resource handling

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-80  
 
 
  CLI: Resource handling   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 26/Jan/17 3:13 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Establish, document and support best practices for handling web resources in Light modules and with the CLI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   

[magnolia-dev] [JIRA] (NPMCLI-63) CLI: Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  CLI: Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Epic Colour: 
 ghx-label- 9 6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) CLI: Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  CLI: Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Epic Name: 
 CLI: Help users get started  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) CLI: Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  CLI: Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 CLI: Help users get started  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Epic Colour: 
 ghx-label-9  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Epic Name: 
 Help users get started  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Right now the focus for the CLI is to get Help  (new) users, often with frontend focus,  get  be  successful and  get  excited about magnolia and the possibilities it provides.  Currently the focus is not the "admin user" which needs for example help and tooling to maintain running magnolia instances. Successful and happy users are important. A frictionless setup for completely new users helps to set them up for success. Attention spans are short and frustration often leads to aborted evaluation of new technology.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-63) Help users get started

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-63  
 
 
  Help users get started   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Better instructions for Help  users  to  get started  and succcessful  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-79) Light Project support

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-79  
 
 
  Light Project support   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 25/Jan/17 2:37 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Help developers working on a web project based on light modules: a "Light Project". Document best practices, provide examples, and integrate support for these in the CLI. We already provide support for light modules, but some things need to be handled specifically at the project level. Key things to address: 
 
Getting and using web resources that are in 3rd party npm packages. 
Project level web esource processing - less, sass, concatonation, minification, js transpilation, sprite processing, etc. Especially on the project level, for example bundling css and js into site.js and site.js. (Gulp/grunt/webpack tasks) 
Project structure 
Project-level configuration 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[magnolia-dev] [JIRA] (NPMCLI-71) LESS and SASS: Identify best practices

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-71  
 
 
  LESS and SASS: Identify best practices   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Identify LESS  and  document  SASS: Identify  best practices  for light-module developers  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-72) Research and document how users can test their modules

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-72  
 
 
  Research and document how users can test their modules   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Investigate and document how you can test light-modules, in a variety of contexts:* Ones managed with maven, as it has a nice functionality to run multiple Node and npm versions.* Ones not managed by maven - as light-modules are commonly developed by frontend developers with no maven installed.* For light-modules shared on  github &  npm. A few questions:* What should be tested?* How will users create tests?* How difficult are the tests to maintain? * How can the CLI support this?   Rationale:Tests ensure quality.Tests demonstrate quality of projects on npm and github, and facilitate forking and innovation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

[magnolia-dev] [JIRA] (NPMCLI-72) Document how users can test their modules

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-72  
 
 
  Document how users can test their modules   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 One idea from the discussions is Investigate and document  how you can test light-modules,  especially the ones  in a variety of contexts:* Ones  managed with maven, as it has a nice functionality to run multiple Node and npm versions. * Ones not managed by maven - as light-modules are commonly developed by frontend developers with no maven installed.* For light-modules shared on npm. A few questions:* What should be tested?* How will users create tests?* How difficult are the tests to maintain?Rationale:Tests ensure quality.Tests demonstrate quality of projects on npm and github, and facilitate forking and innovation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html

[magnolia-dev] [JIRA] (NPMCLI-72) Research and document how users can test their modules

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-72  
 
 
  Research and document how users can test their modules   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Document Research and document  how users can test their modules  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-72) Document how users can test their modules

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-72  
 
 
  Document how users can test their modules   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Investigate Document  how users can test their modules  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-72) Investigate how users can test their modules

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-72  
 
 
  Investigate how users can test their modules   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Document Investigate  how users can test their modules  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from npm packages

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from npm packages   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It should be easy to setup a light module so that it uses web resources from other npm packages. For example if I want to create a light module which provides a component which provides a carousel based on "slick-carousel" (https://www.npmjs.com/package/slick-carousel), my new component should not need to copy and include the web resources of this other module - it should be able to simply depend on this other package, and somehow specify which of its resources it needs.Reasoning:  A key benefit and principle of npm, is that a package can depend on others so that it does not duplicate what is already available elsewhere.If we do not adhere to this principle, developers will be confused and dissapointed.   Example of a light module that could use this: https://www.npmjs.com/package/responsive-image-componentIt includes the lazySizes.js file - but it should not. It should simply depend on the lazy-sizes npm package.(https://www.npmjs.com/package/lazysizes)Background: Previously this was solved with the lightDevCopyResources configuration - but that has issues now that mgnl is installed globally. See linked ticket. Note:resfn (available since Magnoila 5.5.1) makes it easy for a template to include resources in the light modules. It may be part of the solution here, but by itself it does not address the issue of resources from other npm packages.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from npm packages

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from npm packages   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 There It  should be  easy to setup  a  mechanism for a  light  module  to easily provide its  so that it uses  web resources  to the pages  from other npm packages .With package For example if I want to create a light module which provides a component which provides a carousel based on "slick-carousel" (https://www . json npmjs.com/package/slick-carousel) ,  modules can have dependencies  my new component should not need  to  libraries like jquery, etc. It will be useful if  copy and include  the  CLI can assist with making these  web  resources  available automatically  of this other module - it should be able to simply depend on this other package ,  so  and somehow specify which of its resources it needs.Reasoning:A key benefit and principle of npm, is that  a  user  package can depend on others so that it does not duplicate what is already available elsewhere. Example  of a light module  can  that could  use  this: https://www.npmjs.com/package/responsive-image-componentIt includes  the  components  lazySizes.js file - but  it  provides with no or minimal configuration  should not .  It should simply depend on the lazy-sizes npm package.  (https://www.npmjs.com/package/lazysizes)  Background:  Previously this was solved with the lightDevCopyResources configuration - but that has issues now that mgnl is installed globally. See linked ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[magnolia-dev] [JIRA] (NPMCLI-38) Use resources from npm packages

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-38  
 
 
  Use resources from npm packages   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Summary: 
 Simple way for module to include required Use  resources  in page  from npm packages  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-61) Jumpstart should allow getting bundle without travel demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-61  
 
 
  Jumpstart should allow getting bundle without travel demo   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 A Dev should be able to use the CLI to start a real project.The travel demo will not be part of a real project.The Travel demo is hard to remove from the bundle.One solution would be to simply add download ability of bundles without demo.Another usecase is a partner that wants to get their developers up to speed with their own demo and perhaps their own templating kit. With the downloadJars feature, and the contentImporter they could get close to this - but the installed demo gets in the way.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (DOCU-928) Tip for developers that YAML include files should not have spaces at the front of the line

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-928  
 
 
  Tip for developers that YAML include files should not have spaces at the front of the line   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 24/Jan/17 5:23 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 A common pitfall for YAML include files is that they do not work because the lines have too many spaces in front of the first line. This is a micro "perfect storm" 1. Developers are not used to indentation being so important. 2. If you copy some lines out of an existing YAML defintion into a new file - unless you take care of it you will have some spaces (indentation) at the beginning of the lines. Therefore please provide a tip of some kind that the first line in an include file should not have any indentation. Or a note that this could be the problem if their include file is not working.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[magnolia-dev] [JIRA] (NPMCLI-58) Easy start, stop, and logging of Magnolia

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-58  
 
 
  Easy start, stop, and logging of Magnolia   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-76) investigate how newcomers can easily overcome the open files issue

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-76  
 
 
  investigate how newcomers can easily overcome the open files issue   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 blocked  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLCE-60) Remove "too many open files" startup check - if possible thanks to H2

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopening based on conversation with Ilgun and Maxime.  Please perform an additional test with EEPro bundle and monitor the number of opened files on the system during install and startup.  Additionally, add a large number of YAML definitions to the resources directory at the same time (for example the corporate website) and monitor the open files during this process. Based on an evaluation of these values we'll decide whether to remove the startup check.  
 

  
 
 
 
 

 
 Magnolia Community Edition /  MGNLCE-60  
 
 
  Remove "too many open files" startup check - if possible thanks to H2   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Resolution: 
 Won't Fix  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  

[magnolia-dev] [JIRA] (NPMCLI-74) Incorrect pattern in resfn call in page template

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-74  
 
 
  Incorrect pattern in resfn call in page template   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-74) Incorrect pattern in resfn call in page template

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-74  
 
 
  Incorrect pattern in resfn call in page template   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 18/Jan/17 12:02 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 In mgnl-cli-prototypes/page/template.ftl the resfn pattern is incorrect. The last . would either need to be escaped or removed. Recommend removing the last dot to keep the pattern as simple as possible. So the patterns should be: 

 

[#-- ${resfn.css(["__lightDevModuleFolder__/.*css"])!} --]
[#-- ${resfn.js(["__lightDevModuleFolder__/.*js"])!} --]
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
 

[magnolia-dev] [JIRA] (NPMCLI-74) Incorrect pattern in resfn call in page template

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-74  
 
 
  Incorrect pattern in resfn call in page template   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 quickwin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLDEMO-204) Links to tours don't work if you access demo over a correctly configured domain

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-204  
 
 
  Links to tours don't work if you access demo over a correctly configured domain   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Priority: 
 Neutral Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLDEMO-202) Move tour "The Baikal experience" from Europe to Asia

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia Demo Projects /  MGNLDEMO-202  
 
 
  Move tour "The Baikal experience" from Europe to Asia   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-61) Jumpstart should allow getting bundle without travel demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-61  
 
 
  Jumpstart should allow getting bundle without travel demo   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 12/Jan/17 11:50 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 A Dev should be able to use the CLI to start a real project. The travel demo will not be part of a real project. The Travel demo is hard to remove from the bundle. One solution would be to simply add download ability of bundles without demo.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 
  

[magnolia-dev] [JIRA] (MGNLRESTCL-22) Context attribute is not installed during installation

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-22  
 
 
  Context attribute is not installed during installation   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 to-estimate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLUI-4084) Tree scroll position is not properly maintained in Firefox

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia UI /  MGNLUI-4084  
 
 
  Tree scroll position is not properly maintained in Firefox   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 
 
Labels: 
 chrome firefox scroll  to-estimate  tree  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (SUGGEST-67) Templates with prepopulated content

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-67  
 
 
  Templates with prepopulated content   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It would save time and be helpful for our editors if a template could have some default content when an editor instantiates it. Probably inspired by modern css-frameworks like bootstraps, there is a trend to provide more generic page templates and component templates, such as a "row" layout component. The benefit is that the editors have great flexibility.The new need is to be able to populate a flexible page template with some columns, and other placeholder content, such as textimage, carousel, or list components - and save this as a new template. For example as "Section Page" template.This would be useful for component templates too. A row component could be prepopulated with a certain logo image on the left side and three teasers on the right side, for example. This new entitiy could then be saved as a new component template.Editors could then re-use this anywhere. Possibly editors could create these in the page editor with an additional action "Add User Template". Note: the suggestion was made with the idea that the content would simply be copied. Its like a set of prepopulated templates to let editors move faster and adhere to some standards.However a related improvement is that these new populated components could be saved in a new app - and that the content is stored once in this app. So editing the one instance edits them all. (Like the "teaser app" concept.)  Source: This was requested at the 2016 unconference. *Reporter*: Topher*E-mail*: [mailto:christopher.zimmerm...@magnolia-cms.com]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
   

[magnolia-dev] [JIRA] (SUGGEST-67) Templates with prepopulated content

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Suggestion Box /  SUGGEST-67  
 
 
  Templates with prepopulated content   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 03/Jan/17 8:48 AM  
 
 
Environment: 

 
 
Labels: 
 collector-0cf1239d  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It would save time and be helpful for our editors if a template could have some default content when an editor instantiates it.  Probably inspired by modern css-frameworks like bootstraps, there is a trend to provide more generic page templates and component templates, such as a "row" layout component. The benefit is that the editors have great flexibility. The new need is to be able to populate a flexible page template with some columns, and other placeholder content, such as textimage, carousel, or list components - and save this as a new template. For example as "Section Page" template. This would be useful for component templates too. A row component could be prepopulated with a certain logo image on the left side and three teasers on the right side, for example. This new entitiy could then be saved as a new component template. Editors could then re-use this anywhere. Note: the suggestion was made with the idea that the content would simply be copied. Its like a set of prepopulated templates to let editors move faster and adhere to some standards. However a related improvement is that these new populated components could be saved in a new app - and that the content is stored once in this app. So editing the one instance edits them all. (Like the "teaser app" concept.) Source: This was requested at the 2016 unconference.  Reporter: Topher E-mail: christopher.zimmerm...@magnolia-cms.com  
 

  
 
 
 
 
  

[magnolia-dev] [JIRA] (DOCU-906) How to retrieve and display content from an app in a template

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-906  
 
 
  How to retrieve and display content from an app in a template   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Evaluate if the docs can be improved to make this very common task easier. Probably including an example.See this for inspiration:https://forum.magnolia-cms.com/forum/thread.html?threadId=d9865bfd-a447-4491-be0e-54179e7e3ca0Maybe an extra example on the cmsfn page?Maybe a new page focussing on this topic? Now I see that this page exists:https://documentation.magnolia-cms.com/display/DOCS/Accessing+content+on+the+server+sideHowever there probably needs to be a short example and short conceptual explanation - either on this page or elsewhere.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To 

[magnolia-dev] [JIRA] (DOCU-906) How to retrieve and display content from an app in a template

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Documentation /  DOCU-906  
 
 
  How to retrieve and display content from an app in a template   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 22/Dec/16 9:55 AM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 Evaluate if the docs can be improved to make this very common task easier. Probably including an example. See this for inspiration: https://forum.magnolia-cms.com/forum/thread.html?threadId=d9865bfd-a447-4491-be0e-54179e7e3ca0 Maybe an extra example on the cmsfn page? Maybe a new page focussing on this topic?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

[magnolia-dev] [JIRA] (MGNLRESTCL-22) Context attribute is not installed during installation

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-22  
 
 
  Context attribute is not installed during installation   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 In the installation I receive this message. Do I need to configure something? is it expected?{ { code} Magnolia RESTEasy client module (version 1.0.9)Module '/modules/standard-templating-kit' is not installed. Context attribute is not installed. {code } }   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (MGNLRESTCL-22) Context attribute is not installed during installation

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 REST Client /  MGNLRESTCL-22  
 
 
  Context attribute is not installed during installation   
 

  
 
 
 
 

 
Change By: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 In the installation I receive this message. Do I need to configure something? is it expected? {{ Magnolia RESTEasy client module (version 1.0.9)Module '/modules/standard-templating-kit' is not installed. Context attribute is not installed. }}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (NPMCLI-60) It should be easy to get a bundle without the travel demo

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Zimmermann created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia CLI npm module  /  NPMCLI-60  
 
 
  It should be easy to get a bundle without the travel demo   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 21/Dec/16 4:41 PM  
 
 
Priority: 
  Neutral  
 
 
Reporter: 
 Christopher Zimmermann  
 

  
 
 
 
 

 
 It's not straightforward to remove the travel demo.  The CLI should provide an option to get the bundle without the demo. For starting a real project, you want a bundle without the demo. Another usecase is a partner that wants to get their developers up to speed with their own demo and perhaps their own templating kit. With the downloadJars feature, and the contentImporter they could get close to this - but the installed demo gets in the way.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment