Description
Is your feature request related to a problem? Please describe.
While the Python interface makes the management of elements and nodes a lot easier (mainly addressing the cross references), some other aspects are unnecessarily more complex than just raw .inp.
For example, when creating the material properties, the "keyword" based interface does not really treat the name of the material and the properties ("*ELASTIC") as one object (which is something that the .inp lacks) but relies on the order of keywords, essentially making it an additional layer of abstraction that is not much better than raw .inp yet in fact wordier.
Let alone there are still lots of unimplemented keywords.
Describe the solution you'd like
To simply insert .inp style code blocks as part of the model.model_keywords list.
Describe alternatives you've considered
A generic interface to insert arbitrary cards into the model.model_keywords lists using nested dictionaries and lists.
Or, implement all the unimplemented keywords.
Additional context