> For the complete documentation index, see [llms.txt](https://nuscwiki.gitbook.io/25-26/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nuscwiki.gitbook.io/25-26/student-life/directorates/communications.md).

# Communications

### NUS College Club Communications

### General Information & Objectives

A picture speaks a thousand words, so *n* pictures speak *n x 10^3* words?

Jokes aside, I think the current scope of NUSCC Comms is best explicated by exploring our past newsletters, circulars, and socials: Instagram @nus.nuscc, Flickr @nuscc.comms.

Do drop us a follow to access photos from NUSC events: download your cameos, relive memories, discover activities!

In all, we document and celebrate student life, as well as disseminate key updates pertaining to the NUSC community.

We cover the following major NUSC events:

* Start of Semester Dinners (SOSD)
* End of Semester Dinners (EOSD)
* Inter-Faculty and Inter-College (IFG and ICG respectively) Games
* Wednesdays at NUSC
* Artober

As well as other ad-hoc happenings.

<figure><img src="https://2564787905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyo8ELkYJLqXrgg0K2rsE%2Fuploads%2Fgit-blob-a416527c3f6c5523ad1c862443d4cf7135794502%2Fcommunications-01.jpg?alt=media" alt=""><figcaption></figcaption></figure>

*P.S. We execute the annual NUSC Club Photoshoot*

### Committee Structure

The Communications Team comprises the following sub-committees:

* Event Photographers: Yoyo, Yixuan, Will, Kevin
* Publicity & Design: Shaquilla, Estella, Michelle
* Writers: Javier, En Qi, Halyn, Sheuli

Directors: Livia (Event Photographers), Nicole (Publicity & Design), Jeremy (Writers)

<figure><img src="https://2564787905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyo8ELkYJLqXrgg0K2rsE%2Fuploads%2Fgit-blob-405375b2d83b9a23bdfbb9967830c5cee3f36638%2Fcommunications-02.jpg?alt=media" alt=""><figcaption></figcaption></figure>

###

### Reflections and Acknowledgements

As the service term of the 4th NUS College Club comes to a close, we wish to acknowledge and thank those who have journeyed with us:

* NUSC College Club Committees and Sub-committees for coordinating efforts to enliven and document our vibrant student life;
* 1<sup>st</sup>, 2<sup>nd</sup>, 3<sup>rd</sup> NUSCC Communications for laying the groundwork for our work.

And of course, the broader NUS College community.

Finally, we hope we have convincingly captured and memorialised the fervour of student life. There is no substitute for our fleeting four years here – the emotions and memories borne of which we trust we will carry with us into the next stage of our lives.

Sincerely yours,

The 4th NUSCC Communications Team


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://nuscwiki.gitbook.io/25-26/student-life/directorates/communications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
