Map like Data-Structure in LaTex

My CV is a mess, but I think almost everybody got the same result over time. Lot of experiences, certifications, projects and so on. Furthermore, having his CV in LaTex is great but it can be hard to update/upgrade it when needed... Why not using something like a database to store all those elements? Well, we can use another layer or tool to deal with that, but it seems LaTex can do that as well with the pfgkeys package. The idea here is to create a really small local package offering an interface to store different kind of elements per categories. Let start with our requirement. How to put experiences? \experiencePut { devto }{ date }{ 2026 } \experiencePut { devto }{ title }{ author } \experiencePut { devto }{ summary }{ Writing article for fun and no profit } \experiencePut { devto }{ location }{ somewhere on the web } \experiencePut { devto }{ company }{ dev.to } \experiencePut { devto }{ skills }{ tex, latex, erlang, elixir, dart, flutter } \experiencePut is taking 3 arguments, the first one will be a reference to a position (e.g. devto ), the second argument will be an unique keyword (e.g. date ) and finally, the last argument will be the data to store (e.g. 2026 ). How to get this information back? \experienceGet { devto }{ date } \experienceGet { devto }{ title } \experienceGet { devto }{ summary } By creating experienceGet , where the first argument is the reference to a position (e.g. devto ) and the second one to the unique keyword previously set (e.g. date ). Then, it will return 2026 . Neat. Right? Let create our local package called map.sty . $ touch map.sty It will contain the definition of our interfaces and few mandatory elements for LaTex. Thanks to overleaf, we have now great LaTex documentation about that. \NeedsTeXFormat { LaTeX2e } \ProvidesPackage { mystore } [2026/07/24 map package] \RequirePackage { pgfkeys } pfgkeys requires a list of keys to work correctly, then the /cv/ key is created. More information can be seen on the documentation reg