Webstudio
Log in

Join the Webstudio community

Updated 4 weeks ago

Post content via CMS with mixed text and images/media?

ppaulrudy
·
This is a question for a blog where posts are pulled into WS from a CMS.

How might a Webstudio site be set up for a blog whose posts go beyond a predictable "featured image + text" format, and include multiple images and/or media interpersed in the text?

Ideally, any assets that Webstudio handles would be imported (and optimized). Could this be done eventually with the planned markdown CMS import?

(I just added a comment to the markdown import github issue on this subject https://github.com/webstudio-is/webstudio/issues/3485#issuecomment-2204852473)
2
J
p
O
12 comments
JJohn Siciliano
I believe the question is "will images in rich text/content embed get Webstudio optimization treatment too?"

I wonder the same. Currently its working on the img component
ppaulrudy
Thanks for better summarizing my question!
OOleg Isonen
content embed is using image component so yes, it should be enabled by default
JJohn Siciliano
Content embed's images arent getting run through the transformation process though. Here's the UI, doesnt have optimize either
Attachment
image.png
JJohn Siciliano
I think because it's not the component, just a selector. Could be wrong
BBogdan
Exactly, we do not affect html from cms except with styles
ppaulrudy
Is that something that might eventually be on the roadmap? Specifically image optimization from cms content embed
OOleg Isonen
Oh right, my bad, we just inject hmtl as it comes from cms and we render css, we don't do anything else
OOleg Isonen
While in theory we could treat that html as spec and render components instead, this wasn't it's original intention.
OOleg Isonen
I think many CMSs support json based rich text which is probably the rason - using components with any logic instead of just html
ppaulrudy
@Oleg Isonen I think I understand. I have a little experience in using Markdoc https://markdoc.dev/ with Astro. Extensible markdown with customizable components, html tags, and more. it might be interesting to add something like that to the long term roadmap.

But I'm happy with basically rendered imported markdown at the moment!
HHero
How about image components where the src is from the cms? That runs through optimizatin, right?
Add a reply
Sign up and join the conversation on Discord