Versions Compared

Old Version 3

changes.mady.by.user Ruth Stocks

Saved on

compared with

New Version 4

changes.mady.by.user Martin Drápela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: DOCS-de-weblink

...

To have different types of origin sounds cumbersome at first sight - but actually it is a very handy feature. Let's give you some recommendations which resource type to use in which case.

Bestpractice

During development - use file based or classpath based resources. These files are easier to create, maintain and diff when you work within a team.

Use JCR based resource to "override" an existing source or to add an additional resource within a running Magnolia system in production. This can be done with the Resource Files app.

Referencing resources

Web resources

...

The Resource Files app displays resources (CSS, JavaScript, template scripts, YAML configuration files) from all origins and allows you to edit JCR resources.

...

Info
iconfalse
titleBest practice
Multiexcerpt
MultiExcerptNameUse a dedicated CSS pre-processor

New Web technologies such as Syntactically Awesome Style Sheets (Sass) and Less have largely replaced the need to do FreeMarker pre-processing for CSS files. You can now accomplish the same with a dedicated CSS pre-processor. We recommend that you start using such new technologies. Magnolia provides the /resources path (without dot) as a legacy option to support older projects.

Notes to legacy users

Magnolia 5.4 harmonized the loading and referencing of resources. You should start using the new origins and loading order.

...