Community forum for knowledge and support

Updated last year

Determining When to Keep or Create New Relume Component Names

At a glance

The community member is seeking advice on when to keep an existing class name or create a new one when using Relume components. They realized that changes made to a Relume component become part of that component going forward, and they can't paste in a clean version anymore. The community member tried renaming a class from "section_layout3" to "section_featuredBook", but this broke the layout on mobile viewports. Another community member replied with a video that might help, but the original poster is still looking for a written process on how to best proceed when using Relume to avoid these issues.

Useful resources

Can anyone point me to some resources around when I should keep an existing class name and when I should create new when using Relume components? I realized that changes I make to a Relume component become part of that component going forward and I can't paste in a clean version anymore. So... I thought I'd swap out the relume name for a new name in all classes. For example, "section_layout3" becomes "section_featuredBook" and all references down the chain to "layout3" become "featuredBook". Unfortunately, that seems to break the layout on mobile viewports. Anyhow, would love some advice.

D
F
M
3 comments

replied to a similar question when I asked with a video that might help: https://www.loom.com/share/e44d1a2bbf274be1a7e93beae5b5fb99?sid=31d39901-9166-4777-8075-b97d3f506696

But to be honest, I am like you. Would love to have some sort of written process on how to best proceed when using Relume to avoid those issues

how are you going about renaming these components? Would you mind sharing a read-only link so that I have a bit more context?

Add a reply
Sign up and join the conversation on Slack