[Discussion] Better code documentation and IDEs integration

[Naheulf]

Is your feature request related to a problem? Please describe. Even if this add-on is pretty good, being able to save stories from as many websites as possible has a huge drawback : the extension must be updated each time a site change it's structure or it's domain name. Requiring a huge burden on @dteviot as they is the main (and almost only) active dev on that project. ~~Some~~ few people are willing to help out a little one time trying to update the JavaScript (parser files) themselves. However being able to to it might be hard for people with little knowledge of JavaScript and almost no knowledge on how a web-extension works nor this extension work internally and a bad English level. However, this can prove difficult for people with little knowledge of JavaScript, a poor English level, almost no knowledge of how web extensions work and about as much knowledge of WebToEpub inner workings.

Describe the solution you'd like Even if it will be hard to address all those points, we can at east help for one of them : WebToEpub inner workings. Some IDE (ie: advanced text editors) can show contextual help for classes, variables and functions (behaviour, parameters and return value(s)). However, even if few of those IDEs claim to be "AI assisted", they are all silly and require JSDocs to show that help. That's why I suggest trying to document the code and make sure it's displayed correctly in the IDEs .And If I'm going to create docs (at least for me), I might as well share them.

Describe alternatives you've considered I can do it on my side only. (This will be easier for me as I won't have to translate it to English from my native language)

Additional context Aside the displayed help, some IDEs can also perform additional lookup and checks common errors/mistakes. Some of those checks are based on typescript engines and thus requires typescript configuration files to works