You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is information about how to run it locally in the [README](../README.md).
5
+
There are two types of Typedoc generated: user-facing (main) and developer-facing (dev).
6
+
The user-facing documentation is generated at `/typedoc`, and the developer-facing documentation is generated at `/typedoc/dev`.
7
+
The site is generated by the [CI here](../../.github/workflows/) under the job "pages". You can simulate that CI job with the script at `scripts/serve-static.sh`. This includes the demo and the Typedoc.
8
+
9
+
## How versioning works
10
+
11
+
Versioning is handled [this plugin](https://www.npmjs.com/package/@shipgirl/typedoc-plugin-versions).
12
+
[This CI script](../../ci/download-existing-docs.sh) downloads the previous Typedoc builds from the artifacts for all Scramjet releases with the latest from the package version.
The current doc you are reading is generated with [typedoc-plugin-markdown](https://github.com/ElektraInitiative/typedoc-plugin-markdown).
6
+
7
+
Typedoc documents all of the Scramjet APIs. Specifically, you are on the developer-facing documentation, so you will see APIs documented, which aren't exposed publicly in the package.
8
+
9
+
[**Switch to user-facing documentation**](/typedoc) to see what you actually need if you aren't a contributor, rather an implementor or someone interested in Scramjet.
You are currently on the user-facing documentation. This only documents APIs, which are exposed to you, so you can implement Scramjet into your site without having to worry about the internals of the library.
6
+
7
+
[**Switch to developer-facing documentation**](/typedoc-dev) to see all APIs used internally too.
0 commit comments