# Finding Page/Component Slugs

Page and component slugs are unique identifiers used in Digia Studio to reference specific pages and components in your app. These slugs are essential when configuring actions that navigate between pages or reference components programmatically.

## What are Slugs?

Slugs are unique identifiers automatically generated for pages and components in Digia Studio. They consist of:

* **Base name**: Lowercase letters and numbers derived from the page/component name
* **Hyphens**: Used instead of spaces and special characters
* **Random suffix**: 6-digit random alphanumeric string appended for uniqueness

**Examples:**

* Page name: "User Profile" → Slug: `user-profile-a1b2c3`
* Component name: "Login Form" → Slug: `login-form-x9y8z7`

The random 6-digit suffix ensures that slugs remain unique even when multiple pages or components have similar names, preventing conflicts in your app.

## Why You Need Slugs

Slugs are required in various actions and configurations where you need to reference specific pages or components:

* **API calls**: Reference pages in routing configurations
* **Deep linking**: Direct links to specific pages
* **SDK Integration**: Navigate to pages using `DUIFactory().createPage(slug, args)` or `DUIFactory().createComponent(slug, args)`

## Finding Slugs

### Method 1: Pages/Coponent Slug

<figure><img src="/files/JuNKtT61kNI77X9U1XL1" alt="Copy Slugs"><figcaption><p>Copy Slug</p></figcaption></figure>

\*\[Screenshot: Pages Panel showing page names with slugs]\*

### Method 2: Custom Widget Slugs

*\[Screenshot: Properties Panel showing Page ID field]*

## Best Practices

### Naming Conventions

* Use descriptive, readable names that become good slugs
* Avoid special characters that might cause issues
* Keep slugs consistent with your app's

### Maintenance

* Document important slugs in your project documentation
* Use variables for frequently referenced slugs

## Troubleshooting

### Common Issues

**"Page not found" errors:**

* Verify the slug is spelled correctly
* Check if the page exists and is published

**"Component not found" errors:**

* Confirm the component slug is accurate
* Check if the component is properly configured

### Getting Help

If you can't find a slug:

1. Check the Pages Panel or Component Tree for the item
2. Verify the page/component exists and is not deleted
3. Contact your project administrator
4. Use the Digia Studio support channels
5. Review the component/page hierarchy carefully

## Related Documentation

* [Go To Page Action](/logic-and-interaction/actions/go-to-page.md) - Navigation between pages
* [Open Dialog Action](/logic-and-interaction/actions/open-dialog.md) - Display components as dialogs
* [Show Bottom Sheet Action](/logic-and-interaction/actions/show-bottom-sheet.md) - Display components in bottom sheets
* [Pages Overview](/ui-building-blocks/pages.md) - Understanding page structure and properties
* [SDK Integration Flutter](broken://pages/KvYi8BYZ9GRff1rXy4p3) - Using slugs in Flutter SDK integration

***

*Asset Placeholder: Tutorial video demonstrating how to locate and copy page/component slugs in Digia Studio*


---

# 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://docs.digia.tech/studio-workspace/builder-tool/finding-slugs.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.