• September 18, 2026
• admin

Do not place it here

Avoid putting the theme files directly into:

/public_html/

or:

/webdev.azuredevt.com/

like this:

webdev.azuredevt.com/
├── index.php
├── header.php
├── footer.php
├── assets/

That would mix theme files with WordPress core files and make future maintenance much harder.

Instead:

WordPress root
│
├── wp-admin/
├── wp-content/
│   ├── plugins/
│   ├── uploads/
│   └── themes/
│       └── azure-construction/
│
├── wp-includes/
├── wp-config.php
└── index.php

One important thing before activation

Because you’re testing the replacement theme, I recommend that webdev.azuredevt.com be a clone of your existing Azure WordPress website, not a completely blank WordPress installation.

The ideal setup is:

LIVE
azuredevt.com
    │
    └── current WordPress site
              ↓ clone
STAGING
webdev.azuredevt.com
    │
    └── same WordPress database/content/plugins
              +
       Azure new theme

This lets us see exactly what happens to:

• existing pages
• existing page URLs
• WordPress menus
• media
• plugins
• SEO metadata
• contact forms
• tracking codes
• redirects
• existing blog posts

when we activate the new theme.

If webdev.azuredevt.com is currently just a fresh WordPress installation, you can still install the theme now to inspect the design, but before final migration I’d clone the live website into it so we can test the theme against the real Azure content.

So at this stage: install the ZIP through Appearance → Themes on webdev.azuredevt.com, activate it there, and do not touch the production theme yet.