I also think that using Blender for this has a lot of shortcomings, like for instance styling lines and hatches, no WISIWYG. Another one is it heavily couples ifcopenshell / Bonsai with Blender's data structures and 3D algorithms where the philosophy is rather to build an agnostic structure and let multiple apps profit from it.
My take on it as of today FWIW is that I do need a solution right now to finish my ongoing and future projects projects so I have to make do with what I have, I can't have a solution that is not functional, even if it means a fair bit of manual tweaking in the later parts of the workflow. I can build the solution in Blender, on a web interface I do not know how. So I elected on doing it inside Blender, which also have a lot of pros, especially considering there is a fair bit of 3D/2D processing needed to create meaningful drawings. Although conceptually I don't think using scenes to isolate specific drawings or to put together drawings works that great, as you can't instance a scene in another scene, you can only instance collections into other scenes. Adds a little bit of complexity to the whole setup.
Also at least in my field, whether I like or not, DWG / DXF is the defacto deliverable data format my clients expect. So working on a web based interface with web based data formats means I'll have to add another translater to convert svg to dxf, and css styling to dxf styling which is not a huge deal but as anyone who has worked in the field knows, translation can't convey 100% of the source meaning to the target language, so I would lose a bit of information in the process, and I would miss some information that you get in dxf and doesn't exist in svg.
Another point is I think I don't really get the point to use a web interface instead of a standalone application. I think it's from lack of experience in the field. Is it to be OS agnostic ? Easier to build something from the ground up, and make changes to ?
