[MTE-61] Concept for JS/CSS dependent components Created: 29/Oct/15  Updated: 23/Jun/16  Resolved: 11/Apr/16

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:
Epic Link: Light Development 1.0

 Description   

To provide a satisfactory basic OOTB set of components to satisfy our customers and evaluators, we require several components which depend on front-end resources (JS/CSS):
Video
Carousel
Columns
Social share

However, including CSS and JS is incompatible with our goals with the MTE to create a future-proof module that is not dependent on the quickly changing trends of front end development.

How then should we include these components in the product, while keeping a future-proof MTE?

A related issue is: how can a component provide its unique resources, rather than a module providing resources for a collection of components?

Some options:

  • MTE does not contain components - a separate module does.
  • MTE contains template definitions & dialogs, but not templates - a separate module contains the templates and associated resources.
  • MTE contains only components that do not require front-end resources. A separate module "advanced-components" or something like that contains these components.


 Comments   
Comment by Espen Jervidalo [ 29/Oct/15 ]

Somebody looked into using npm for this?
'npm install magnolia-carousel'

Comment by Christopher Zimmermann [ 29/Oct/15 ]

Cool idea.

Comment by Christopher Zimmermann [ 11/Apr/16 ]

Closing as outdated.

Change since ticket creation:

  • MTE module no longer contains templates and their resources, they have all been moved to MTK. So MTE can now be "future-proof".
  • MTK can contain frontend resources. Resources for each component should be kept separate, so that they do not get entangled.
  • Carousel and Social Sharing will not be part of MTK module.
  • These components (Carousel, Social Sharing) will be available as independent (light) modules and will either contain their own resources, or reference them as dependencies via NPM.
Generated at Mon Feb 12 07:41:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.