SVG Vs Everybody
summary
SVG1.1 is fully supported in all evergreen browsers and the claim here is concrete: Code42 switches to SVGs for all icons and logos to avoid blurry raster assets, cut HTTP requests and allow programmatic recoloring across six sites. Workflow uses Illustrator’s Image Trace to convert PNGs, SVG Go in gulp to optimize, and a custom WordPress plugin that stores optimized files and injects them as inline SVG via a get_file_contents pattern so editors swap logos without developers, enabling zero HTTP requests, ARIA accessibility, filters and SMIL/GreenSock animations.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker background
- 1:08What are SVGs and why use them
- 7:33Converting PNG to SVG in Illustrator
- 13:07Three ways to use SVGs in code
- 16:30Anatomy of an SVG file
- 19:26Using SVGs in WordPress
- 21:41Code 42 case study for SVG plugin
- 23:11Making SVGs accessible
- 24:14Animating SVGs without JavaScript
- 25:19SVG filters and effects
- 26:55Reusing SVG elements with <use>
- 27:43SVG elements and shapes explained
- 30:23Responsive SVG logos with media queries
- 32:50Working with SVG paths and Bézier curves
- 33:11ViewBox and preserve aspect ratio
- 34:21Responsive text in SVGs
- 35:13SVG resources and experts
- 37:23Q&A session
