Convert .astro pages to mdx

Author: FileEX

web/src/pages/Contributing.mdx

@@ -1,14 +1,13 @@
 import AutoStarlightPage from '@src/components/AutoStarlightPage.astro';
 import { SITE_CONTRIBUTING_URL } from "@src/content.constants";
 
-<section data-pagefind-ignore>
-
 <AutoStarlightPage frontmatter={{
     template: 'doc',
     title: 'How you can help',
     tableOfContents: true
 }}>
 
+<section data-pagefind-ignore>
 Multi Theft Auto has loads of areas in which you can help us. In turn, we'll be more than happy to help you get started with any ideas you have, help test them and - if they're good enough - release them to the whole community.
 This page outlines the key areas you could do something in, of course, there are many things we've not thought of, so think outside the box!
 
@@ -45,5 +44,5 @@ Before you make changes check out [Contribution Guidelines](https://github.com/m
 ### Grant
 You can donate to MTA [here](https://multitheftauto.com/donate/manage.php).
 
-</AutoStarlightPage>
-</section>
+</section>
+</AutoStarlightPage>

web/src/pages/reference/Clothes_replacement.mdx

@@ -9,8 +9,6 @@ import { clothingModels, clothingTextures } from '@src/data/clothes_ids.ts';
     }
 }}>
 
-<div id="_top"></div>
-
 ### Replacing models (DFF)
 Starting with version **1.6.0 r22987**, CJ's clothing models can be replaced.
 ```lua
@@ -19,6 +17,7 @@ Starting with version **1.6.0 r22987**, CJ's clothing models can be replaced.
 local dff = engineLoadDFF("custom_afrobeard.dff")
 engineReplaceModel(dff, 30001)
 ```
+
 #### Model IDs and names
 <details>
   <summary>Full list of model IDs that are associated with CJ clothing models.</summary>

web/src/pages/reference/Dimension.astro

