I would like to have a kind of API that allows me to add a new word entry, add its definitions, describe the derivations (if any) of the word, and have a field

I would like to have a kind of API that allows me to add a new word entry, add its definitions, describe the derivations (if any) of the word, and have a field for examples of the words usage. Some sort of system that would allow me to take a corpus, deconstruct the terms and words used, create a definition for each word, and so on. The reason is that I'm fascinated with dictionaries - the physical kind - in general, and would like to incorporate some sort of dictionary/glossary system in most of my apps as a means of documenting the technical terms for the subject those apps address. Another thing is that I'm a complete newbie to the subject of lexicography, and I'd love to learn more from like-minded individuals, on what kind of tooling and methodology is out there. I suppose I could go and look at the sources for such things as the OpenDict, sdcv (https://wiki.archlinux.org/index.php/Sdcv https://wiki.archlinux.org/index.php/Sdcv) and so on .. but surely there must be standards for the ways Websters and so on construct their lexicography. I'm just not familiar with these tools, so I'd hoped to have some insight from other like-minded individuals in this community, before I launch into a google-trail of my own investigation. With your site (wonderful, by the way) - did you invent your own schema for the database, or are you using some standard tooling on the backend? My ideal tooling would give me the ability to pipe a text file into it, construct a list of all un-defined terms/words/symbols, give the means of importing definitions from known sources for each word, and so on. Ultimately I'd love to be able to construct custom dictionaries for any given corpus, such that no term in that corpus is undefined; and to be even more meta about it, no term in the dictionary itself would be undefined. Obviously this is a highly iterative thing, as the undefined terms list grows with every definition added - which is why I think I have to understand the tooling better before I start constructing my own processes for this task.