@crosire I'm preparing a separate branch for the documentation so we can add it as a submodule or if you want or I'll clone it from inside github actions.I'll wait for an answer ^^

I've added the documentation as a submodule:https://github.com/nitanmarcel/scripthookvdotnet-doc which is a fork of the template used on the documentation.

Also I did some changes. The main page uses theGetting Started wiki page and the footer contains a link to the license which now will be generated as part of the website

Ah, sorry 🙃, I didn't mean it that drastic, was thinking that the template could have been a submodule to avoid adding all these files that have no relation to SHVDN. So a directory structure like this:

- docs   - docfx.json   - index.md   - toc.yml   - scripting_v2/      - index.md   - scripting_v3/      - index.md   - templates/      - darkfx/ submodule pointing towards https://github.com/steffen-wilke/darkfx (since you can have Git submodules in sub directories, see "-path" argument to git submodule add)      - memberpage/ submodule pointing towards where that came from

While adding the entire docs as a submodule may be advantageous too, the problem I'm seeing is that it breaks the link between the GitHub Actions script and the docs content. So would be better to keep those close together I think.

Ah, sorry 🙃, I didn't mean it that drastic, was thinking that the template could have been a submodule to avoid adding all these files that have no relation to SHVDN. So a directory structure like this:

- docs   - docfx.json   - index.md   - toc.yml   - scripting_v2/      - index.md   - scripting_v3/      - index.md   - templates/      - darkfx/ submodule pointing towards https://github.com/steffen-wilke/darkfx (since you can have Git submodules in sub directories, see "-path" argument to git submodule add)      - memberpage/ submodule pointing towards where that came from

While adding the entire docs as a submodule may be advantageous too, the problem I'm seeing is that it breaks the link between the GitHub Actions script and the docs content. So would be better to keep those close together I think.

Ok, I'll see what I can do about it. Also the memberspage is a nuget package and I don't think it's built in in docfx like the default template but I will check :)

Awesome work!!!

Awesome work!!!

Thanks. Anyway this will be pushed forward because I'm waiting for docFX v3 to come stable

I didn't care about web documentation too much until I received full access to do what I want without external approvals, but now it's good time for me to make a proper web documentation since we'll officially deprecate the v2 SDK/API in v3.7.0 (3.5 year passed since the first v3 release though). I'll make another PR when I create the official web docs.

I heard Lemon got annoyed for not a few people asking for how to use LemonUI in scripts built against v2 API (not v3), and I'm disappointed at the fact a lot of people (maybe more than the half of script devs on 5mods?) use v2 SDK/API for new scripts even they don't reference to other scripts built against v2 API, too. I'll be willing to create the official web documentation for API(s) if more people will have their scripts migrate to v3 SDK/API.

I totally forgot this existed. Oups xD