@@ -0,0 +1,51 @@
+import AutoStarlightPage from "@src/components/AutoStarlightPage.astro";
+import SeeAlsoSection from "@src/components/SeeAlsoSection.astro";
+import { getSeeAlsoLinksFromList } from "@src/utils/general";
+
+<AutoStarlightPage frontmatter={{
+  template: 'doc',
+  title: 'Dimension',
+  tableOfContents: false,
+}}>
+
+Dimensions are a way of separating parts of the game world from each other. Each dimension can contain elements of the types listed below. These are are only visible to players in the same dimension. You can, in theory, have up to 65535 dimensions.
+
+The following [Element](/reference/Element/) types can be used in the Dimension system:
+* [Player](/reference/player/)
+* [Ped](/reference/ped/)
+* [Vehicle](/reference/vehicle/)
+* [Object](/reference/object/)
+* [Pickup](/reference/pickup/)
+* [Marker](/reference/marker/)
+* [Collision shape](/reference/colshape/)
+* [Blip](/reference/blip/)
+* [Radar area](/reference/radararea/)
+* [Team](/reference/team/)
+* [Sound](/reference/sound/)
+* [Weapon](/reference/weapon/)
+* [Light](/reference/light/)
+* [Water](/reference/water/)
+* Custom dummy elements ([createElement](/reference/createElement/))
+
+The camera's dimension is updated when:
+* The local player joins the server (set to 0)
+* [resetMapInfo](/reference/resetMapInfo/) is called (set to 0)
+* The local player spawns (set to the player's dimension)
+* [setElementDimension](/reference/setElementDimension/) is called
+
+## Uses
+
+A useful use of this is for unique [interiors](/reference/Interior/). For example, there is only one actual Pizza restaurant in San Andreas, with each warp point going to the same place. This works fine in single player games (as you aren't going to be in two places at once), but with multiplayer this can be confusing, as you could enter in one place and see all the players who entered in another. To avoid this, you can split the players into dimensions, so they will only see players who entered in the same place, duplicating the Pizza restaurant interior as many times as you want with different dimensions.
+
+## Relevant scripting functions
+
+* [setElementDimension](/reference/setElementDimension/)
+* [getElementDimension](/reference/getElementDimension/)
+* [spawnPlayer](/reference/spawnPlayer/)
+
+<SeeAlsoSection seeAlsoLinks={getSeeAlsoLinksFromList([
+      'reference:Interior',
+      'reference:Entity',
+])} currentId='' />
+
+</AutoStarlightPage>

web/src/pages/reference/Dimension.mdx

@@ -0,0 +1,43 @@
+import StarlightPage from '@astrojs/starlight/components/StarlightPage.astro';
+import NoteBox from '@src/components/NoteBox.astro';
+
+<StarlightPage frontmatter={{
+    template: 'doc',
+    title: 'Filepath',
+    tableOfContents: false,
+}}>
+
+A `filepath` is a path that leads up to a file. These are relative to the root directory of the resource it is being called from.
+
+It is also possible to use special filepaths in order to reference files from other resources. This can be done with the following syntax:
+```text
+:<resourceName>/file.ext
+```
+
+So, for example:
+```lua
+xmlLoadFile ( ":helpmanager/help.xml" )
+```
+
+<NoteBox type='info'>Server side filepaths which refer to resources will work correctly even if the other resource is not running. However client side filepaths require the target resource to be running.</NoteBox>
+
+### Client file security
+
+To protect a client file from being read by another server, prepend the filepath with `@` when the file is created:
+```lua
+xmlCreateFile ( "@:myresource/someinfo.xml" )
+fileCreate ( "@listofthings.txt" )
+```
+
+To read a private file, `@` must also be prepended when the file is reopened:
+```lua
+xmlLoadFile ( "@:myresource/someinfo.xml" )
+fileOpen ( "@listofthings.txt" )
+```
+
+Notes:
+* The filepath without `@` is read/writeable by all servers.
+* The public and all the private versions of a particular filepath can exist at the same time. Which one is accessed depends upon the usage of `@` and the server that is currently connected.
+* The server file `mods/deathmatch/server-id.keys` is used for private file security. Keep a copy of it in a safe place!
+
+</StarlightPage>

web/src/pages/reference/Filepath.astro

@@ -0,0 +1,41 @@
+import AutoStarlightPage from "@src/components/AutoStarlightPage.astro";
+import SeeAlsoSection from "@src/components/SeeAlsoSection.astro";
+import { getSeeAlsoLinksFromList } from "@src/utils/general";
+
+<AutoStarlightPage frontmatter={{
+  template: 'doc',
+  title: 'Interior',
+  tableOfContents: false,
+}}>
+
+An interior in GTA is an area that isn't 'outside'. For example, inside houses, casinos, restaurants, shops etc. Players can not, by default, access these. You can use various scripting functions to move elements into these interiors. When you change the interior a player is in, they can only see the non-player elements in that interior. Players can see each other in whatever interior they are in.
+
+You can have up to 255 interiors, interior 0 being the first one and referring to the normal GTA world.
+
+The camera's interior is updated when:
+* The local player joins the server (set to 0)
+* [resetMapInfo](/reference/resetMapInfo/) is called (set to 0)
+* The local player spawns (set to the player's interior)
+* [setElementInterior](/reference/setElementInterior/) is called
+
+## Uses
+
+To allow a player to enter an interior, you should use the [setElementInterior](/reference/setElementInterior/) function on the player you wish to move. You can also use this function on other elements, for example to make a vehicle or object appear in the interior.
+
+## Dimensions
+
+The original GTA interiors are reused in a number of places throughout the game - e.g. each fast food restaurant interior is used many times. [Dimensions](/reference/Dimension/) are a feature that was added to MTA to solve this problem. You can allocate each instance of the interior a separate dimension which will mean that the players in each dimension won't be able to see each other or interact with each other. This will mean that the interiors appear to be entirely separate, despite physically being in the same place.
+
+## Relevant scripting functions
+
+* [setElementInterior](/reference/setElementInterior/)
+* [getElementInterior](/reference/getElementInterior/)
+* [spawnPlayer](/reference/spawnPlayer/)
+
+<SeeAlsoSection seeAlsoLinks={getSeeAlsoLinksFromList([
+      'reference:Dimension',
+      'reference:ID_Lists/Interiors',
+      'reference:Entity',
+])} currentId='' />
+
+</AutoStarlightPage>

web/src/pages/reference/Filepath.mdx

@@ -0,0 +1,29 @@
+import StarlightPage from '@astrojs/starlight/components/StarlightPage.astro';
+
+<StarlightPage frontmatter={{
+  template: 'doc',
+  title: 'Local Scheme Handler',
+  tableOfContents: false,
+}}>
+
+In many cases it is necessary to access files stored on the local disk from browsers.
+
+### Scheme format
+`http://mta/resourceName/file.extension`
+
+* **resourceName:** The [resource](/reference/resource/) name, local is a special name for the current resource.
+* **file.extension:** The file path within resourceName. Check [filepath](/reference/Filepath/).
+
+You can use this scheme format for [loadBrowserURL](/reference/loadBrowserURL/) as well as in HTML files e.g. `<img/>`; tags.
+
+### Examples
+##### Example 1
+
+`http://mta/myResource/assets/myImage.png` <br/>
+Refers to the file **assets/myImage.png** in a resource named myResource.
+
+##### Example 2
+`http://mta/local/assets/myImage.png` <br/>
+Refers to the file **assets/myImage.png** in the current resource.
+
+</StarlightPage>