Yep, we should remove state and country names from the “site name” field.
A case of an early wrong direction on my part…“Tejon Ranch, CA”, “Gilroy, CA”, “Barstow, CA” seemed natural enough…there won’t ever be 1,382 sites in 35 distinct countries will there? Ha.
It is redundant in the database and isn’t actually necessary for the user interface. That is, the user interface should be able to display name/state/country where appropriate maybe even dynamically. On the changes page, for example, country could be included if no region/country was selected. We can maybe leave that for later, and plan on first taking state/country out of the name.
(1) Continue to edit/name sites as we currently do.
(2) Run SQL/script to remove state/country
(3) Deploy updated UI code that reproduces current UI by pulling fields from correct place.
(4) Switch to editors using only the site “name” in the “name” field – usually city, but sometimes city-suffix.
After that we have quite a few options about what gets displayed.
Logged this issue: https://github.com/kdwink/supercharge.info/issues/2