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

Evaluate adding Js and css resource inclusion via paths with with patterns

    XMLWordPrintable

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None

    Description

      Magnolia should provide an easy and elegant way to provide js and css resources in web pages via paths with wildcards or patterns, as demonstrated in "neat-resources": https://github.com/rah003/neat-resources

      To determine:

      • Which exact functions should be provided?
      • How to handle serving of cached and non-cached resources? Probably there should only be one method, that delivers uncached in developer mode, otherwise delivers cached versions.
      • In which templatingFunctions library should this be provided - in the existing cmsfn, or a new resourcesfn?
      • What are the implications for themes?

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                  Created:
                  Updated:

                  Checklists

                    Task DoD