Relume
Log in

Community forum for knowledge and support

Updated 4 months ago

Enabling Client-Driven Content Updates for Uncommon Components

At a glance
The community member is using a Header 80 component as a hero section, but they are concerned that the client will not be able to update the images that appear on scroll using the editor alone. They want to find the best approach to allow the client to update the content themselves without needing to contact the community member after the support period ends. A comment suggests that turning the component into a component and binding the images could make it easier to handle.
GGreg
·

Hey all. Quick question relating to uncommon components that use interactions.

What is the best approach when using them in order for the client to be able to update the content themselves, without having to access and navigate the designer?

I'm currently using Header 80 as a hero section but as I've come to realise that the client would be unable to edit the images that appear on scroll using the editor alone. I want to hand off the site knowing they can update the images without the need to contact myself after their support period ends.

Cheers

J
1 comment
JJesper

Turning it into a component and binding the images makes handling it a little bit easier

Add a reply
Sign up and join the conversation on Slack