Hi Kaleb, first of all thanks for the answer and willingness to help.

Now looking at how the ST accepted middleware is organized in reality and how they recommend to be organize in the above mentioned document, one can see that there is no relation , not even marginally close. It actually doesn't matter as long as you have good templates that hides the code organization ugliness.

I have to say I've started to look closer into the ST software and examples and I was really overwhelmed on how miserable and anti-pattern are.

The one shiny idea was CubeMX and the derivative CubeMXIDE, and above all the managed code generation via the FTL templates, it's not much, but the possibility to have some kind of repeatable, relatively consistent  project file that allows (re)producing source code bundles for many slightly different boards revisions and scopes it's a God send. Also putting main parameters in a GUI and selecting their visibility depending on HW features of the selected MCU is very nice, in the end the old crusty consultant/programmer could still make handcrafted unmaintainable code to make themselves irreplaceable, but I hope that someone will put an end to it /rant.

I've had a look at the FTL files of the accepted TLS library, the mbedTLS, that sadly focus way too much on the bloody webservers but have no plan to implement proper S/MIME signing, because of course everybody makes mostly https  servers only on this embedded devices, sigh

Anyway, the files are messy as well, or they look so to somebody that doesn't have any specification, much less an architecture document on how this stuff should be organized for a new middleware package, or I wasn't able to find anything useful.
And the organization in these DB directories that have the update method by replacing the existing one with a new version, gahh.

Maybe wolfSSL as a company and partner will be able to get some stuff, eventually under NDA.

I've seen that Microchip seem to have a similar approach with FTL template files and even see in the wolf git repository an integration with something called Harmony, that seem to be a similar code generator with CubeMX, but I have no knowledge or experience with it, but maybe some work could be transferred to the ST framework.

In any case, if you need any help in testing the templates and even some programming, please don't hesitate to contact me when the work will start. The hardest part is making a sane concept and architecture, based on what CubeMX expects, but once started it will speed up nicely.

Best regards,
Mircea