u/mokshsinghdangi

https://reddit.com/link/1sihxh4/video/1a4uhufh2kug1/player

I am building a new project in Framer and created this full page navbar. The navbar is a component whose height changes from 64px to viewport height. Now I have another component inside navbar which changes when click on respective tabs inside. The problem is that is the viewport height become too small, the content in the navbar cuts out and I want to make the content on the right scrollable. I try to set the overflow to scroll inside the component of content on the left but that doesn't seems to work. Is there any way I can make the section on the right scrollable when the screensize becomes too small?

Hey r/Framer,

I recently launched my first plugin (Carto) as an independent solo project, and I’m currently brainstorming what to build next. I want to tackle a technical bottleneck that actually bothers people, rather than just making another basic utility wrapper.

It seems like right now, if you want to display charts or graphs using Framer CMS data, you’re basically forced to use an iframe embed (like Chart.js, Airtable, etc.).

The problem with iframes is that they kill the Framer workflow: you can’t link them to your global color variables, handling responsive breakpoints is rigid, and you completely lose the ability to use native Framer scroll and hover animations.

The Idea: I’m thinking of building a plugin that pulls numeric data directly from your connected Framer CMS and mathematically draws native Framer layers (Frames and SVG paths) right onto the canvas to create Bar, Line, or Pie charts.

Because the output would be native layers instead of a sandbox code component, you could:

• Link the chart colors directly to your Framer Theme variables.
• Add native Framer scroll-reveal animations to individual data points.
• Fully control the layout and styling across desktop, tablet, and mobile breakpoints just like a normal frame.

Before I spend days writing the logic for this, I wanted to get a reality check from this sub:

1. Is this a real pain point you actually face, or just a "cool on paper, rarely used" feature?
2. What kind of sites are you building where you actually need CMS-driven charts? (Reports, directories, SaaS marketing pages?)
3. If you would use this, what chart types are absolute dealbreakers/must-haves?

Let me know if this sounds like something worth pursuing, or if I should pivot to a different problem entirely. Appreciate any feedback!