chore: update templates to ory.com

Author: vinckr

templates/repository/common/.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -22,10 +22,10 @@ body:
             Guidelines](https://github.com/$REPOSITORY/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

templates/repository/common/.github/ISSUE_TEMPLATE/DESIGN-DOC.yml

@@ -33,10 +33,10 @@ body:
             Guidelines](https://github.com/$REPOSITORY/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

templates/repository/common/.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yml

@@ -26,10 +26,10 @@ body:
             Guidelines](https://github.com/$REPOSITORY/blob/master/CONTRIBUTING.md)."
           required: true
         - label:
-            "I have joined the [Ory Community Slack](https://slack.ory.sh)."
+            "I have joined the [Ory Community Slack](https://slack.ory.com)."
         - label:
             "I am signed up to the [Ory Security Patch
-            Newsletter](https://www.ory.sh/l/sign-up-newsletter)."
+            Newsletter](https://www.ory.com/l/sign-up-newsletter)."
     id: checklist
     type: checkboxes
   - attributes:

templates/repository/common/.github/ISSUE_TEMPLATE/config.yml

@@ -6,6 +6,6 @@ contact_links:
       Please ask and answer questions here, show your implementations and
       discuss ideas.
   - name: Ory Chat
-    url: https://www.ory.sh/chat
+    url: https://www.ory.com/chat
     about:
       Hang out with other Ory community members to ask and answer questions.

templates/repository/common/ADOPTERS.md

@@ -31,7 +31,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://openai.com/">openai.com</a></td>
-            <td><a href="https://www.ory.sh/case-studies/openai">OpenAI Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/openai">OpenAI Case Study</a></td>
         </tr>
         <tr>
             <td>Fandom</td>
@@ -42,7 +42,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://www.fandom.com/">fandom.com</a></td>
-            <td><a href="https://www.ory.sh/case-studies/fandom">Fandom Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/fandom">Fandom Case Study</a></td>
         </tr>
         <tr>
             <td>Lumin</td>
@@ -53,7 +53,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://www.luminpdf.com/">luminpdf.com</a></td>
-            <td><a href="https://www.ory.sh/case-studies/lumin">Lumin Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/lumin">Lumin Case Study</a></td>
         </tr>
         <tr>
             <td>Sencrop</td>
@@ -64,7 +64,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://sencrop.com/">sencrop.com</a></td>
-            <td><a href="https://www.ory.sh/case-studies/sencrop">Sencrop Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/sencrop">Sencrop Case Study</a></td>
         </tr>
         <tr>
             <td>OSINT Industries</td>
@@ -75,7 +75,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://www.osint.industries/">osint.industries</a></td>
-            <td><a href="https://www.ory.sh/case-studies/osint">OSINT Industries Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/osint">OSINT Industries Case Study</a></td>
         </tr>
         <tr>
             <td>HGV</td>
@@ -86,7 +86,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://www.hgv.it/">hgv.it</a></td>
-            <td><a href="https://www.ory.sh/case-studies/hgv">HGV Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/hgv">HGV Case Study</a></td>
         </tr>
         <tr>
             <td>Maxroll</td>
@@ -97,7 +97,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://maxroll.gg/">maxroll.gg</a></td>
-            <td><a href="https://www.ory.sh/case-studies/maxroll">Maxroll Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/maxroll">Maxroll Case Study</a></td>
         </tr>
         <tr>
             <td>Zezam</td>
@@ -108,7 +108,7 @@ that your company deserves a spot here, reach out to
                 </picture>
             </td>
             <td><a href="https://www.zezam.io/">zezam.io</a></td>
-            <td><a href="https://www.ory.sh/case-studies/zezam">Zezam Case Study</a></td>
+            <td><a href="https://www.ory.com/case-studies/zezam">Zezam Case Study</a></td>
         </tr>
         <tr>
             <td>T.RowePrice</td>

templates/repository/common/CODE_OF_CONDUCT.md

@@ -44,7 +44,7 @@ individual problems. If Ory open source software is used in production in a
 for-profit company or enterprise environment, we mandate a paid support contract
 where Ory is obligated under their service level agreements (SLAs) to offer a
 defined level of availability and responsibility. For more information about
-paid support please contact us at sales@ory.sh.
+paid support please contact us at sales@ory.com.
 
 ## Enforcement Responsibilities
 
@@ -70,7 +70,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[office@ory.sh](mailto:office@ory.sh). All complaints will be reviewed and
+[office@ory.com](mailto:office@ory.com). All complaints will be reviewed and
 investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

templates/repository/common/CONTRIBUTING.md

@@ -21,7 +21,7 @@
 
 _Please note_: We take Ory $PROJECT's security and our users' trust very
 seriously. If you believe you have found a security issue in Ory $PROJECT,
-please disclose it by contacting us at security@ory.sh.
+please disclose it by contacting us at security@ory.com.
 
 There are many ways in which you can contribute. The goal of this document is to
 provide a high-level overview of how you can get involved in Ory.
@@ -41,7 +41,7 @@ won't clash with Ory
 $PROJECT's direction. A great way to
 do this is via
 [Ory $PROJECT Discussions]($DISCUSSIONS)
-or the [Ory Chat](https://www.ory.sh/chat).
+or the [Ory Chat](https://www.ory.com/chat).
 
 ## FAQ
 
@@ -64,7 +64,7 @@ or the [Ory Chat](https://www.ory.sh/chat).
   [a Contributors License Agreement?](https://cla-assistant.io/$REPOSITORY)
 
 - I would like updates about new versions of Ory $PROJECT.
-  [How are new releases announced?](https://www.ory.sh/l/sign-up-newsletter)
+  [How are new releases announced?](https://www.ory.com/l/sign-up-newsletter)
 
 ## How can I contribute?
 
@@ -106,15 +106,15 @@ to help out:
 
 ## Communication
 
-We use [Slack](https://www.ory.sh/chat). You are welcome to drop in and ask
+We use [Slack](https://www.ory.com/chat). You are welcome to drop in and ask
 questions, discuss bugs and feature requests, talk to other users of Ory, etc.
 
 Check out [Ory $PROJECT Discussions]($DISCUSSIONS). This is a great place for
 in-depth discussions and lots of code examples, logs and similar data.
 
 You can also join our community calls if you want to speak to the Ory team
 directly or ask some questions. You can find more info and participate in
-[Slack](https://www.ory.sh/chat) in the #community-call channel.
+[Slack](https://www.ory.com/chat) in the #community-call channel.
 
 If you want to receive regular notifications about updates to Ory $PROJECT,
 consider joining the mailing list. We will _only_ send you vital information on
@@ -136,7 +136,7 @@ to add your example or Ory-related project to the awesome-ory README.
 ## Contribute code
 
 Unless you are fixing a known bug, we **strongly** recommend discussing it with
-the core team via a GitHub issue or [in our chat](https://www.ory.sh/chat)
+the core team via a GitHub issue or [in our chat](https://www.ory.com/chat)
 before getting started to ensure your work is consistent with Ory $PROJECT's
 roadmap and architecture.
 
@@ -205,7 +205,7 @@ instructions please head over to the Ory Documentation
 ## Disclosing vulnerabilities
 
 Please disclose vulnerabilities exclusively to
-[security@ory.sh](mailto:security@ory.sh). Do not use GitHub issues.
+[security@ory.com](mailto:security@ory.com). Do not use GitHub issues.
 
 ## Code style
 
@@ -247,4 +247,4 @@ community a safe place for you and we've got your back.
 
 We welcome discussion about creating a welcoming, safe, and productive
 environment for the community. If you have any questions, feedback, or concerns
-[please let us know](https://www.ory.sh/chat).
+[please let us know](https://www.ory.com/chat).

templates/repository/common/PROJECTS.md

@@ -18,7 +18,7 @@ dependencies (Java, Node, Ruby, libxml, ...).
 
 [Ory Kratos](https://github.com/ory/kratos) is an API-first Identity and User
 Management system that is built according to
-[cloud architecture best practices](https://www.ory.sh/docs/next/ecosystem/software-architecture-philosophy).
+[cloud architecture best practices](https://www.ory.com/docs/next/ecosystem/software-architecture-philosophy).
 It implements core use cases that almost every software application needs to
 deal with: Self-service Login and Registration, Multi-Factor Authentication
 (MFA/2FA), Account Recovery and Verification, Profile, and Account Management.

templates/repository/common/SECURITY.md

@@ -4,7 +4,7 @@ This policy outlines Ory's security commitments and practices for users across
 different licensing and deployment models.
 
 To learn more about Ory's security service level agreements (SLAs) and
-processes, please [contact us](https://www.ory.sh/contact/).
+processes, please [contact us](https://www.ory.com/contact/).
 
 ## Ory Network Users
 
@@ -50,4 +50,4 @@ processes, please [contact us](https://www.ory.sh/contact/).
 ## Reporting a Vulnerability
 
 For details on how to report security vulnerabilities, visit our
-[security policy documentation](https://www.ory.sh/docs/ecosystem/security).
+[security policy documentation](https://www.ory.com/docs/ecosystem/security).

templates/repository/library/.github/pull_request_template.md

@@ -24,7 +24,7 @@ Pull requests introducing new features, which do not have a design document link
 get merged.
 
 You can discuss changes with maintainers either in the Github Discussions in this repository or
-join the [Ory Chat](https://www.ory.sh/chat).
+join the [Ory Chat](https://www.ory.com/chat).
 -->
 
 ## Checklist
@@ -39,7 +39,7 @@ them, don't hesitate to ask. We're here to help! This is simply a reminder of wh
 - [ ] I have read the [security policy](../security/policy).
 - [ ] I confirm that this pull request does not address a security vulnerability. 
       If this pull request addresses a security vulnerability, 
-      I confirm that I got approval (please contact [security@ory.sh](mailto:security@ory.sh)) from the maintainers to push the changes.
+      I confirm that I got approval (please contact [security@ory.com](mailto:security@ory.com)) from the maintainers to push the changes.
 - [ ] I have added tests that prove my fix is effective or that my feature works.
 - [ ] I have added the necessary documentation within the code base (if appropriate).