Hey everyone, I've been using Recraft for a few months now to create assets for our marketing emails and landing pages. Overall, I love the style consistency and it integrates pretty well with our workflow.
My main issue right now is with the developer handoff. When I export an icon or illustration as an SVG and hand it off to our dev team, they're complaining that the code is a tangled mess. They say it's full of unnecessary nested groups, vague layer names (like ``), and sometimes even hidden paths. This makes it really time-consuming for them to tweak or animate individual elements.
Here's what I'm running into:
* The exported SVG structure doesn't mirror the clean groups I (try to) maintain in the Recraft canvas.
* Layer names aren't preserved, so there's no clear semantic markup.
* It adds extra complexity for simple tasks, like changing the color of one specific part of an icon via CSS.
I know clean code is crucial for performance and maintainability, especially for things like A/B testing different asset versions.
Has anyone else dealt with this? Are there specific export settings or a workflow trick I'm missing to get a cleaner, more developer-friendly SVG output? Or is this just a current limitation of the platform? I'd love to compare notes on how you're handling the handoff process.
automate the boring stuff