Doc directory structure

.docs/content/2.Essentials/0.usage-on-x.md

@@ -0,0 +1,6 @@
+# How to use on X
+
+- General usage 
+- How to run on server?
+- How to run on client?
+- How to run on native app?

.docs/content/2.Essentials/1.targets.md

@@ -0,0 +1,13 @@
+# Targets
+
+When making an instance of the library using `makeProviders()`. It will immediately require choosing a target.
+
+::alert{type="info"}
+A target is the device where the stream will be played on.
+**Where the scraping is run has nothing to do with the target**, only where the stream is finally played in the end is significant in choosing a target.
+::
+
+#### Possible targets
+- **`targets.BROWSER`** Stream will be played in a browser with CORS
+- **`targets.NATIVE`** Stream will be played natively
+- **`targets.ALL`** Stream will be played on a device with no restrictions of any kind

.docs/content/2.Essentials/2.fetchers.md

@@ -0,0 +1,47 @@
+# Fetchers
+
+When making an instance of the library using `makeProviders()`. It will immediately make a fetcher.
+This comes with some considerations depending on the environment youre running.
+
+## Using `fetch()`
+In most cases, you can use the `fetch()` API. This will work in newer versions of Node.js (18 and above) and on the browser.
+
+```ts
+const fetcher = makeDefaultFetcher(fetch);
+```
+
+If you using older version of Node.js. You can use the npm package `node-fetch` to polyfill fetch:
+
+```ts
+import fetch from "node-fetch";
+
+const fetcher = makeDefaultFetcher(fetch);
+```
+
+## Using fetchers on the browser
+When using this library on a browser, you will need a proxy. Browsers come with many restrictions on when a web request can be made, and to bypass those restrictions, you will need a cors proxy.
+
+The movie-web team has a proxy pre-made and pre-configured for you to use. For more information, check out [movie-web/simple-proxy](https://github.com/movie-web/simple-proxy). After installing, you can use this proxy like so:
+
+```ts
+const fetcher = makeSimpleProxyFetcher("https://your.proxy.workers.dev/", fetch);
+```
+
+If you aren't able to use this specific proxy and need to use a different one, you can make your own fetcher in the next section.
+
+## Making a custom fetcher
+
+In some rare cases, a custom fetcher will need to be made. This can be quite difficult to do from scratch so it's recommended to base it off an existing fetcher and building your own functionality around it.
+
+```ts
+export function makeCustomFetcher(): Fetcher {
+  const fetcher = makeStandardFetcher(f);
+  const customFetcher: Fetcher = (url, ops) => {
+    return fetcher(url, ops);
+  };
+
+  return customFetcher;
+}
+```
+
+If you need to make your own fetcher for a proxy. Make sure you make it compatible with the following headers: `Cookie`, `Referer`, `Origin`. Proxied fetchers need to be able to write those headers when making a request.

.docs/content/2.Essentials/3.customize-providers.md

@@ -0,0 +1,5 @@
+# Customize providers
+
+- use makeProviders()
+- use buildProviders()
+- only use some providers

.docs/content/2.Essentials/4.using-streams.md

@@ -0,0 +1,4 @@
+# Using streams
+
+- How to use the outputs
+- file based streams VS hls

.docs/content/2.Essentials/_dir.yml

@@ -0,0 +1,2 @@
+icon: ph:book-open-fill
+navigation.redirect: /essentials/usage