# Web3 Projects

Web3 Project is a structured org type for teams that need content generation grounded in project knowledge, not just freeform prompting. It turns project facts, positioning, and reusable answers into a live content system inside TheContentForge.

### Who it's for

Web3 Project is designed for protocol teams, ecosystems, token projects, and other Web3 orgs that need to publish consistently while staying accurate about product, roadmap, team, and narrative.

### What changes for a Web3 Project org

When an org is configured as **Web3 Project**, TheContentForge adds a structured project knowledge workflow on top of the normal social workspace:

* **Web3-specific onboarding** - extra setup screens for project profile, positioning, team, roadmap, and FAQs / objections
* **Project Knowledge in Settings** - a dedicated admin area for maintaining reusable project context
* **Summarize the project** in [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md) - a Web3-only generation mode grounded in approved project knowledge

This is additive. The rest of the product — Content Forge, Video Forge, Calendar, Publishing, Patterns, and the rest of the core workflow — still works the same way.

### Project Knowledge

For Web3 Project orgs, admins can maintain structured project context such as:

* **Project profile** - name, category, chain, website, docs, positioning, and account posture
* **Positioning** - differentiators, narratives to own, audience maturity, and topics to avoid
* **Team directory** - public team members used in spotlight or credibility content
* **Roadmap** - planned, in-progress, and completed roadmap items
* **FAQs & objections** - reusable answers, objection handling, and misconception correction

This content is meant to reduce drift, improve consistency, and make generation more trustworthy for project-native content.

### How Content Forge uses it

In Web3 Project orgs, Content Forge can generate from structured project context instead of relying on a one-off prompt alone.

The main Web3-specific workflow is **Summarize the project**, which produces a promo-grade X thread with IG/FB adaptations using approved project knowledge. Depending on what your org has configured, generation can draw from project profile, differentiators, team, roadmap, FAQs, approved supporting claims, and safe supporting assets.

That makes it easier to produce:

* project summaries
* roadmap or progress updates
* team or credibility posts
* FAQ / objection handling content
* educational or onboarding content grounded in the actual project

### Why this matters

Most generic AI workflows treat every project post like a fresh prompt. Web3 Project is different: it gives the system reusable structure, so the team can generate faster without losing the thread on what the project is, how it should be positioned, and what is safe to say repeatedly.

### Related

* [Onboarding Wizard](/thecontentforge-docs/getting-started/onboarding-wizard.md) - Web3 Project adds structured setup steps after core onboarding
* [Content Forge](/thecontentforge-docs/feature-guides/content-studio.md) - Includes the Web3-only **Summarize the project** mode
* [Asset Library](/thecontentforge-docs/feature-guides/asset-library.md) - Supporting docs and safe-to-use assets can strengthen generation inputs


---

# Agent Instructions: 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:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/web3-project.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.