[magnolia-dev] [JIRA] (MTE-61) Concept for JS/CSS dependent components

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title

Christopher Zimmermann created an issue   Magnolia Templating Essentials / MTE-61 Concept for JS/CSS dependent components Issue Type: Story Affects Versions: 0.7 Assignee: Unassigned Created: 29/Oct/15 11:09 AM Fix Versions: 1.0 Labels: selected-for-backlog to-estimate Priority: Neutral Reporter: Christopher Zimmermann 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. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) ---------------------------------------------------------------- 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: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------