# App and docs

> Fill in your product's details and point DemoVexa at your app's code and docs so Claude writes accurate videos.

Source: https://demovexa.com/docs/workspaces/app-and-docs

The **General** and **App & docs** tabs in **Workspace settings** tell DemoVexa what your product is and where its code and docs are. Claude uses them when it writes briefs and scripts and when it builds videos.

To open them, click the workspace switcher in the sidebar and choose **Workspace settings**. Click **Save changes** after you edit.

## General

| Field | What it's for |
|---|---|
| **Product name** | The name used in scripts, cards and posts |
| **What it is** | A short description of the product |
| **Video language** | The default language for new videos. Each project can change it in its brief. See [Languages](/docs/more/languages). |
| **Audience** | Who the product is for |
| **Website** | Your product's website |
| **App address** | What the browser's address bar shows in animated videos |
| **End-card button** | The default call to action on the end card |

**Analyze with Claude** fills in the empty fields from your code. Anything you typed stays as it is. See [Workspaces](/docs/workspaces/overview#analyze-the-app-with-claude).

> [!TIP]
> Set **App address** to the address your users really see, so the browser bar in your videos looks like your app.

## App & docs

| Field | What it's for |
|---|---|
| **Code folder** | Your app's code. Click **Choose folder…** or paste the full path. DemoVexa checks it as you type. |
| **Docs folder** | Where your docs and how-to guides are. Enter a relative path, or leave it empty and DemoVexa finds it automatically. |
| **Detected stack** | The languages and frameworks DemoVexa found in the code |

The code folder can be in any language. DemoVexa only reads it and never changes anything in it.

If the folder is a git repository, the Ideas page uses its last 45 days of history to suggest videos about what you've shipped. See [Ideas](/docs/more/ideas).

### If the folder isn't accepted

| Message | What to do |
|---|---|
| Use the full path, e.g. /Users/you/code/app or C:\code\app (or click Choose folder). | Paste the full path, not a relative one, or use **Choose folder…** |
| That folder doesn't exist on this computer. | Check the path for typos, or pick the folder again |

On Linux, **Choose folder…** needs zenity or kdialog. See [Install](/docs/getting-started/install#linux-extras).

## How Claude uses your docs

Your how-to guides matter more than you might expect:

- When Claude writes a brief, it reads your how-to guides and lists them under "Based on:". With your Claude login, it also reads the app's code.
- On the **Modules** tab, a module shows "Guide: …" when a how-to guide matches it. See [Modules](/docs/workspaces/modules).
- The Ideas page suggests videos from your how-to guides, your modules and your git history.

The **Checks** tab includes a "Docs / how-to guides" check. See [Connections and checks](/docs/workspaces/connections-and-checks).

## Tips for docs that make good videos

- **Write one guide per task or feature.** A guide that walks through one job gives Claude one clear story to tell.
- **Name guides after what users do,** using the same words as your app's menus and buttons.
- **List the steps in order,** with the exact labels a user clicks. Clear steps make for clear scenes.
- **Say who the feature is for and why it helps.** That becomes the brief's audience and the one thing viewers should remember.
- **Keep numbers in your own hands.** Claude won't invent figures; put real ones in the brief under **Facts and numbers we can say**.

## Related

- [Modules](/docs/workspaces/modules)
- [Brand and design](/docs/workspaces/brand-and-design)
- [Brief](/docs/videos/brief)