Improving Relume: Editing Semantic HTML, Responsive Fonts, and Accessibility with New Publish Features

·Aug 26, 2026 09:00 AM·

Hi team. Love what you are doing and improving. Been part of the community for 1400+ days. the reasons I stopped using Relume for most of my work:

there is no way to edit semantic html in relume (components)
font sizes do not leverage min and max widths
your system relies on hard coded breakpoints and not container queries
webflow components still use the very outdated CF framework

to name a few. Question: are there any options with the new publish feature to edit and improve such things on my own in Relume? Because when it comes to accessibility, clean HTML … relume seems to be behind, and I strive to deliver the best quality Code matters even more in the AI-age we are in. thank you.

2 comments

· Sorted by Oldest

Matt J.
·
·
Hey Samuel U.! Appreciate your veteran support over the years and your feedback here is critical to our success. Generally, my response will be vague here because we're early. Also we're not tied to third-party software here, so I would also say "anything is possible" - which was the entire reason for pivoting to a brand new platform, that was largely started from scratch - a huge risk, and a move most companies wouldn't even consider, let alone pull off in 9~ months. With that said, I'd love to understand more precisely what you mean by some of this feedback and more importantly - why it matters to you - I think this is the part where the value in your feedback lies. Most of this feedback feels like hang-over from the previous platform - I want to be clear that this is a completely different platform - the components, the data structures, and how they are created are completely different from the previous system - there were some real constraints to actually doing some of this in the old system, that are simply just not constraints at all in the new system. So now it just becomes a decision and a resources question, not a "can we do this or not" question. (Holy shit, I've been reading too much AI and that sounded so AI but I swear I'm typing it out)
1.
Semantic HTML - do you have any examples of the types of edits you'd make to our Relume Publish components and the semantic HTML here? There were very deliberate moves and intentional care behind the scenes to ensure we're building these components in a semantic way - thus enabling accessibility. Again, explain why this matters to you, this is where I feel like the value of what you are asking for really comes from.
2.
Fluid font sizes - why does this matter to you?
3.
Same as above - container queries and fluid font sizes fall under the same fundamental system, have you weighed out the pros/cons of this system versus others - what are the tradeoffs - is it appropriate for the majority of websites or no? Those are the kinds of questions we have to ask. Similarly, is it maintainable and predictable? I don't have an answer here since I have not done proper research on it, but I think we'd be foolish to not explore it - and for all we know, our team probably already has. The meticulous attention to every detail and every decision that was made, especially at the fundamental levels, would likely blow your mind.
4.
This is a non-issue now that we are in our own system.
Aside from accessibility - (and maybe this is the only reason) - but from your point of view, why does "best quality code, clean HTML" matter to you? Again, I'm just probing for more context - not challenging your opinion, invalidating your feedback, or trying to mute your voice. My intention here is to do the opposite - how can we effectively take action on your feedback. What do we need to consider? Whats your baseline experience/context here, so we're all working from the same starting point, and working from there. I can appreciate that a response here could take some time - so no rush - I appreciate any additional context you can provide here! Appreciate you! 🙌
Samuel U.
·
·
Matt J. thank you for taking the time to answer here. I try to answer some of your questions. To be honest I am only looking at the code of your example templates for the new publish feature. One HTML issue I spot right away. There is no H1 on the page. Just missing. Another issue: Links in the footer are not in am HTML List element. Every section is wrapped in an extra div. Not crucial but another extra element and more code. Why this matters? Well some HTML matters for SEO, some for accessibility, and for AI who does only read the code. E.g. check your sites when the font sizes is much larger and not the default one. Some Layouts do not work anymore because they are not built with container queries. I know for most people not big issues. but in an AI world where an agent could optimize such things easily I don't see why not leveraging best in class websites.

Matt J.
·
·
Hey Samuel U.! Appreciate your veteran support over the years and your feedback here is critical to our success. Generally, my response will be vague here because we're early. Also we're not tied to third-party software here, so I would also say "anything is possible" - which was the entire reason for pivoting to a brand new platform, that was largely started from scratch - a huge risk, and a move most companies wouldn't even consider, let alone pull off in 9~ months. With that said, I'd love to understand more precisely what you mean by some of this feedback and more importantly - why it matters to you - I think this is the part where the value in your feedback lies. Most of this feedback feels like hang-over from the previous platform - I want to be clear that this is a completely different platform - the components, the data structures, and how they are created are completely different from the previous system - there were some real constraints to actually doing some of this in the old system, that are simply just not constraints at all in the new system. So now it just becomes a decision and a resources question, not a "can we do this or not" question. (Holy shit, I've been reading too much AI and that sounded so AI but I swear I'm typing it out)
1.
Semantic HTML - do you have any examples of the types of edits you'd make to our Relume Publish components and the semantic HTML here? There were very deliberate moves and intentional care behind the scenes to ensure we're building these components in a semantic way - thus enabling accessibility. Again, explain why this matters to you, this is where I feel like the value of what you are asking for really comes from.
2.
Fluid font sizes - why does this matter to you?
3.
Same as above - container queries and fluid font sizes fall under the same fundamental system, have you weighed out the pros/cons of this system versus others - what are the tradeoffs - is it appropriate for the majority of websites or no? Those are the kinds of questions we have to ask. Similarly, is it maintainable and predictable? I don't have an answer here since I have not done proper research on it, but I think we'd be foolish to not explore it - and for all we know, our team probably already has. The meticulous attention to every detail and every decision that was made, especially at the fundamental levels, would likely blow your mind.
4.
This is a non-issue now that we are in our own system.
Aside from accessibility - (and maybe this is the only reason) - but from your point of view, why does "best quality code, clean HTML" matter to you? Again, I'm just probing for more context - not challenging your opinion, invalidating your feedback, or trying to mute your voice. My intention here is to do the opposite - how can we effectively take action on your feedback. What do we need to consider? Whats your baseline experience/context here, so we're all working from the same starting point, and working from there. I can appreciate that a response here could take some time - so no rush - I appreciate any additional context you can provide here! Appreciate you! 🙌
Samuel U.
·
·
Matt J. thank you for taking the time to answer here. I try to answer some of your questions. To be honest I am only looking at the code of your example templates for the new publish feature. One HTML issue I spot right away. There is no H1 on the page. Just missing. Another issue: Links in the footer are not in am HTML List element. Every section is wrapped in an extra div. Not crucial but another extra element and more code. Why this matters? Well some HTML matters for SEO, some for accessibility, and for AI who does only read the code. E.g. check your sites when the font sizes is much larger and not the default one. Some Layouts do not work anymore because they are not built with container queries. I know for most people not big issues. but in an AI world where an agent could optimize such things easily I don't see why not leveraging best in class websites.