[Registrar] Rewrite transfer page and add registration limits troubleshooting#28780
Conversation
…shooting 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.
kodster28
left a comment
There was a problem hiding this comment.
Left some comments to address
|
/bonk review this PR for duplicative content and other potential issues |
There was a problem hiding this comment.
Agreeing with most of kodster28's feedback. Posting additional items below — 1 medium issue (missing partial content), 2 low issues, plus suggestions addressing some of the prior review comments.
The restructuring into two clear phases is a good approach, and the troubleshooting additions are solid. The anchor preservation (#disable-dnssec, #transfer-from-website-builders, #restrictions) checks out.
Note: The email-verification partial (Render file="email-verification" product="registrar") was removed in this rewrite. It warned users with unverified account emails that they cannot transfer or register domains. Consider adding that note back — either inline or in the "Before you begin" Details block.
|
Review submitted. Here is what I posted: Summary: 9 inline comments with suggestions, plus a top-level note about the removed Key items:
I also posted suggestions reinforcing kodster28's prior feedback (opening paragraph density, leading with actions, cross-linking instead of repeating content, and linking "active on Cloudflare" to the full-setup docs). |
…fer scenario - Break opening paragraph into scannable bullet list (cloudflare#1) - Lead with action instead of comparison to other registrars (cloudflare#2) - Replace IDN jargon with plain language and example (cloudflare#3) - Lead with actionable advice in Restrictions block (cloudflare#5) - Cross-link 'active on Cloudflare' to full-setup docs (cloudflare#6) - Replace inlined DNSSEC links with dnssec-providers partial (cloudflare#7) - Slim 'Add your domain' section to cross-link full-setup page (cloudflare#8) - Reorder unlock section to put action before context (cloudflare#9) - Restore 45-day grace period scenario with concrete date example and ICANN refund entitlement, matching FAQ content (cloudflare#10)
- 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)
Rewrites the "Transfer your domain to Cloudflare" page for clarity and adds registration limits content to the troubleshooting page. Follows up on #28723 (merged).
Transfer page (
transfer-domain-to-cloudflare.mdx):requirements,before-you-begin,restrictions) that were only used on this page.co), rejection reasons, TLD-specific requirements (.ai2-year minimum,.ukno extra year), and concrete actionable guidance with examplespcx_content_typefromtutorialtohow-toTroubleshooting page (
troubleshooting.mdx):.comwith 9.5 years must wait 6 months)clientHold/serverHold= suspended,redemptionPeriod= expired past grace,pendingDelete= scheduled for deletion)Preserves all existing anchors referenced by external pages:
#disable-dnssec,#transfer-from-website-builders,#restrictions.