Skip to content

Point configuration page links at 51degrees.com/configure - #311

Draft
jwrosewell wants to merge 1 commit into
rcfrom
chore/configure-address
Draft

jwrosewell wants to merge 1 commit into
rcfrom
chore/configure-address

Conversation

@jwrosewell

@jwrosewell jwrosewell commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Draft, do not merge yet

This pull request must stay a draft until https://51degrees.com/configure answers. It is to be released after the 51degrees.com website release that turns that address on, because the published documentation is served from 51degrees.com and its links to the configuration page become links within the same site.

What changed and why

The configuration page has moved from configure.51degrees.com to https://51degrees.com/configure. Every link and every mention of the old address in the documentation source now uses the new one.

  • https://configure.51degrees.com/<code> became https://51degrees.com/configure/<code>, with each key, sharing code, path and trailing slash kept exactly as written.
  • Link text and prose that said configure.51degrees.com now say 51degrees.com/configure.
  • Nothing else changed. The diff is 38 lines in 18 files, 68 replacements, one line out and one line in each time.
File Lines
src/devicedetection/features/robotstxt.md 1
src/devicedetection/features/useragentclienthints/overview.md 1
src/devicedetection/otherintegrations/uaparser.md 2
src/devicedetection/otherintegrations/wordpress.md 4
src/devicedetection/upgradingtoV4.md 8
src/humanconfidence/analytics.md 1
src/humanconfidence/cloud.md 1
src/humanconfidence/quickstart.md 1
src/integrations/googleanalytics.md 1
src/integrations/prebid.md 1
src/ipintelligence/quickstart.md 1
src/main.md 1
src/reversegeocoding/quickstart.md 1
src/services/cloud/errormessages.md 7
src/services/cloud/resourcekeys.md 1
src/services/cloud/robotstxt.md 1
src/services/configurator.md 4
src/snippets/example-require-resourcekey.txt 1

Wording

Every page touched for the address was read in full for the internal name of the place. It appears on those pages only in page identifiers, in the @configuratorexplanation alias (which is shown to readers as "Resource Key guide") and in image file names, so no sentence needed to change. The pages already say what the reader does, for example "Create a Resource Key at 51degrees.com/configure".

Base branch

rc, because changes to this repository are merged into rc and reach main in a "Release candidate" pull request (the only-rc-into-main workflow, and for example #309 into rc followed by #310 into main).

Campaign tags

None added. .utm-lint.json is { "mode": "forbid" }, so links to 51degrees.com in this repository carry no campaign tags.

What was left alone

  • The generated HTML on gh-pages, which the Build workflow regenerates from src/ once this reaches main.
  • Documentation generated from the API repositories, which is built from those repositories and is changed there.

How it was checked

  • A search of every file on rc for configure.51degrees.com, ignoring case, found 38 lines in the 18 files above before the change and none on this branch afterwards.
  • The comparison with rc shows 38 additions and 38 deletions and no other difference.
  • No build was run locally. The preview and campaign tag lint workflows run on this pull request.

Before marking ready

  1. Confirm https://51degrees.com/configure loads.
  2. Confirm a link with a code, for example https://51degrees.com/configure/AQRVdgJ-fPDE5gU130g, opens with its properties ticked.
  3. Confirm a link with a trailing slash, https://51degrees.com/configure/, loads.

The Cloud Configurator has moved from configure.51degrees.com to
https://51degrees.com/configure. Every link and mention in the
documentation source now uses the new address, keeping each link's key
or sharing code.
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview 👀

@jwrosewell jwrosewell changed the title Point Cloud Configurator links at 51degrees.com/configure Point configuration page links at 51degrees.com/configure Nov 12, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant