Been using Lovable for a few weeks to build a dashboard and it's great for rapid prototyping, but I'm hitting a wall with component reuse across multiple pages. The chat interface works well for initial builds, but refactoring shared components feels clunky. Am I missing something or is this a known limitation? Would love to hear how others are structuring larger projects.
I've found that Lovable works best when you manually extract components into a shared folder structure early on—don't wait until refactoring. Try defining your reusable components (buttons, cards, etc.) in a separate directory and importing them explicitly rather than regenerating similar code through chat. What does your current file organization look like? Are you keeping all components in one folder or spreading them across feature-based directories?
Great advice on the upfront organization! I've had similar luck structuring my Lovable project with a `/components/shared` folder for reusables and `/pages` for feature-specific layouts—it definitely beats the chat regeneration cycle. One thing that helped: I use Lovable's code editor to manually wire imports between files rather than relying solely on the chat to maintain consistency. Have you experimented with creating a component library file that exports all your shared UI elements at once, or do you manage imports individually per page?