[Docs Site] Update pinned api-schemas commit#10
Closed
github-actions[bot] wants to merge 1 commit intoproductionfrom
Closed
[Docs Site] Update pinned api-schemas commit#10github-actions[bot] wants to merge 1 commit intoproductionfrom
github-actions[bot] wants to merge 1 commit intoproductionfrom
Conversation
…a25b3c6ec86d3f12566
Author
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
fb1337
pushed a commit
that referenced
this pull request
Mar 16, 2026
…shooting (cloudflare#28780) * [Registrar] Rewrite transfer page and add registration limits troubleshooting Restructure the transfer-domain-to-cloudflare page into two clear phases (add domain to Cloudflare, then transfer registration) instead of the previous flat 10-step list. Inline partials, add DNSSEC/nameserver provider links, explain why each step is needed, and add registration limits content with actionable guidance. Add new troubleshooting section for transfers rejected due to registration period limits (10-year max for most TLDs, 5-year for .co). Clarify vague language throughout: specific WHOIS status explanations, concrete 45-day expiration rule, ICANN contact-change lock details. * [Registrar] Simplify transfer timeline language in opening paragraph * [Registrar] Address PR review feedback and restore grace period transfer scenario - Break opening paragraph into scannable bullet list (#1) - Lead with action instead of comparison to other registrars (#2) - Replace IDN jargon with plain language and example (#3) - Lead with actionable advice in Restrictions block (#5) - Cross-link 'active on Cloudflare' to full-setup docs (#6) - Replace inlined DNSSEC links with dnssec-providers partial (#7) - Slim 'Add your domain' section to cross-link full-setup page (#8) - Reorder unlock section to put action before context (#9) - Restore 45-day grace period scenario with concrete date example and ICANN refund entitlement, matching FAQ content (#10) * [Registrar] Simplify transfer page, move details to troubleshooting - Simplify opening: shorter total time bullet, one-line prereq - Move Restrictions block content to troubleshooting page - Move registration limits and 'domain not available' Details blocks to troubleshooting page as standalone sections with full examples - Add 45-day grace period note in Before you begin with FAQ link - Update TLD page to link to troubleshooting instead of removed anchor - Simplify approve-transfer section for non-technical audience - Convert caution to note for Active status requirement - Make authoritative DNS requirement a bullet in Before you begin - Remove redundant 'Go to Transfer Domains page' text (DashButton CTA) * [Registrar] Restore auth code callout in opening note block
Author
|
Hey there, we've closed out this pull request because it's been stale for a while and there's been no additional action on it. If these changes are still relevant, open a new pull request (or flag to us in a GitHub issue). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the api-schemas commit reference to the latest version (669a09babe6cf7cf37d61a25b3c6ec86d3f12566).