-
Story
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
We have decided that processed resources should be supported for resources served via /.resources
(See https://wiki.magnolia-cms.com/display/PMTEAM/2015-10-06+Processed+Resources)
The system should support all resources, regardless of origin.
Create a concept on how this should work. It should include:
- UX
- Technical implementation
Notes:
Processed resources
- What to do with Resource#modelClass
- What to do with nested processed resources as sub-nodes (e.g. sample-css)
- Encourage additional generators as filters (e.g. Sass)
- is related to
-
MGNLRES-184 Phase out in-place templating app in favor of Resources app
- Closed
-
MGNLINTEMPL-83 Remove legacy in-place templating "Templates" app
- Closed
-
MAGNOLIA-6355 Context object is not exposed to login form in Magnolia 5.4
- Closed
- relates to
-
MGNLRES-237 Re-enable a user-interface for processed resources
- Closed
-
MGNLRES-203 First set of improvements for Resource files app
- Closed
-
MGNLRES-265 Correct content type for bypassed processed CSS files
- Closed
- supersedes
-
MGNLRES-144 Implement new origin-based ResourcesServlet
- Closed
- Wiki Page
-
Wiki Page Loading...