.asf.yaml docn has moved

Author: sebbASF

content/pages/doc.md

@@ -21,7 +21,7 @@ Infra provides a library of resources that is constantly evolving to reflect the
 #### Source code ####
 - [Project source code repositories](version-control.html)
 - [Repositories for Maven releases and snapshots](repository-faq.html)
-- <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features" target="_blank">.asf.yaml features for Git repositories</a>
+- <a href="https://github.com/apache/infrastructure-asfyaml/blob/main/README.md" target="_blank">.asf.yaml features for Git repositories</a>
 - [GitHub Actions and Secrets](github-actions-secrets.html)
   - [GitHub Actions policy](github-actions-policy.html)
 

content/pages/infra-contact.md

@@ -155,7 +155,7 @@ That depends on your role and what you want to do. If this chart doesn't help, I
   <tr valign="top" style="border: 1px solid">
     <td style="padding:10px;border: 1px solid">create an <b>svnpubsub-based site</b></td>
     <td style="padding:10px;border: 1px solid">SVN URL of the compiled site (directory containing HTML files)</td>
-    <td style="padding:10px;border: 1px solid">For Git-based web sites, refer to <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features" target="_blank">Git-.asf.yaml features</a> for instructions on publishing.</td>
+    <td style="padding:10px;border: 1px solid">For Git-based web sites, refer to <a href="https://github.com/apache/infrastructure-asfyaml/blob/main/README.md" target="_blank">Git-.asf.yaml features</a> for instructions on publishing.</td>
   </tr>
   <tr valign="top" style="border: 1px solid">
     <td style="padding:10px;border: 1px solid">create a <b>project blog</b></td>

content/pages/project-blogs.md

@@ -7,7 +7,7 @@ If you're building your site via Pelican, Hugo, or another static site generator
 
 All project blogs should be accessible via $projectName.apache.org/blog. A blog can be a great way of announcing new milestones and features, sharing tips and tricks, and putting a "face" on your project for your developer and user communities. The project's PMC is responsible for the blog's content, and for granting write access to PPMC members.
 
-There are some resources available if you're using <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-BlogdeploymentserviceforGitrepositories" target="_blank">.asf.yaml</a> for blog deployment.
+There are some resources available if you're using <a href="https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#blog" target="_blank">.asf.yaml</a> for blog deployment.
 
 It is good practice to discuss the content of blog posts on the project's dev list before publishing.
 

content/pages/request-bug-tracker.md

@@ -33,7 +33,7 @@ github:
     projects: true
 ```
 
-You can review your .asf.yaml settings for Git at <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features" target="_blank">Git .asf.yaml features</a>.
+You can review your .asf.yaml settings for Git at <a href="https://github.com/apache/infrastructure-asfyaml/blob/main/README.md" target="_blank">Git .asf.yaml features</a>.
 
 ### Switching from Jira to GitHub Issue tracking