Add mappings to support conversion of contents other than Mapdl commands

[anspcoinaud]

📝 Description of the feature

After testing conversion of other XML-Docbook contents, the conversion is successful but empty. It means the content types to be converted are ignored because not mapped to any output type.
My guess is we have to map every xml tag (here in blue) to a rst style for the output to be correct:

If possible, a .MD output would be preferable.

💡 Steps for implementing the feature

No response

🔗 Useful links and references

No response

[anspcoinaud]

@clatapie don't hesitate to ask for more details or anything that would help you along the way 😊

[anspcoinaud]

@clatapie hey :) Did you have a chance to have a look a this? I'm still figuring out how to migrate docbook contents to either RST or MD. Thanks!

[clatapie]

Hi @anspcoinaud!

In my opinion, this need might fit better in the creation of another project instead of adding directly this functionality in this package but it's an open discussion! I have the feeling that, as its goal is not the same one of this package, the difficulty on how to use it might increase.
Let me ping @RobPasMue, @germa89 and @MaxJPRey for visibility on that question.

In the meantime, let me contact you to talk about the way we could process.

[germa89]

As far as I understood, PyDita is a general purpose library. Hence we should not implement any logic specific to any documentation. We should provide PyDita as a dependency where you can build your own library to treat your own documentation set.

Having said that, PyDita should provide the tools to create this library, allowing custom rules, etc. If anything is needed for that purpose, please @anspcoinaud let us know.

[anspcoinaud]

Thanks @germa89
We are actively looking for a way to convert Docbook contents into either RST or MD, so that these contents can be migrated to the Developer Portal (which does not support docbook). I initially contacted Camille because it looks like what she did partly covers that need.