I am undecided on using mainly svg images from simple icons or Fork Awesome as a CDN call, so I am planning on adding both as footer files and i can just rename them to "footer.tpl" if i want to switch
Fork Awesome Pro:
Less/Cleaner code
SVGs or other images do not have to be stored locally
Fork Awesome Con:
CDN call
SVG Pro:
No CDN call needed since things are local
SVG Con:
(for now with what i know/dont know) less "control"
I am undecided on using mainly svg images from simple icons or Fork Awesome as a CDN call, so I am planning on adding both as footer files and i can just rename them to "footer.tpl" if i want to switch
Fork Awesome Pro:
Fork Awesome Con:
SVG Pro:
SVG Con: