diff --git a/content/docs/api/index.mdx b/content/docs/api/index.mdx
new file mode 100644
index 0000000..e697c85
--- /dev/null
+++ b/content/docs/api/index.mdx
@@ -0,0 +1,23 @@
+---
+title: Pyrodactyl API
+description: Pyrodactyl API Documentation
+---
+
+
+ This section covers the Pyrodactyl API.
+
+
+
+ This section is a work in progress and is not complete. For more information, join our [discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support).
+
+
+The Pyrodactyl API allows you to interact with the Pyrodactyl panel programmatically. You can use it to manage servers, users, and other resources. From billing to server management, the API provides a wide range of functionalities.
+
+
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/elytra/configuration.mdx b/content/docs/elytra/configuration.mdx
new file mode 100644
index 0000000..f702a21
--- /dev/null
+++ b/content/docs/elytra/configuration.mdx
@@ -0,0 +1,6 @@
+---
+title: Configuring Elytra
+description: How to configure Elytra to work with your Pyrodactyl Panel
+---
+
+title
\ No newline at end of file
diff --git a/content/docs/elytra/index.mdx b/content/docs/elytra/index.mdx
index 53fe36c..748b2ba 100644
--- a/content/docs/elytra/index.mdx
+++ b/content/docs/elytra/index.mdx
@@ -25,3 +25,10 @@ Key Features and Changes:
Have something you want to see added to Elytra?
Make an issue on our [Github!](https://github.com/pyrohost/elytra/issues/new)
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/elytra/installation.mdx b/content/docs/elytra/installation.mdx
index 50dc82d..724d729 100644
--- a/content/docs/elytra/installation.mdx
+++ b/content/docs/elytra/installation.mdx
@@ -282,3 +282,9 @@ Once you've got your stuff working. your free to go
sudo systemctl enable --now elytra
```
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/admins/allocations.mdx b/content/docs/extra-info/admins/allocations.mdx
new file mode 100644
index 0000000..7d3b3ec
--- /dev/null
+++ b/content/docs/extra-info/admins/allocations.mdx
@@ -0,0 +1,13 @@
+---
+title: allocations
+description: Allocations & ports
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/admins/index.mdx.disabled b/content/docs/extra-info/admins/index.mdx.disabled
new file mode 100644
index 0000000..49b56df
--- /dev/null
+++ b/content/docs/extra-info/admins/index.mdx.disabled
@@ -0,0 +1,29 @@
+---
+title: Overview - Admin
+description: Admin Users Tasks & Abilities
+---
+
+
+
+ Add user accounts with & without admin permissions
+
+
+ Add locations to keep nodes orginzed
+
+
+ Add nodes to where servers are located
+
+
+ Creating serers & assigning them to a node
+
+
+ Creating ports & allocating them to servers
+
+
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/admins/locations.mdx b/content/docs/extra-info/admins/locations.mdx
new file mode 100644
index 0000000..99f8081
--- /dev/null
+++ b/content/docs/extra-info/admins/locations.mdx
@@ -0,0 +1,90 @@
+---
+title: Creating Locations
+description: Creating & Configuring locations
+---
+
+## What Is a Location?
+
+In Pyrodactyl a Location is a high–level grouping used to classify Nodes by geography, datacenter, or provider. It is purely organizational and does not itself run any workloads.
+
+## Location vs Node
+
+- Location: Logical label (no hardware, no allocations).
+- Node: Actual machine configuration (daemon, allocations, resource limits) that is assigned to exactly one Location.
+
+## Creating a Location
+
+1. Go to Admin Area > Locations.
+2. Click Create Location.
+3. Provide:
+ - Short Code: Concise identifier (e.g. us-nyc-1).
+ - Description (optional but recommended).
+4. Save.
+
+Short Codes should be:
+- Lowercase
+- Hyphen separated
+- Stable (avoid later renames if referenced externally)
+
+Examples: us-east, us-east-2, eu-fra, ap-sgp, edge-la, aws-usw-1, us.chicago.pyro
+
+## Assigning Nodes
+
+When adding or editing a Node select the desired Location. Reassigning a Node later does not affect servers functionally; it only updates grouping.
+
+## Editing & Renaming
+
+- You may edit description anytime.
+- Renaming the short code is safe internally but may break external automation that relies on the old code--audit before changing.
+
+## Deleting a Location
+
+- You must first move or remove all Nodes under it.
+- Deletion leaves servers intact (they live under their Nodes) but you cannot delete if any Node still references the Location.
+
+## Best Practices
+
+- Keep list small and meaningful (regions/providers, not every rack).
+- Use consistent pattern (region-city-number or provider-region).
+- Avoid embedding transient info (like temporary offers or hardware specs).
+- Document naming scheme for staff.
+
+## Common Mistakes
+
+| Mistake | Impact | Fix |
+|---------|--------|-----|
+| Too many granular Locations | Cluttered UI | Merge into broader regions |
+| Using Location to reflect hardware tier | Confusion | Use Node naming / descriptions instead |
+| Renaming without notice | Automation breakage | Maintain a mapping or avoid rename |
+
+## API Notes
+
+Locations are retrievable and manageable via the administrative API. Create Locations first, then post Nodes referencing the Location ID or short code (depending on endpoint requirements).
+
+## When to Add Another Location
+
+Add a new Location only if:
+- New geographic region introduced
+- New provider with distinct compliance / cost profile
+- You need a clear segregation boundary for reporting
+
+If it is just a new machine in an existing region/provider, add another Node--not a Location.
+
+## Quick Checklist
+
+- Does it represent a distinct region or provider? (Yes -> Location)
+- Will staff readily understand the code? (Yes -> Good)
+- Will it stay relevant for 6+ months? (Yes -> Proceed).
+
+
+
+
+
+After all of that you are done! Your location is made and now you can see it in the main locations page.
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/admins/nodes.mdx b/content/docs/extra-info/admins/nodes.mdx
new file mode 100644
index 0000000..3f2da3b
--- /dev/null
+++ b/content/docs/extra-info/admins/nodes.mdx
@@ -0,0 +1,186 @@
+---
+title: Creating Nodes
+description: Creating and configuring nodes
+---
+
+Don’t create a Node just to group servers--use naming/filters. If you must,
+use Locations for grouping (e.g., bedwars.provider).
+
+## When to Create a Node
+
+- When you have new hardware (VPS or Dedicated) to host more servers.
+- When you split one dedicated server into multiple virtual machines
+ (e.g., Proxmox or another hypervisor).
+
+## What is a Node?
+
+- A Node represents physical hardware running the Pyrodactyl Elytra
+ (or Pterodactyl Wings) daemon that hosts servers in containers.
+- Nodes define resource pools for CPU, Memory, Disk Space, IPs, and ports.
+
+## Node vs Location vs Server
+
+- Location: A grouping label (region/provider).
+- Node: Machine + daemon + resource/allocation pool; belongs to one Location.
+- Server: A user container consuming a slice of a Node’s resources and allocations.
+
+Tip: Don’t create a Node just to group servers--use naming/filters. If needed,
+use Locations for that.
+
+## Prerequisites
+
+- Domain name (optional, but required for SSL/TLS).
+- Daemon reachable (firewall open).
+- FQDN or IP ready (decide on SSL/reverse proxy).
+- SFTP/Docker dependencies installed as needed.
+
+## Terminology
+
+- Servers: The game servers you want to run (e.g., Minecraft, TF2).
+- VPS/Dedicated: The hardware hosting the game servers.
+- Nodes: Internal name to specify which hardware is used.
+- Location: The panel label to separate where nodes are physically hosted.
+
+## Creating a Node
+
+1. Admin Area > Nodes > Create Node.
+2. Fill out the fields and save.
+3. Add at least one IP/Port allocation.
+4. Assign or create servers for this Node.
+
+## Core Fields
+
+- General: Name, Description, Location.
+- Connectivity: FQDN/IP, Public Port (daemon, e.g., 8080), SFTP Port (e.g., 2022);
+ open firewall rules.
+- Resource Limits (totals for the Node): Total Memory, Disk, CPU; Over-Allocate %
+ for memory/disk/CPU.
+- Allocation/Ports: Default IP, additional IPs, add port ranges, remove unused ports.
+- Daemon Config: Base Path (e.g., /var/lib/pyrodactyl/servers), Behind Proxy,
+ Maintenance Mode, Backup directory/limits.
+- Security/Limits: Upload size, allowed archive extensions, default Docker images list,
+ reject stale daemon versions.
+- Advanced: Task timeout/graceful stop, container network mode, disk check strategy.
+
+## Editing a Node
+
+- Safe changes: Description, over-allocation values, add IPs/ports, Docker image list,
+ upload limits, Maintenance toggle.
+- Use caution: FQDN/IP, Public/SFTP ports (requires DNS/firewall updates and service restart),
+ Base Path (requires data migration).
+
+## Renaming
+
+- No runtime impact; may break external automation. Audit scripts first.
+
+## Resource Strategy
+
+- Memory/Disk: Reflect usable capacity minus OS; use modest over-allocation.
+- CPU: Sum of server CPU limits should respect Total CPU plus over-allocate margin.
+ Over-allocate lightly for bursty workloads (25–50%); avoid for consistently high usage.
+
+## Allocation Management
+
+- Workflow: Add IPs → add port ranges → servers consume ports → remove unused.
+- Best practices:
+ - Keep a 10–15% port buffer.
+ - Group port ranges by game type.
+ - Add aliases for multi-provider/NAT setups.
+
+## Deleting a Node
+
+- Move or delete all servers first, then clear allocations, then delete the Node.
+ There is no automatic migration.
+
+## Migration (High-Level)
+
+1. Create the new Node and ensure parity (images, versions, ports).
+2. Stop the server.
+3. Transfer files (rsync/backup/restore).
+4. Recreate on the new Node.
+5. Validate.
+6. Clean old allocations.
+
+## Monitoring & Health
+
+- Watch daemon heartbeat.
+- Track free allocations and over-allocation pressure (avoid >90% of physical).
+- Monitor disk usage and inodes.
+- Keep Docker images updated.
+
+## Common Mistakes (and fixes)
+
+- Setting Total Memory to full RAM → OOM risk → reserve 5–15% for the OS.
+- Excessive over-allocation (e.g., 200%) → performance issues → lower the ratio.
+- Missing firewall rules for daemon/SFTP → offline/errors → open and persist rules.
+- Mixing prod/test on the same Node → contention → separate or limit.
+- Deleting an IP before clearing allocations → stale errors → remove allocations first.
+- Skipping Maintenance before major changes → disruptions → enable Maintenance.
+- Changing Base Path carelessly → broken paths → plan migration/symlinks.
+
+## Best Practices
+
+- Use consistent naming (e.g., node-us-nyc-1); put hardware class in description.
+- Maintain a capacity sheet (total vs. allocated).
+- Prune unused ports; curate a minimal set of Docker images.
+- Use Maintenance Mode for daemon/kernel upgrades.
+
+## API Notes
+
+- Admin API: create/list Nodes, manage allocations, update limits, toggle maintenance.
+- Typical flow: POST Location → POST Node → POST allocations → POST servers (Node ID).
+ Validate daemon connection.
+
+## When to Add Another Node
+
+- Add when you have a new machine, sustained capacity >80% memory, isolation needs,
+ or different performance tiers.
+- Don’t add a Node just for a single new server or a different Docker image.
+
+## Quick Checklist
+
+- Daemon reachable; DNS/SSL/proxy correct; firewall open (daemon/SFTP).
+- Resource totals set minus OS; intentional over-allocation.
+- IPs added with an adequate port pool.
+- Docker images curated; monitoring/logs configured; backup strategy in place.
+
+## Capacity Review Tips
+
+- Memory: alert at 75%, plan at 85%.
+- Disk: alert at 70%, plan at 80%, emergency at 90%.
+- Ports: alert when <10% free.
+- CPU: check sustained 15m load vs. core count.
+
+## Troubleshooting
+
+- Node offline: check daemon service, TLS/proxy, and connectivity (nc/curl).
+- Can’t allocate ports: pool exhausted, IP missing, or port in use/firewalled.
+- Start fails (insufficient resources): over-allocation exceeded → adjust or migrate.
+
+## Glossary
+
+- Allocation: Reserved IP:Port.
+- Over-Allocate: Oversubscribe beyond physical resources.
+- Daemon: Background container manager.
+- Maintenance Mode: Blocks new actions; running servers continue.
+
+## Example Naming
+
+- node-us-east-1, node-eu-fra-2, node-ap-sgp-1, node-edge-la-1, node-aws-usw-1, us.chicago.pyro
+
+## Scaling
+
+- Vertical: increase Node resources (after hardware upgrade).
+- Horizontal: add another Node in the same Location.
+- Geographic: create a new Location and add a Node there.
+
+## Visual References
+
+- Nodes homepage, Create Node form, Node detail overview.
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
diff --git a/content/docs/extra-info/admins/servers.mdx b/content/docs/extra-info/admins/servers.mdx
new file mode 100644
index 0000000..1d03efd
--- /dev/null
+++ b/content/docs/extra-info/admins/servers.mdx
@@ -0,0 +1,117 @@
+---
+title: Creating Servers
+description: How to create and mannge a server
+---
+
+Creating servers is the fundamental part of using Pyrodactyl.
+
+After setting up your nodes and seeing a green beating heart, you can continue with setting up servers.
+
+## What is a Server?
+
+A server in Pyrodactyl is a containerized application instance that runs on a Node. It consumes a defined amount of resources (CPU, memory, disk, network allocations) from its assigned Node.
+
+## Prerequisites
+
+- At least one configured and online Node.
+- Available allocations (IP:Port combinations) on the chosen Node.
+- A valid Egg for the game or application you wish to run.
+
+## Creating a Server
+
+1. **Navigate to the Admin Area:** From your Pyrodactyl panel, go to `Admin Area` > `Servers`.
+2. **Click "Create New":** In the top right corner, click the "Create New" button.
+3. **Fill out the Server Details:**
+
+ - **Server Name:** A user-friendly name for your server (e.g., "My Minecraft Survival Server").
+ - **Server Owner:** Select the user who will own and manage this server.
+ - **Description (Optional):** A brief description of the server's purpose.
+ - **Node:** Choose the Node where this server will be deployed. Ensure the Node has sufficient resources and allocations.
+ - **Allocation:** Select an available IP:Port allocation from the chosen Node. This is how users will connect to your server.
+ - **Egg:** Select the appropriate Egg for the game or application (e.g., "Minecraft: Java Edition").
+ - **Nest:** The Nest associated with the chosen Egg will be automatically selected.
+
+4. **Configure Resources:**
+
+ - **Memory (MiB):** The maximum amount of RAM the server can use.
+ - **Swap (MiB):** The amount of swap space available. Set to `-1` for unlimited.
+ - **Disk Space (MiB):** The maximum amount of disk space the server can use.
+ - **CPU Limit (%):** The percentage of a single CPU core the server can use (e.g., `100` for one thread, `200` for two cores).
+ - **IO Weight:** Adjusts the I/O priority for the server (10-1000, default 500).
+
+5. **Configure Startup Parameters:**
+
+ - **Startup Command:** The command used to start the server. This is usually pre-filled by the Egg.
+ - **Service Variables:** Additional variables defined by the Egg that can be configured (e.g., server JAR file, difficulty).
+
+6. **Advanced Settings (Optional):**
+
+ - **Database Limit:** Maximum number of databases the server owner can create.
+ - **Allocation Limit:** Maximum number of additional allocations the server owner can create. (in the [network tab](/post-install/users/servers/network))
+ - **Backup Limit:** Maximum number of backups the server owner can create.
+ - **OOM Killer:** Enable or disable the Out-Of-Memory killer for this server.
+
+7. **Click "Create Server":** Once all details are filled, click the button to create the server.
+
+The server will now be provisioned on the selected Node. You can monitor its status and manage it from the server list.
+
+## Managing Servers
+
+Once a server is created, the user that is assigned the server can perform various management tasks:
+
+ Admins can still manage and access servers, they will apear under "other servers" when on the homepage of the panel
+
+
+- **Start/Stop/Restart:** Control the server's power state.
+- **Console:** View server logs and send commands.
+- **Files:** Access and manage server files via SFTP or the web interface.
+- **Databases:** Create and manage MySQL databases for the server.
+- **Schedules:** Set up automated tasks (e.g., daily backups, restarts).
+- **Network:** Manage additional IP allocations and port forwarding.
+- **Subusers:** Grant other users access to manage specific aspects of the server.
+- **Settings:** Modify server resource limits, startup parameters, and other configurations.
+- **Backups:** Create, restore, and manage server backups.
+
+## Best Practices
+
+- **Resource Allocation:** Allocate resources carefully. Over-allocating can lead to resource exhaustion on the Node, while under-allocating can cause server performance issues.
+- **Security:** Regularly update server software and use strong passwords for SFTP and database access.
+- **Backups:** Implement a regular backup strategy to prevent data loss.
+- **Monitoring:** Keep an eye on server resource usage and logs to identify and resolve issues proactively.
+- **Eggs:** Ensure you are using up-to-date and well-maintained Eggs for your applications.
+
+## Common Issues
+
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| Server won't start | Insufficient resources on Node | Check Node capacity and reduce server limits or add resources |
+| Port binding errors | Allocation already in use or bind IP incorrect | Use `0.0.0.0` as bind address, verify port is free on Node |
+| Out of Memory crashes | Memory limit too low for application | Increase memory allocation or enable swap |
+| Server stuck in "Installing" | Egg installation script failed | Check server logs, verify Egg is up-to-date |
+| Cannot connect to server | Firewall blocking ports or wrong allocation | Verify Node firewall rules allow the server's port |
+| SFTP connection fails | Wrong SFTP port or Node unreachable | Verify Node's SFTP port (default 2022) is open and correct |
+| Slow file uploads | Upload size limit too restrictive | Increase Node's upload size limit in settings |
+| Database creation fails | Database limit reached | Increase database limit or remove unused databases |
+| Startup command errors | Invalid variables or missing files | Review Egg configuration and service variables |
+| Backup fails | Insufficient disk space or backup limit reached | Free up disk space or increase backup limit |
+
+### Troubleshooting Tips
+
+- **Check Server Logs:** Most issues and their situations are in the server logs themselves.
+- **Verify Node Status:** Ensure the Node has a green heartbeat and correct resources.
+- **Review Egg Configuration:** Ensure the Egg is compatible with the application version you're trying to use.
+- **Resource Monitoring:** Use Node metrics to find resource bottlenecks (CPU, RAM, disk I/O).
+
+### When to Contact Support
+
+If you've verified all settings and the issue persists:
+- Check the [Common Issues](/common-issues/bind-issues) section for detailed troubleshooting guides.
+- Review [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support) for similar issues.
+- Gather server logs, Node status, and error messages before seeking help.
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
diff --git a/content/docs/extra-info/admins/users.mdx b/content/docs/extra-info/admins/users.mdx
new file mode 100644
index 0000000..9ecf43e
--- /dev/null
+++ b/content/docs/extra-info/admins/users.mdx
@@ -0,0 +1,13 @@
+---
+title: Adding Users
+description: Making a user account for your panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/index.mdx b/content/docs/extra-info/index.mdx
new file mode 100644
index 0000000..ecd31bb
--- /dev/null
+++ b/content/docs/extra-info/index.mdx
@@ -0,0 +1,37 @@
+---
+title: Extra info
+description: Post-installation configuration and setup guides.
+---
+
+# Extra Information
+
+This section covers Extra information that you might find helpful, everything here goes in alot more depth from basic usage and to confiuration and best Practices.
+
+
+
+
+
+ Add user accounts with & without admin permissions
+
+
+ Add locations to keep nodes orginzed
+
+
+ Add nodes to where servers are located
+
+
+ Creating servers & assigning them to a node
+
+
+ Creating ports & allocating them to servers
+
+
+
+
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/meta.json b/content/docs/extra-info/meta.json
new file mode 100644
index 0000000..a01081d
--- /dev/null
+++ b/content/docs/extra-info/meta.json
@@ -0,0 +1,6 @@
+{
+ "title": "Extra Info",
+ "description": "Extra Infomation that goes in depth about Pyrodactyl and Elytra",
+ "icon": "info",
+ "root": true
+}
diff --git a/content/docs/extra-info/users/account/index.mdx b/content/docs/extra-info/users/account/index.mdx
new file mode 100644
index 0000000..78d01c4
--- /dev/null
+++ b/content/docs/extra-info/users/account/index.mdx
@@ -0,0 +1,13 @@
+---
+title: User accounts
+description: Account pages, setting up MFA & SSH keys
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/index.mdx b/content/docs/extra-info/users/index.mdx
new file mode 100644
index 0000000..31313a8
--- /dev/null
+++ b/content/docs/extra-info/users/index.mdx
@@ -0,0 +1,13 @@
+---
+title: Overview - The user
+description: An overview of what the user can do and where things are as a logged in user.
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/activity.mdx b/content/docs/extra-info/users/servers/activity.mdx
new file mode 100644
index 0000000..52090fc
--- /dev/null
+++ b/content/docs/extra-info/users/servers/activity.mdx
@@ -0,0 +1,13 @@
+---
+title: Activity in the server
+description: Everything you need to know about the Activity section in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/databases.mdx b/content/docs/extra-info/users/servers/databases.mdx
new file mode 100644
index 0000000..c523a17
--- /dev/null
+++ b/content/docs/extra-info/users/servers/databases.mdx
@@ -0,0 +1,13 @@
+---
+title: Server Databases
+description: Everything you need to know about Database section in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/network.mdx b/content/docs/extra-info/users/servers/network.mdx
new file mode 100644
index 0000000..4a3994f
--- /dev/null
+++ b/content/docs/extra-info/users/servers/network.mdx
@@ -0,0 +1,13 @@
+---
+title: Server Network
+description: Everything you need to know about the Network section in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/scedules.mdx b/content/docs/extra-info/users/servers/scedules.mdx
new file mode 100644
index 0000000..f3c21d7
--- /dev/null
+++ b/content/docs/extra-info/users/servers/scedules.mdx
@@ -0,0 +1,13 @@
+---
+title: Scedules
+description: Everything you need to know about the Scedules section in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/settings.mdx b/content/docs/extra-info/users/servers/settings.mdx
new file mode 100644
index 0000000..f05f392
--- /dev/null
+++ b/content/docs/extra-info/users/servers/settings.mdx
@@ -0,0 +1,13 @@
+---
+title: Server Settings
+description: Everything you need to know about the Settings section in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/software.mdx b/content/docs/extra-info/users/servers/software.mdx
new file mode 100644
index 0000000..9b548f3
--- /dev/null
+++ b/content/docs/extra-info/users/servers/software.mdx
@@ -0,0 +1,13 @@
+---
+title: Server Software
+description: Everything you need to know about the Activity Software in the panel
+---
+
+text
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/extra-info/users/servers/subusers.mdx b/content/docs/extra-info/users/servers/subusers.mdx
new file mode 100644
index 0000000..8c953e0
--- /dev/null
+++ b/content/docs/extra-info/users/servers/subusers.mdx
@@ -0,0 +1,11 @@
+---
+title: Sub-users
+description: Everything you need to know about the Sub-users section in the panel
+---
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/meta.json b/content/docs/meta.json
index d3045b5..4b95b62 100644
--- a/content/docs/meta.json
+++ b/content/docs/meta.json
@@ -1,3 +1,3 @@
{
- "pages": ["pyrodactyl", "elytra"]
+ "pages": ["pyrodactyl", "elytra", "extra-info", "api"]
}
diff --git a/content/docs/pyrodactyl/blueprint/index.mdx b/content/docs/pyrodactyl/blueprint/index.mdx
new file mode 100644
index 0000000..7641a7b
--- /dev/null
+++ b/content/docs/pyrodactyl/blueprint/index.mdx
@@ -0,0 +1,12 @@
+---
+title: Blueprint
+description: Blueprint is a plugin system to allow for easy expansion of Pyrodactyl's functionality.
+---
+
+
+ This feature is currently in alpha and may not be stable. Use at your own risk.
+
+
+
+ This feature is not yet fully documented. Please refer to the [blueprint website](https://blueprint.zip)
+
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/common-issues/bind-issues.mdx b/content/docs/pyrodactyl/common-issues/bind-issues.mdx
index e8b575d..2445465 100644
--- a/content/docs/pyrodactyl/common-issues/bind-issues.mdx
+++ b/content/docs/pyrodactyl/common-issues/bind-issues.mdx
@@ -76,4 +76,10 @@ If the server starts successfully but you cannot connect:
sudo ufw allow /tcp
```
----
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/common-issues/domain.mdx b/content/docs/pyrodactyl/common-issues/domain.mdx
index 3fc5881..0acf00e 100644
--- a/content/docs/pyrodactyl/common-issues/domain.mdx
+++ b/content/docs/pyrodactyl/common-issues/domain.mdx
@@ -35,3 +35,11 @@ docker restart
Then, try your operation again. This should resolve most DNS-related connection failures.
+
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/config/egg-features.mdx b/content/docs/pyrodactyl/config/egg-features.mdx
index 2ffdccb..78c4bfe 100644
--- a/content/docs/pyrodactyl/config/egg-features.mdx
+++ b/content/docs/pyrodactyl/config/egg-features.mdx
@@ -34,3 +34,9 @@ The system will do it's best to auto match it to a loader found via the modrinth
`plugin/spigot`: Find plugins for Spigot Servers
`plugin/bungeecord`: Find plugins for Bungeecord proxies
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/config/envs.mdx b/content/docs/pyrodactyl/config/envs.mdx
index 37983e2..7b9b07b 100644
--- a/content/docs/pyrodactyl/config/envs.mdx
+++ b/content/docs/pyrodactyl/config/envs.mdx
@@ -337,3 +337,10 @@ description: Pyrodactyl Environment Variables
|----------|------|-------------|---------|
| `SLACK_BOT_USER_OAUTH_TOKEN` | `string` | Slack bot OAuth token. | - |
| `SLACK_BOT_USER_DEFAULT_CHANNEL` | `string` | Default Slack channel for notifications. | - |
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/config/index.mdx b/content/docs/pyrodactyl/config/index.mdx
index c8420fb..27bb160 100644
--- a/content/docs/pyrodactyl/config/index.mdx
+++ b/content/docs/pyrodactyl/config/index.mdx
@@ -12,3 +12,10 @@ description: Pyrodactyl Configurations
Environment Variables for pyrodactyl configuration
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/installation/community-install-guides.mdx b/content/docs/pyrodactyl/installation/community-install-guides.mdx
index 60ad778..293dff9 100644
--- a/content/docs/pyrodactyl/installation/community-install-guides.mdx
+++ b/content/docs/pyrodactyl/installation/community-install-guides.mdx
@@ -24,3 +24,10 @@ These guides are contributed by the community and may offer alternative installa
share it in our GitHub Discussions, or join our Discord community at
[discord.gg/FGWKZT5dxv](https://discord.gg/FGWKZT5dxv) for support!
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/installation/index.mdx b/content/docs/pyrodactyl/installation/index.mdx
index 6d2a80a..3698705 100644
--- a/content/docs/pyrodactyl/installation/index.mdx
+++ b/content/docs/pyrodactyl/installation/index.mdx
@@ -38,3 +38,10 @@ description: Learn how to get started with Pyrodactyl
Migrate your current Pterodactyl setup to Pyrodactyl.
+
+## Additional Resources
+
+- [Docker Documentation](https://docs.docker.com/)
+- [Pyrodactyl GitHub](https://github.com/pyrohost/pyrodactyl)
+- [Pterodactyl Documentation](https://pterodactyl.io/)
+- [Pyrodactyl Discord](https://discord.com/invite/FGWKZT5dxv?utm_campaign=pyrodactyl_support)
\ No newline at end of file
diff --git a/content/docs/pyrodactyl/meta.json b/content/docs/pyrodactyl/meta.json
index 591b886..d7c8ce3 100644
--- a/content/docs/pyrodactyl/meta.json
+++ b/content/docs/pyrodactyl/meta.json
@@ -1,8 +1,21 @@
{
"title": "Pyrodactyl",
- "description": "Pyrodactyl docs",
+ "description": "Docs for the Pyrodactyl game server panel",
"icon": "pyrodactyl",
- "pages": ["index", "changelog", "..."],
+ "pages": [
+ "index",
+ "changelog",
+ "automated",
+ "installation",
+ "config",
+ "local-development",
+ "migrations",
+ "subdomains",
+ "common-issues",
+ "---",
+ "Common Tasks",
+ "../common-tasks"
+ ],
"root": true,
"defaultOpen": true
}
diff --git a/content/docs/pyrodactyl/subdomains/cloudflare.mdx b/content/docs/pyrodactyl/subdomains/cloudflare.mdx
index 2c4c79f..7c02f07 100644
--- a/content/docs/pyrodactyl/subdomains/cloudflare.mdx
+++ b/content/docs/pyrodactyl/subdomains/cloudflare.mdx
@@ -4,11 +4,16 @@ description: Subdomains with Cloudflare
---
-You must get you api keys from the same spot as in the guide or it will **NOT** work
+ This guide only covers Cloudflare DNS provider, Other guides are still work in progress
## Creating a domain
+To create a domain first you need to goto the admin panel and at the top click on the `settings` text then the `domains` tab.
+
+fillout the fourm with correcct info you can find the template with the `edit:zone dns` by clicking [here](https://dash.cloudflare.com/profile/api-tokens)
+after you fill it out with the domain you want to use for subdomains copy your token at the end
+Then click the `Create Domain` button and fill out the form.
diff --git a/content/docs/pyrodactyl/subdomains/hetnzer.mdx b/content/docs/pyrodactyl/subdomains/hetnzer.mdx
new file mode 100644
index 0000000..7d91fcc
--- /dev/null
+++ b/content/docs/pyrodactyl/subdomains/hetnzer.mdx
@@ -0,0 +1,12 @@
+---
+title: Hetnzer Subdomains
+description: Subdomains with Hetnzer
+---
+
+
+ This guide only covers Hetnzer DNS provider, Other guides are still work in progress
+
+
+
+ This guide is a work in progress and may not be complete. Please refer to the [official documentation](https://docs.hetnzer.com/api/dns) for more information.
+
\ No newline at end of file
diff --git a/public/favicon.svg b/public/favicon.svg
new file mode 100644
index 0000000..946b0a0
Binary files /dev/null and b/public/favicon.svg differ
diff --git a/public/img/locations/locations-about.png b/public/img/locations/locations-about.png
new file mode 100644
index 0000000..ceb1478
Binary files /dev/null and b/public/img/locations/locations-about.png differ
diff --git a/public/img/locations/locations-creation.png b/public/img/locations/locations-creation.png
new file mode 100644
index 0000000..6a8ad09
Binary files /dev/null and b/public/img/locations/locations-creation.png differ
diff --git a/public/img/locations/locations-home.png b/public/img/locations/locations-home.png
new file mode 100644
index 0000000..feb55db
Binary files /dev/null and b/public/img/locations/locations-home.png differ
diff --git a/public/img/subdomains/domains-create.png b/public/img/subdomains/domains-create.png
new file mode 100644
index 0000000..c1334fb
Binary files /dev/null and b/public/img/subdomains/domains-create.png differ
diff --git a/public/img/subdomains/domains-home.png b/public/img/subdomains/domains-home.png
new file mode 100644
index 0000000..10fa95b
Binary files /dev/null and b/public/img/subdomains/domains-home.png differ
diff --git a/src/app/(home)/page.tsx b/src/app/(home)/page.tsx
index 074932a..fdde349 100644
--- a/src/app/(home)/page.tsx
+++ b/src/app/(home)/page.tsx
@@ -156,4 +156,4 @@ const Page = () => {
);
};
-export default Page;
+export default Page;
\ No newline at end of file
diff --git a/src/app/docs/[[...slug]]/page.tsx b/src/app/docs/[[...slug]]/page.tsx
index 9068a30..79e421d 100644
--- a/src/app/docs/[[...slug]]/page.tsx
+++ b/src/app/docs/[[...slug]]/page.tsx
@@ -1,4 +1,4 @@
-import { notFound } from 'next/navigation';
+import { notFound, redirect } from 'next/navigation';
import type { Metadata } from 'next';
import { DocsPage, DocsBody, DocsTitle, DocsDescription } from 'fumadocs-ui/page';
import { Tab, Tabs } from 'fumadocs-ui/components/tabs';
@@ -14,6 +14,12 @@ interface PageParams {
export default async function Page({ params }: PageParams) {
const { slug } = await params;
+
+ // Redirect /docs to /docs/pyrodactyl
+ if (!slug || slug.length === 0) {
+ redirect('/docs/pyrodactyl');
+ }
+
const page = await source.getPage(slug);
if (!page) {
@@ -57,7 +63,10 @@ export default async function Page({ params }: PageParams) {
}
export async function generateStaticParams() {
- return source.generateParams();
+ return [
+ { slug: [] }, // Include the /docs root path for static export
+ ...source.generateParams()
+ ];
}
export async function generateMetadata({ params }: PageParams): Promise {
diff --git a/src/app/docs/layout.tsx b/src/app/docs/layout.tsx
index 9b6f77f..cf98324 100644
--- a/src/app/docs/layout.tsx
+++ b/src/app/docs/layout.tsx
@@ -26,4 +26,4 @@ export default function Layout({ children }: { children: ReactNode }) {
{children}
);
-}
+}
\ No newline at end of file
diff --git a/src/app/layout.tsx b/src/app/layout.tsx
index 14c6066..60be16b 100644
--- a/src/app/layout.tsx
+++ b/src/app/layout.tsx
@@ -29,4 +29,4 @@ export default function Layout({ children }: { children: ReactNode }) {