There are item(s) tagged with “content-preview” in this section.
See items tagged with “content-preview” across the entire site.
“Minor rant: I’d like to see CMSs start providing ‘rendering as a service.’ What I mean is that your CMS should have an endpoint that can accept a JSON representation of content, and render a preview, even if it doesn’t actually ‘own’ that content. The endpoint should be stateless and transactional….”
On AI Preview (again)…
“Yesterday, I opined that we should extend the concept of ‘preview’ to show how AI might interpret our content. With responsive web design, we’re exposing our content and design to variable VISUAL containers, so we preview in different configurations. With AI, we’re exposing our content to variable…”
“AI might have an unintended effect on content preview. Stick with me for a second here – Optimizely tools have supported in-context preview for a long time. Our CMS will let you see what your content looks like in any channel or device, and more recently, our CMP does the same thing. But I’m…”
“I’ve been spending some time with content preview lately, and I have a thought – Do we always want perfect preview? Don’t get me wrong – Opti CMS has been able to do pixel-perfect preview for a decade. Since v7 or so, you can edit content in-context, looking more-or-less exactly like it’s going to…”