>Hi - I am get the broad strokes of what you are doing here but I am still a bit unsure of the finer details
I am afraid I don't have the time right now and isn't something that can be rushed. Web Components are new and finding the best way to use them with QuickBase involves trial and error and some inspired thinking. I have prototypes working but I am not satisfied enough to release anything public other than the earlier definition for [import] in this thread.
Perhaps you can place your form in a user defined page (named say myform.html) and include that page on the dashboard using the native "Web Page" widget QuickBase offers. Or you could use jQuery's load() method to inject the HTML in your myform.html into the dashbaord or a cell of a report. These methods are not perfect because you don't get full control over the layout, styling and behavior of your form (without additional scripting that is a bit advanced - but doable). For example, if you use the Web Page widget QuickBase will place your form into an <iframe> in the dashboard and you have to accept or deal with viewport sizing and trapped in a frame issues. Likewise if you inject your page using $.load() there may be an interaction between QuickBase's CSS and the styling you expect on your form because all the content (native and your injected HTML) is in one page. Web Components is designed to avoid these problems but the patterns of using Web Components alone as well as applying them to QuickBase have to be worked out.