> For the complete documentation index, see [llms.txt](https://rugzombie.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rugzombie.gitbook.io/docs/platform-changes-late-2022-2023/the-hub.md).

# THE HUB

The Hub is the central platform the DAO provides to the Web3 space. This will be an open source research platform that's goal is to create a safe and transparent space to onboard and navigate the Web3 ecosystem. Maintained by The Zombie DAO, the community is incentivise to keep The Hub populated with useful and high quality content.

#### Homepage

The homepage will contain relevant news and information within the space, content from the DAO[The Zombie DAO](/docs/platform-changes-late-2022-2023/the-zombie-dao.md#media-manager)and Writers, significant audits by community devs as well as digestible summaries by respected community members. This will contain info updates from Alliance projects as well as a research search engine to help navigate the plethora of information the DAO will be curating.

### Research Center

#### Alliances

This section will contain each Alliance project's info page and the necessary dashbaords project owners need to manage their page. Info pages will contain public forums for their communities to chat as well as recent audits, comments, summaries, video reviews, [investment knowledge quizzes](/docs/platform-changes-late-2022-2023/the-zombie-alliance.md#investment-quizes) and more. All this info will be used to determine an overall project rating.

#### Media

This will be the library of video content and articles created and ranked by the community.

### Voting Center

This will where decisions are made, influencing the DAO and platform as a whole. Through this dashboard Zombie Holders can vote on proposals or create new ones to improve the ecosystem overtime.

Read [The Zombie DAO](/docs/platform-changes-late-2022-2023/the-zombie-dao.md#proposals-and-voting) for more information.

#### User Profile / Task Center

This is a personalized page for Web3 users, it's associated with your wallet address and displays user info such as DAO roles, decentralized reputation, written audits, articles, comments and overall impact. This page will also show users their portfolio and show them relevant info based on their investments, including [investment knowledge quizzes](/docs/platform-changes-late-2022-2023/the-zombie-alliance.md#investment-quizes) to ensure users understand their investments.

Each user will be provide a list of daily tasks to complete in this section, read [New Rewards Model](/docs/platform-changes-late-2022-2023/new-rewards-model.md#task-farming) for more information.

#### Ecosystem health dashboard

A general dashboard displaying onchain metrics regarding the performance and health of the DAO and RugZombie ecosystem. This will start with the Zombie Token but dashboards for other projects will be created in the future.

* TVL & TVL distribution
* Holders
* DAO spending
* Grave engagement
* Other relevant stats added overtime


---

# 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://rugzombie.gitbook.io/docs/platform-changes-late-2022-2023/the-hub.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.
