Best Practices for Client-Friendly Content Updates with Uncommon Components

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