> For the complete documentation index, see [llms.txt](https://utmwiki.rahbab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://utmwiki.rahbab.com/about-this-site/about.md).

# About

### Hey there!

I am Rahbab, and I'm the one managing this page you're on.\
\
Welcome to **UTM JBC** (UTM Johor Bahru Community) - a little side project I started to make life for fellow UTM students a bit easier (*and also perhaps because I like documenting stuff.*)

I’m just a student who got tired of being unable to find stuff/scattered contact details/outdated guides, and having to hear "*ask person x lah" or "idk"* every time I had a question.\
\
So, I decided to build a place where students can actually find what they need - perhaps think of it as the "Wikipedia" of UTM.

This site will always be fully free to access and free to contribute.

***

<h3 align="center"><i class="fa-check">:check:</i> <mark style="background-color:green;">What this site is</mark></h3>

* A **non-commercial**, student-run project - free to access and built purely for educational purposes.
* A **neutral platform** for sharing verified information from and for UTM
* A **collaborative space:** You're free to contribute!

<h3 align="center"><i class="fa-ban">:ban:</i> <mark style="background-color:red;">What this site isn’t</mark></h3>

* **Not** an official UTM website or service.
* **Not** affiliated, endorsed, or maintained by **Universiti Teknologi Malaysia**.
* **Not** a substitute for official announcements. Please refer to official UTM communication channels.

***

<h3 align="center"><i class="fa-phone">:phone:</i> Contact</h3>

<p align="center">For any inquiries, feel free to contact me me via: </p>

<p align="center"><strong>Email</strong> - utmjbc@gmail.com <br><strong>UTM JBC Discord -</strong> <a href="https://discord.gg/EJtnJ86Vzu"><strong>https://discord.gg/EJtnJ86Vzu</strong></a></p>

***

<h3 align="center"><strong>Disclaimer</strong></h3>

Licensed under the [**Creative Commons Attribution-ShareAlike 4.0 International License (CC BY-SA 4.0)**.](https://creativecommons.org/licenses/by-sa/4.0/)

> You are free to **share, adapt, and redistribute** the materials on this site, provided that proper **attribution is given** and any derivative works are distributed under the **same license**.

This website is an **independent, non-commercial student project**, and is **not affiliated with nor endorsed by Universiti Teknologi Malaysia (UTM) in any way whatsoever.**\
\
All references to “UTM” are made **solely for descriptive and informational purposes**, to identify the university relevant to the content of this website. \
\
Such use constitutes **good-faith descriptive use** as recognized under **Section 55(1)(b)** of the *Trade Marks Act 2019 (Malaysia)* \
[*https://www.myipo.gov.my/wp-content/uploads/2025/02/ACT-815-TRADEMARKS-ACT-201.pdf#page=58*](https://www.myipo.gov.my/wp-content/uploads/2025/02/ACT-815-TRADEMARKS-ACT-201.pdf#page=58)


---

# 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://utmwiki.rahbab.com/about-this-site/about.md?ask=<question>&goal=<endgoal>
```

`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.