Automattic / Automattic/studio

Feature Request: Allow custom domains that do not require .local TLD/extension

Open
#3,162 8 comments 1 reaction 0 assignees View on GitHub
Enhancement
Dominant language
TypeScript
Stars
517
Forks
95
Avg merge
1d 22h
Merged PRs (30d)
162

Description

### What

The custom domain functionality isn't truly custom. You have to use the .local TLD

### Why

Totally a personal preference, when I am developing plugins locally I'll spin up an install using the following format https://{namespace}.plugin in other local dev setups that do allow this. This is to differentiate between sites, plugins, apps, etc. Just a quality of life item

### How

Image

Contributor guide

Open the contributing guide

Research direction

Start by locating the custom-domain configuration and validation entry point in WordPress Studio, then review how the current .local requirement is enforced. Confirm the desired behavior by configuring a domain such as {namespace}.plugin and verifying that the local site starts and remains reachable without requiring the .local suffix.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop, networking
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.