Hello,
I got some suggestions for LibreAutomate but first I want to explain what Dash docsets are.

Dash docsets

Dash docsets are a form fully offline documentation dumps in .tgz format (.tar.gz) that are made for example with HTTrack, then all remote links are turned into local ones.

If needed, Javascript cans be stripped and some CSS files removed.

Afterwards a table of contents, with function names, classes, etc is manually created.

It will actually behave as a bookmark list that jumps to the correct offline HTML page for the clicked item in the table of contents.

It's also useful for searching functions, classes & more in a single search bar, and getting all the matched results.

Dash docset viewers

Right now I know of only two docset viewers by the same developers (one is open-source, the other is commercial).

• Zeal (at https://zealdocs.org/) is the open-source version
• Velocity (at https://velocity.silverlakesoftware.com/) is the commercial version

Docset for the LibreAutomate API

I noticed that your project already has a DocFX documentation for the API & guides.

• https://github.com/qgindi/LibreAutomate/tree/master/Other/DocFX/_doc
  It also has toc.yml files in many folders which describe the 'sitemap' of the documentation.

Could it be possible for you to find a way to convert DocFX to a Dash docset?

This way we could be able to point a Dash docset viewer to a single link that refers to a .tgz file and your LibreAutomate reference would be available fully offline in a native documentation viewer.

Example of a Dash docset link for a single language/docset:

• https://zealusercontributions.vercel.app/api/docsets/AutoIt

<entry>
	<name>AutoIt</name>
	<version>3.3.14.0</version>
	<url>https://kapeli.com/feeds/zzz/user_contributed/build/AutoIt/AutoIt.tgz</url>
	<url>https://sanfrancisco.kapeli.com/feeds/zzz/user_contributed/build/AutoIt/AutoIt.tgz</url>
	<url>https://newyork.kapeli.com/feeds/zzz/user_contributed/build/AutoIt/AutoIt.tgz</url>
	<url>https://london.kapeli.com/feeds/zzz/user_contributed/build/AutoIt/AutoIt.tgz</url>
	<url>https://frankfurt.kapeli.com/feeds/zzz/user_contributed/build/AutoIt/AutoIt.tgz</url>
	<other-versions/>
</entry>

ASP.NET access

That one isn't of high priority in my list but it could be interesting.

If this was possible, perhaps having a new compiler output type of 'ASP.NET DLL' could generate a dummy DLL file that loads Au.dll, then AuCpp.dll.

Then the LibreAutomate API would more easily expose the ASP.NET CGI environment to a C# script.
That includes reading STDIN, outputting the HTTP response to STDOUT, reading environment variables etc.

There could be help on how to build the needed ASPX webpage & the web.config file, or LibreAutomate could generate good generic ones at compile time.

It would be a sort of PHP-like environment where global constants such as a _SERVER_NAME string, _HTTP_HEADERS string array & e.g. _QUERY_STRING string array & _REQUEST_BODY byte array could be exposed.

Could be useful for creating local HTTP APIs that need the help of native code.

I don't think that I will myself use this feature is implemented, not now, but it cans prove very useful later.

That's it for my suggestions (for now),
Thanks