Thanks a lot for your answer Max and Nik, greatly appreciating you taking the time and being so reactive !
To give you a bit more context on the use case, it's really a ingest and summarize a lot of prospect context via LLM -> swap in some context only on some slides only (like 6 cards over 25), so the generations route doesn't really fit the need.
I feel like for this kind of use cases, the from-template route might benefit from duplicating the template and working from there, editing instead of regenerating from scratch, which directly leads to the formatting issue mentioned earlier
or the /from-template might benefit from getting the html version of the gamma, which would include span and custom formatting etc, allowing the agent to rewrite from scratch while keeping formatting intact
just my 2 cents here 🙂 I think what you introduced with remix and are consolidating with from-template is extremely powerful, especially if you find a way to ensure a pixel perfect design consistency, so using gamma doesn't become a design break hunt, which sadly makes it impossible to deploy programmatically at scale if we need to keep a human in the loop to review and fix manually each card's component settings.
%20(1).png){kind=avatar}
