(ui-nav-link {:component "a" :href...}) of it's just a string

I’m not sure I understand the question, and perhaps Jakub did and is right. The dom/a in Fulcro is both a macro and a function, so you can always pass it by value. You can also use a string and then use that string (“a”) as the tag in c.f.f.dom/crete-element

You can also pass an element (reified) from react (e.g. (dom/a {:href "foo"}) returns an element value that can be used elsewhere). i.e.

(let [ele (dom/a ...)]
  a)

Any react component/library that honors the “controlled component” idea is best. Anything works ok once you understand how to put a factory on it, but since Fulcro encourages you to control state, controlled components are best. That said, input-like things may need a patch (see StringBufferedInput in c.f.f.dom.inputs)

Usually the hardest part is js ecosystem variances…i.e. how do you actually require the darn thing, and how do you deal with things like “embedded css” that webpack is supposed to handle. Those are not Fulcro issues.

thank you, I was trying to solve this exact problem earlier when porting the fulcro template to pathom3

Thanks that's good to hear :)