Codepen? More on reddit.com

You'd send the Python code to the backend, execute it there (with some kind of sandboxing), and then send the result back to the frontend. Executing Python in the browser isn't straightforward yet. You'd need to send an interpreter to the frontend that is written in either JS or Webassembly. More on reddit.com

You can do it with a node-based bundler like webpack or vite - those are still the leading way to do it today. Vite is preferred by many people today if you don't have any legacy reasons why you need webpack. My preference would probably be a docker setup for local development, but that does require a setup for every new project. I've never had any kind of setup that will compile files without running anything. Ultimately there will always need to be a process running to compile your files, it's just a matter of how it gets booted up or triggered. I haven't used them because docker is better for my setup, but I have also heard of vscode plugins that will auto-compile for you while you have vscode open - if that suits you, you should use it! The advantages of a docker setup and why I use it: configure once, run on any machine don't need to fuss with versions or configuration once you've set it up - a docker configuration is as close to 100% future-proof as you're going to get simplifies sharing your project across teams - other team members don't need to worry about their machine setup makes versions and configuration explicit so you always know exactly what this build was meant to run on Once you've been working on websites for a long time like I have, you start to appreciate projects where the setup to develop process is smooth and error-free, and you do not have to worry about your local setup in order to run an old site you coded some time ago. Dockerizing can usually provide that. More on reddit.com

I would suggest building your own UI kit within Webflow. Test the features as you build, name and document in a pattern that makes them easy to reuse and bind simple styling/functions as needed when you implement them.

You can add to this indefinitely and clone your kit for each new project you use. I split mine into pages that have like components — a page for heroes, a page for cards, navs, etc. Interactions can, and should be saved as well.

From there I can rapidly build layouts and have a guide for how to work in any CSS/JS overtop. Most of this is copy/paste.

This is a bit of a different approach to what you’re suggesting but it seems to be better suited to Webflow as a platform. It can also speed up your design process. Spend time building a solid UI kit with clear documentation and you can rapidly build ~75% of your site using tested elements.

More on reddit.com