I think it has a lot of potential, im currently editing all 18 documents to replace names and some objects ive written about, so having it is definitely a real world issue solver lmao, instead i could just go to a variable table / header file (what ever you want to call it or refer to as) and change the variables once for all files that are reading from that table/file/data would be really useful. i think the simpler the better, as would be needed by non programmers and they may not have a good understanding of code, so making it simple syntax would be the best thing, id hide any data that appears complex unless directly “shown” by users (like my self) so it is not in non technical users face confusing them. making your software usable across the board. i think complex use cases need these sort of tools. but in a lot of indie cases, it could be hidden or behind an option.
maybe you could have a predefined document type that has everything already set, have an option for pointing docs to that header file (if not done with syntax) and have a table / list a non technical user can add or subtract from to add their variables. then those variables can be accessed from a modifier like “/” or “!”
and for complex users make it more code like where they can create any document type and just add what they want via #includes ##includes and variables with syntax for those that may need more flexible and more involved capabilities.
it could be in many different formats but i think that it could be massively valuable. especially if you can reference this from things like script dialog editor and quests etc.