<Lenis> component is already creating a content element for you, you can access it from ref. I don't see any reason why you would need to define a custom content element.

const contentRef = useRef()

return ( <Lenis ref={(ref)=>{
  contentRef.current = ref?.content
}}>
  // content
</Lenis> )

Hey @clementroche, thanks for the quick response! I understand. My problem is actually a slightly different one, I just thought it’d be fixed by defining the content.

In my NextJS I have a root layout that uses <Lenis root> for smooth vertical scrolling. I then have a subpage, that is meant to be only scrolled horizontally, so I defined another instance of Lenis in said component, again as root, with the options

orientation: 'horizontal',
gestureOrientation: 'both',

It seems, that the two instances of Lenis interfere with each other and I don’t know how to fix this?

Defining a content element for a root Lenis is useless and will do nothing. Why can't you define a layout that will take care of switching from vertical to horizontal? And then call it within your page? Your Lenis doesn't need to be defined in the root layout.