Bug Report: Blog Post Body Section Content Editing Issues

·May 02, 2025 05:31 PM·

Share

Hi Relume team! 😊 I wanted to flag a bug we’ve run into while using the Blog Post Body section (Content 29). The layout visually includes multiple formatting elements—bolded headers, body copy, an image, and a subtext line—which looks great on the front end. However, when selecting this section to edit, the content is pulled in as one unformatted block of text. We’re not able to independently edit the header, subtext, or other formatting components. Would it be possible to update this section so each element is editable as it appears in the layout? Thanks so much—we really appreciate your help! Here's a loom for visual context: https://www.loom.com/share/8a392f855cb345b4be1b197ec8a63f4d?sid=3c61434d-460c-41a5-8cb1-f3814de5eba4

2 comments

· Sorted by Oldest

Matt J.
·
·
Elodie R. thanks for flagging - this is actually similar to your other issue with this component. My guess is that importing this component into Figma is actually going to be very difficult because this component is originally based on a rich text field in Webflow - which works fine in Webflow but there's no such thing in Figma. Its something we can look into improving, but I really doubt we'd actually be able to improve it. A likely workaround would be to treat this component as a placeholder template for repeating posts rather than inputting real content into it and then draft that real content somewhere else and when ready to build in Webflow, input that content into the webflow CMS.
Matt J.
·
·
I've added this to our list though - just want to be clear that I'm not at all ignoring your request here - simply just trying to provide some context, expectations, and a possible workaround.
🙌1

Matt J.
·
·
Elodie R. thanks for flagging - this is actually similar to your other issue with this component. My guess is that importing this component into Figma is actually going to be very difficult because this component is originally based on a rich text field in Webflow - which works fine in Webflow but there's no such thing in Figma. Its something we can look into improving, but I really doubt we'd actually be able to improve it. A likely workaround would be to treat this component as a placeholder template for repeating posts rather than inputting real content into it and then draft that real content somewhere else and when ready to build in Webflow, input that content into the webflow CMS.
Matt J.
·
·
I've added this to our list though - just want to be clear that I'm not at all ignoring your request here - simply just trying to provide some context, expectations, and a possible workaround.
🙌1