[MTE-88] Evaluate adding Js and css resource inclusion via paths with with patterns Created: 27/Jun/16 Updated: 24/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia Templating Essentials |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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)
|
||||
| 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:
|