Merge branch 'main' into main

Author: nate-double-u

.cspell.yml

@@ -27,6 +27,7 @@ words:
   - Docsy
   - keda
   - kedacore
+  - nate
   - subpages
   - techdocs
   - toolkits

docs/netlify-domains-setup.md

@@ -7,16 +7,16 @@ cSpell:ignore: caniszczyk
 ## Netlify
 
 If a project already has its own Netlify instance, ask them to add
-[@caniszczyk][] as administrator. As a part of project onboarding, any billing
-information should be taken care of. If it isn't, ask them to open a
-[CNCF Service Desk](https://github.com/cncf/servicedesk) ticket.
+[@caniszczyk][] and [@nate-double-u][] as administrators. As a part of project
+onboarding, any billing information should be taken care of. If it isn't, ask
+them to open a [CNCF service desk][] ticket.
 
 If a project does not have a website, or is migrating from using GitHub pages to
 Netlify, create a new site for them under the CNCF Projects netlify instance.
 
 ### Netlify maintainers
 
-- Ensure that [@caniszczyk][] is an Owner.
+- Ensure that [@caniszczyk][] and [@nate-double-u][] are owners.
 - Contact the project and ask for **at least two** maintainers for Netlify. You
   will need their GitHub usernames. Add them either as Collaborators to specific
   sites (if in the CNCF Projects Netlify team) or as Collaborators for the
@@ -25,17 +25,16 @@ Netlify, create a new site for them under the CNCF Projects netlify instance.
 ## Domains
 
 If a project has a pre-existing domain, this should be transferred to the CNCF
-during their onboarding process.
+during their onboarding process. To transfer a domain, please open an [LF
+support desk][] ticket (Project Support Services → Domains & DNS → Transfer
+Domain(s)).
 
-If a project is new and does not have a domain name, they should open a
-[CNCF Service Desk](https://github.com/cncf/servicedesk) ticket to arrange for
-one.
+If a project is new and does not have a domain name, they should open a [CNCF
+service desk][] ticket to arrange for one.
 
 In most cases, we prefer to manage domains for project websites using Netlify
 DNS.
 
-At the moment, [@caniszczyk][] manages domain transfers.
-
 ### Netlify DNS domains
 
 When using Netlify DNS, we delegate the domain from another provider to Netlify
@@ -47,8 +46,7 @@ more.
 Some projects have more than one domain name and want all of them to point to
 their website. In this case, read
 [Multiple Domains](https://docs.netlify.com/domains-https/custom-domains/multiple-domains/)
-for more information, and ask them to open a
-[CNCF Service Desk](https://github.com/cncf/servicedesk) ticket.
+for more information, and ask them to open a [CNCF service desk][] ticket.
 
 ### Domains that don't point to Netlify websites
 
@@ -58,3 +56,6 @@ used for, among other things, email addresses.
 Issues related to these should be forwarded on to Linux Foundation IT staff.
 
 [@caniszczyk]: https://github.com/caniszczyk
+[@nate-double-u]: https://github.com/nate-double-u
+[CNCF service desk]: https://servicedesk.cncf.io/
+[LF support desk]: https://support.linuxfoundation.org/

docs/services.md

@@ -4,7 +4,7 @@ The CNCF provides technical writing and documentation website services for all
 its projects.
 
 All requests are subject to approval by the CNCF and should be submitted through
-the [CNCF service desk](https://servicedesk.cncf.io).
+the [CNCF service desk][].
 
 ## Docs assessment
 
@@ -38,6 +38,8 @@ Netlify installed/added to this repository A list of key maintainer(s) who
 should have access to Netlify A decision on whether your project will use CNCF’s
 CLA or Github’s DCO for committer verification.
 
+For more information, see [Netlify and domain setup](netlify-domains-setup.md).
+
 ## Techdocs office hours
 
 **What it is:** An hour long open meeting with CNCF’s technical writers where
@@ -113,3 +115,5 @@ statement of work for a contractor and plan accordingly.
 
 > Note: Longer technical writer engagements are subject to team availability and
 > CNCF priorities. Availability is not guaranteed.
+
+[CNCF service desk]: https://servicedesk.cncf.io/