> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.weltpixel.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to change Pearl Theme name to a Random theme name

Renaming the Pearl Theme is best done by creating a **child theme** that **extends Pearl** and giving that child a custom name. You can use Magento’s standard child theme approach or start from the child theme that ships with the Pearl Theme pack.

---

## 1) Copy the bundled child theme
Copy the provided child theme from  
`/app/design/frontend/Pearl/weltpixel_custom`  
to a new path, for example:  
`/app/design/frontend/MyTheme/my-theme/`

---

## 2) Update `theme.xml`
Edit: `/app/design/frontend/MyTheme/my-theme/theme.xml`

Change only the **title** so it shows your custom name in Admin. **Keep** the parent set to `Pearl/weltpixel`.

Theme XML values to set:
- `<title>Random Name Theme</title>`
- `<parent>Pearl/weltpixel</parent>`
- (optional preview) `<media><preview_image>media/preview.png</preview_image></media>`

> Do **not** change the parent. The child must continue to inherit from `Pearl/weltpixel`.

---

## 3) Update `registration.php`
Edit: `/app/design/frontend/MyTheme/my-theme/registration.php` and set your new theme path:

`'frontend/MyTheme/my-theme'`, `__DIR__`

(Full file should register the theme at the path `frontend/MyTheme/my-theme`.)

---

## 4) Assign the new theme in Admin
Go to **Content → Design → Configuration**, edit the desired scope (Global/Website/Store View), and select your **Random Name Theme**.

![Select the new theme in Admin](https://storage.crisp.chat/users/helpdesk/website/-/d/4/6/5/d465af7244cd5800/65b7577f-2cb8-4034-b035-e97c4a_1qlw42b.png)

---

## 5) Regenerate and clear caches
Open **System → Tools → Cache Management** and:
- Use **Regenerate Pearl Theme LESS/CSS files** (select the correct Store View).
- **Flush Magento Cache**.

---

## 6) Build static assets (CLI)
From your Magento root:

- (Optional for local/dev) switch to developer mode:  
  `php bin/magento deploy:mode:set developer`
- Deploy static content as needed (typically for production):  
  `php bin/magento setup:static-content:deploy -f`
- Flush cache:  
  `php bin/magento cache:flush`

> Tip: On production, you’ll generally stay in **production mode** and run the static content deploy after assigning the theme.

---

## 7) Verify on the storefront
Open your site and check the loaded assets:
- **Right-click → Inspect → View page source** and confirm CSS/JS paths include `frontend/MyTheme/my-theme`.

![Verify assets load from the new theme](https://storage.crisp.chat/users/helpdesk/website/-/8/4/9/b/849b7ea60e837000/8b165e12-d99f-408c-8f6d-863ab3_1tl46kp.png)

---

### Notes
- This approach **renames the child theme** only; Pearl remains the **parent** providing features and updates.
- Place your overrides/customizations inside `MyTheme/my-theme` to keep them **upgrade-safe**.