> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/management/management-intro/sites-and-accounts.md).
# Sites & Accounts
These are all of the sites we use for Space Station 3D.
## [Our Website](https://ss3d.space/)
Developed on our "Website" GitHub repo (see GitHub section below).
The domain name is currently owned and paid for by **Grimmie** (or **Judge** on our Discord).
## Development
### [GitBook](https://ss3d.gitbook.io/home)
Most of our wiki and documents have been moved here.
### [GitHub](https://github.com/RE-SS3D/SS3D)
GitHub Repositories:
* **Art** - the repository for all of our art assets. This is helpful because we store the source files for the assets here, making them easier to edit in the future.
* **Website** - is what it sounds like, it's the repo for our website, which hosts our monthly devblog as well as various information and contribution guides.
* **CentCom** - is the repo for our central communications server, which manages user registration, authentication, and character storage, similar to what Byond is to SS13.
* **SS3D** - is our main repo which is the repo for the game itself as well as the implementation board (for technical tasks) and this wiki.
GitHub Owners:
* **CosmicCoincidence**
* **John**
* **Probably Not**
### [Trello](https://trello.com/ress3d)
Trello Boards:
* Management - used for management tasks.
* Ideas - used to store ideas about game systems or content.
* Models - 3d model tasks.
* Rig Models - 3d model tasks of models that will require rigging.
* Animations - tasks for 3d animations.
* 2D - for 2d graphic and texture tasks.
* VFX - tasks for visual effects like shaders.
* SFX - tasks for sound effects or music.
The Trello team consists of all of the members of the council. In addition, some more trusted contributed have write access on some boards (e.g. Konstantin3001 has access to the 2D board).
## Google
### Gmail
`ress3d.project@gmail.com`
Used for opening other accounts and general emails.
### [GoogleDrive](https://drive.google.com/drive/folders/16WCAVGAE_lPYF5l9avK2C0o045xNx0zI?usp=sharing)
GoogleDrive is used as a dropbox for submitted assets, which are then reviewed and prepared for use prior to being moved into the GitHub project. In addition, **CentCom** uses the GoogleDrive for hosting other things like artwork and documents.
***All assets saved here fall under our art license (***[***CC BY-NC-SA 4.0***](https://github.com/RE-SS3D/SS3D/blob/develop/Documents/LICENSE-ASSETS.md)***).***
### [YouTube](https://www.youtube.com/@spacestation3d)
For posting development tutorials, tests, new content, art, etc..
## Communities
### [Discord](https://discord.gg/94HwaZW)
Discord is the official method of communication for the SS3D community and devs. This includes posting WIP content for criticism and discussing game designs. There are also many people willing to help in various genres of game development.
**CentCom** members and mods moderate the Discord.\
**CosmicCoincidence** is the owner.
### [Reddit](https://www.reddit.com/r/RESS3D/)
Reddit is for posting announcements, memes, WIP, art, etc..
Currently owned by **Grimmie**, and moderated by various **CentCom** members.
### [Twitter](https://twitter.com/SpaceStation3D)
For posting devblogs and occasional funnies.
Mostly run by **ProbablyNot**.
## Financial
### [PayPal](https://www.paypal.me/SpaceStation3D)
PayPal is our monetary hub, all donations get funneled and recorded here prior to be distributed to project costs. When donating to the PayPal, you can use the link provided or send money directly to our email ()
### [Patreon](https://www.patreon.com/ss3d)
Where you can subscribe to us and donate a small amount each month. This money gets forwarded to the PayPal.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ss3d.gitbook.io/management/management-intro/sites-and-accounts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.