Hi Guys,
Is it possible to resuse images under Multiple CSS design assets via linking?
Or to they have to be a direct associated asset of the CSS asset (mysource_files/image.gif)
or is it bad joo joo?
Many thanks
Fuzz
Personally I wouldn't link them under the design file. Rather I use globals keywords in my parse file. Reason for this is to cut down on all the linking that happens when you have customizations.
Ooo I didn't think you could use global keywords in a CSS asset - I thought these had to be associated assets if you used a CSS design asset.
Actually one of our administrators made the suggestion of using global keywords in the stylesheets at one time but if I can remember correctly it was not really a good option.
Mr Hall you poo pooed this one didn't you?
I'm just looking for the easiest way to reuse assets across multiple CSS assets - using an asset Id in the CSS file isn't good either.
It's either associated assets or full path data urls.
[quote]
Ooo I didn't think you could use global keywords in a CSS asset - I thought these had to be associated assets if you used a CSS design asset.
[/quote]
Sorry, I didn't mean in a CSS file, I just meant in a Design Parse file to LINK to the css file.
[quote]
Sorry, I didn't mean in a CSS file, I just meant in a Design Parse file to LINK to the css file.
[/quote]
If you're using a CSS design file, pretty sure you can use globals; My gut feeling is that turning static caching on (CSS design file details screen) would offset any performance issues that may arise from this. Can anyone confirm?
Thanks nic and Rugi =)
You can use globals and it works in the css file however - however there is processing time for the keywords. Using id's works - but won't cache. Data or mysource_files is fast with minimal overheads.
But to be an associcated asset the file must be under the asset - hence my question regarding linking - for css design assets.
If you can use globals in a css design asset - I'd rather use the globals - but if you don't need a css design asset and use a css or text file asset - i'll recommend the data urls.
But yep good question rugi regarding static css option.
Hey Bobby
Our office was asked what the options were in your case at one stage and we provided something along the lines of:
– associated files (mysource_files/blah.jpg)
– domain relative (/__data/assets/image/0016/628/blah.png)
– globals keywords (%globals_asset_url:1234%)
At the time I believe you chose to stick with associated files because you were already familiar with the process and there were too many images to use globals keywords for i.e. would increase parse time. The CSS file did not have the performance features they do now.
I'd be more inclined to keep your image under the CSS file and use the domain relative approach or globals keyword if its only a couple of references versus linking it.
You'r system now has a few features on the CSS files that could help with performance if you wanted to convert to globals keywords. As long as the design uses linked CSS design areas you can turn on the static, versioned, minified options.
Cheers
Scotty
Thanks Scotty yep I do have this correspondance and placed this feedback out to our administrators.
It's always good to check as we get differing opinions and advice and I really value the advice you provide.I have placed out to use domain relative or globals
We are still using linked design nested areas as originally set up so I'll pass through the advice that we can indeed use static options on our CSS files also:)
Cheers again Scotty
Fuzz