# Community toolkit — your community inside your own site

> Bring an existing Estage community into a site Genesis built for you — feed, profiles, courses, challenges, video library, live broadcasts, stories, moderation and badges, all restyled to your brand.

Source: https://knowledge.estage.com/community/toolkit/
Part of the ESTAGE knowledge base (https://knowledge.estage.com). Full corpus: https://knowledge.estage.com/llms-full.txt

---
The [community portal](/community/) is a destination on its own address. The **Community toolkit**
is the other option: it renders your **existing Estage community inside a site Genesis built for
you**, screen by screen, in your own design.

:::note[Web apps only]
The toolkit needs a server, so it's available on [Web app](/platform/web-apps/) projects.
:::

## What you get

Every community screen, as part of your site:

| Area | What's there |
| --- | --- |
| **Feed & posts** | The activity stream, posting, and discussion |
| **Member profiles** | Who's in the community, and their profile pages |
| **Courses** | Courses with their lessons and downloadable resources |
| **Challenges** | Time-boxed activities members take part in |
| **Video library** | The community's videos |
| **Live broadcasts** | Live rooms with chat alongside them |
| **Stories** | Short-form updates |
| **Moderation queues** | The queues where you approve or reject what members post |
| **Badges & gamification** | Points, levels, and badges |

## Sign-in is handled by Estage

Members sign in through a **secure Estage login**. Their credentials never touch your site's
code — your build renders the community, it doesn't hold the passwords.

## It looks like your site, not like a template

The AI **restyles every community screen to match your brand** — the same way it styles the rest of
your site. Ask for changes to a community screen in chat, exactly as you would for any other page.

## Getting started

You need a community that already exists on Estage. If yours lives on the classic platform,
[import the legacy project](/community/legacy-import/) first — that's what binds your builder to
the right community, members, and content.

:::caution
The toolkit binding is one of the few things that **doesn't move** when you
[re-bind a project](/project-settings/general/#re-bind-to-another-estage-project) to a different
Estage project — set it up again on the new one.
:::