It was aggravating that opening README.md stored locally drove Firefox crazy. (It would recursively spawn new tabs, expecting the GitHub server to resolve the markdown… which spawned the next tab.)
So I prompted Claude ai to generate a Dashboard Gramplet that renders markdown files within Gramps. It has a Folder icon in the lower left that opens a file browser at the gramps52/plugins directory. Drilling down into a folder show .md files to open. If this is of interest, I’m happy to share.
Next, I was considering adding a custom markdown tags to support Gramps tutorials and guiding “Aunt Martha” through a shared tree. It would have to allow finding Icons from the installed Gramps. Maybe even switching category view modes and active objects. Or the same hotlinking objects feature as in Notes… but without its GUI link editing interface.
The developers strayed down that path before… but it turned into something of a quicksand trap.
Browser tech is in constant flux. So you’re always chasing a new (or old) feature that does not work on a certain configuration. Or patching a new security breach.
But I’d be happy to see a better remote/automation linkage between Gramps and browsers.
