...
| Note |
|---|
Important: If the path contains a file with the same name, the new file from the package will not be added. Instead, the document XML will be modified during import to utilize the file already in the BackOffice. |
...
Change the font location to the same staic static folder path when importing packages.
...
Prevents duplicate fonts
Saves storage space
Ensures use of verified, working fonts - as it is possible for someone to upload a corrupt font or for the font to become corrupt during unzipping
This approach assumes that font names are consistent amongst users, which is what we also find in looking at usage. However, in systems that utilize a lot of different fonts and designers without strict font requirements, you will still have a small percentage of duplicate fonts due to the font file names being different.
Asset Management
It's strongly recommended to:
...
This approach prevents accidental overriding ignoring of unique assets with that happen to share the same name that are supposed to be uniquefile name. For example, someone uses an image called “headshot.png” and when they import the package, there may already be another “headshot.png” from a completely different designer. Clearly, you want both copies, and you don’t want to replace the package file with the already existing file. Thus, it is prudent to use unique folder pasts with assets.
However, please create a cleanup strategy to clean up old unused assets.