A desired Cargo feature preventing a DPL3 -> Cargo switch, for some, is lack of a "linksto" and "linksfrom" equivalent (links/backlinks).
Others have requested how to achieve [[ https://www.mediawiki.org/wiki/Extension_talk:Cargo/Archive_October_to_December_2018#In-page_list_of_backlinks_RESOLVED | the same ]], and some have attempted [[ https://www.mediawiki.org/wiki/Extension_talk:Cargo/Archive_September_to_December_2022#Links/File_Use | workarounds ]] using _fullText search to determine links -- we also just tried that, though we discovered full-text search doesn't work in the case of transclusion (nor transclusion from extensions). Cargo cannot "see" transcluded content as belonging a page's full text (technically it isn't). We also can't search expanded text.
Another key difference, is DPL3 can "see", return, and do stuff to transcluded/expanded content, where Cargo cannot. In short, transclusion prevents full-text search as a viable workaround/tool for such cases (and I have to wonder where else transclusion may be an issue, what about transcluding/applying categories using templates?). The (proposed) cargo links/backlinks column could render this unnecessary, though would need to account for transclusion, including from extensions (like the widely used [[ https://www.mediawiki.org/wiki/Extension:Labeled_Section_Transclusion | LST extension ]]--which we also use). They ugly workaround we're using is to put a DPL3 "linksto" query into a Cargo store paramter as a default value, to get its contents in a Cargo column.
Could cargo simply fetch and populate backlinks/links for _pageData, from MediaWiki (since such already exists), to populate the proposed/requested columns?--This would also perhaps work if Cargo is set up on a separate database (recommended)?
Alternatively (or perhaps also), could the _fullText column have a config option to include transcluded contents? (Not sure if that suggestion is doable, nor advisable)