Uploaded image for project: 'Magnolia Templating Essentials'
  1. Magnolia Templating Essentials
  2. MTE-61

Concept for JS/CSS dependent components

    XMLWordPrintable

Details

    • Story
    • Resolution: Outdated
    • Neutral
    • None
    • 0.7
    • None
    • None

    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.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                czimmermann Christopher Zimmermann
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD