I built yet another carousel maker. This one is for developers.
Yes, I know. The internet probably wasn’t waiting for another one 😅
But I wanted to focus on something specific: turning engineering articles into visual stories.
Think database migrations, system architecture, scaling problems, and the trade-offs behind technical decisions.
There’s a lot of good content buried in engineering blogs. Turning it into a useful carousel means finding the story, explaining the concepts, and figuring out what deserves a diagram.
That’s what I’m building Chartin to help with.
Paste an engineering article URL → turn it into a carousel with a story, technical diagrams, and slides you can export for LinkedIn or Instagram.
The people I’m building for are developers sharing what they learn, technical writers, and DevRel teams repurposing engineering content.
The biggest challenge is making the slides easy to follow while preserving the technical details that make the article valuable.
You can check it out here: https://chartin.co
If you publish technical content, how are you turning longer articles into social posts today?
I still do it ugly and by hand. One sentence from the article that already did the work, then one concrete example under it, and I stop. Carousels I tried twice and both times people argued with the diagram, not the caption, so if the author can fix that diagram before export I'd actually trust it. Paste-a-URL and get 8 slides I trust less until I've seen it drop a trade-off on purpose.
The diagram question is where this gets interesting. Text-to-carousel tools can summarize paragraphs into bullet points all day, but extracting the right visual from a database migration post or a scaling architecture article is genuinely harder. The diagram IS the content in most engineering posts — the surrounding text just annotates it.
We write technical SEO content and the repurposing problem is real. A 2,000-word article about crawl budget or rendering becomes "here are 5 tips" on social, which strips out everything that made it worth reading. The carousel format at least lets you preserve a sequence of steps or a before-and-after comparison.
Curious about accuracy on technical diagrams specifically. Does Chartin generate new diagrams from the article text, or extract and reformat existing ones? The failure mode for generated diagrams in technical content is subtle wrongness — looks right, technically incorrect.
The hard part you named, keeping the technical detail, is also where it can go wrong: a diagram that's slightly off about a migration gets called out in LinkedIn comments fast. Can the author edit the diagram itself, or only regenerate it? For DevRel teams that review step is probably what decides whether they trust the output.
Have early users shown that preserving technical detail is the main reason they would return to Chartin, or is the bigger value simply avoiding the work of turning articles into social content?
Love this angle. Building Xstream4K right now so this hits close to home — what made you look into it in the first place?