If you want to use an SVG editor like SVG-Edit in your project but need features or methods it doesn’t support by default, the best approach is to fork the library and customize it based on your needs.

This gives you full control over the source and allows easy integration of new functionality. Instead of placing it inside the Assets folder, which is usually for static files, it’s better to keep it in a separate module like /libs/svgedit/ to make collaboration and maintenance easier.

If the editor isn’t tightly connected to your core app, you can also host it separately and embed it using an iframe or external URL—this is how tools like Free SVG Editor manage it. For long-term use and team collaboration, it’s important to document your changes clearly and keep the setup modular to make future updates easier to handle.