[MTE-67] NPM, Grunt, Bower etc research for MTE resources Created: 26/Nov/15  Updated: 14/Dec/15  Resolved: 09/Dec/15

Status: Closed
Project: Magnolia Templating Essentials
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Espen Jervidalo Assignee: Espen Jervidalo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MTE-66 Workshop: Frontend Resource Inclusion Closed
dependency
depends upon MTE-66 Workshop: Frontend Resource Inclusion Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Basel 22
Story Points: 8

 Description   

Goal:

  • Design concept for handling resources
  • Review of the concept

A few topics to consider:

  • How should a module handle dependencies to existing external 3rd party js libraries like jquery, angular, slick-carousel or css libraries like bootstrap.
  • Ditto for components.
  • How should a module declare it's internal js and css files - so that when a project or site uses the module those js and css files are included in the output html. (PM has proposed yaml based "resource library" for this.)
  • Should we use an established front end builder (like grunt/gulp etc) to perform some of our processed resources tasks?


 Comments   
Comment by Espen Jervidalo [ 09/Dec/15 ]

The current status is reflected in https://wiki.magnolia-cms.com/display/DEV/Light+modules+packaging

Generated at Mon Feb 12 07:41:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.