# Before You Start

What WEEGLOO is and why you would use it is covered in [What is WEEGLOO?](/ai/what-is-weegloo.md). Building on that, this page is a single map showing what each of the pieces that make up WEEGLOO handles and how they fit together.

WEEGLOO is built from several functional axes: content modeling, publishing and delivery, multilingual support, collaboration, permissions, member authentication, deployment, integration, and AI. These axes sit on top of an enterprise-grade content management system (CMS) designed from the start to provide everything running a large-scale service requires. These pieces are not used once during the build and then set aside; you keep working with them in a content studio for as long as you operate your service. Each piece is covered here for its role only; the full concepts and how-to are handed off to the relevant section.

## The pieces that make up WEEGLOO {#the-pieces-that-make-up-weegloo}

### Workspace {#workspace}

Under your account, things are layered into *Organization* and *Space*. A *Space* is the working unit that holds content, members, and settings, and every task takes place within one *Space*. WEEGLOO does not use open sign-up; you start by becoming a *Space* member through an invitation.

- [How it works](/getting-started/core-concepts/common/how-it-works.md): covers the three-layer structure of account, *Organization*, and *Space*, and the flow by which what you create in the content studio is delivered externally.

### Content {#content}

You define content structure with a *Content Type*, the items that fill that structure are *Content*, and uploaded files such as images or videos are *Media*.

- [Content](/getting-started/core-concepts/content.md): covers the flow of shaping structure with a *Content Type* and filling it with *Content* and *Media*.

### Publishing and delivery {#publishing-and-delivery}

Content created in the content studio must be published before it is delivered externally. States such as *Draft* while you are still writing and *Published* once it goes live let you control when something is exposed.

- [States and publishing](/getting-started/core-concepts/common/states-and-versions.md): covers the states content can hold and what publishing changes.

### Multilingual {#multilingual}

Within a single *Content*, you manage values per language separately, serving each visitor in their own language.

- [Localization](/getting-started/core-concepts/content/localization.md): covers how to hold and manage multiple language values within a single *Content*.

### Collaboration {#collaboration}

You classify *Content* and *Media* across categories with *Tag*, and your team carries discussions forward through comments.

- [Collaboration](/getting-started/core-concepts/collaboration.md): covers how to work on content together using *Tag* classification and comments.

### Access and permissions {#access-and-permissions}

You invite members, define the scope of their permissions through roles, and issue tokens to control read access for external clients that do not log in.

- [Access and permissions](/getting-started/core-concepts/access-and-permissions.md): covers how to manage access with members, roles, and tokens.

### Service members {#service-members}

Separate from the operators who use the content studio, *ServiceLogin* is your own membership system that lets your product's users sign up and log in themselves.

- [Service members](/getting-started/core-concepts/service-users.md): covers *ServiceLogin*, which lets your product's users sign up and log in themselves, along with member permissions.

### Deployment and integration {#deployment-and-integration}

You deploy your frontend to the internet with *Web Hosting*, and integrate automatically with external services through *Webhook*.

- [Deployment and integration](/getting-started/core-concepts/deployment-and-integration.md): covers frontend deployment and integration with external services.

### Apps {#apps}

You package a finished configuration as a *Market App* to distribute on the marketplace, or pick one from the marketplace and install it into your own *Space*.

- [Market App](/getting-started/core-concepts/market-app.md): covers the flow of building and distributing a *Market App* or bringing one in and installing it.

### Using AI {#using-ai}

You can generate and transform content with AI, and automate repetitive tasks. How to use an LLM agent together with WEEGLOO MCP is covered in [MCP](/ai/tools/mcp.md).

## How the pieces fit together {#how-the-pieces-fit-together}

The pieces do not sit apart from one another; they connect into a single flow. Within a *Space*, you define structure with a *Content Type*, fill it with *Content* and *Media*, and once you publish, it is served to clients through the delivery API. On top of that, multilingual support, collaboration, permissions, members, deployment, integration, and apps all share the same workspace to form one service.

## What to do next {#what-to-do-next}

- [Quick Start](/getting-started/quick-start/intro-1.md): when you want to learn by building along in the content studio yourself.
- [Concepts & Features](/getting-started/core-concepts/common/how-it-works.md): when you want to understand step by step, with examples, what each feature is and how to use it.