sktime · fkiraly · Sep 10, 2023 · Sep 10, 2023 · Sep 10, 2023 · Sep 10, 2023
diff --git a/docs/source/about/governance.rst b/docs/source/about/governance.rst
@@ -238,5 +238,5 @@ References
 Our governance model is inspired by various existing governance
 structures. In particular, we’d like to acknowledge:
 
-* `sktime’s governance model <https://www.sktime.org/en/latest/get_involved/governance.htmls>`_
+* `sktime’s governance model <https://www.sktime.net/en/latest/get_involved/governance.htmls>`_
 * `scikit-learn’s governance model <https://scikit-learn.org/stable/governance.html>`_
diff --git a/docs/source/about/history.rst b/docs/source/about/history.rst
@@ -25,4 +25,4 @@ If you are interested in contributing, check out our
 
 .. _scikit-learn: https://scikit-learn.org/stable/index.html
 .. _BaseEstimator API: https://scikit-learn.org/stable/developers/develop.html
-.. _sktime: https://www.sktime.org/en/stable/index.html
+.. _sktime: https://www.sktime.net/en/stable/index.html
diff --git a/docs/source/about/mission.rst b/docs/source/about/mission.rst
@@ -10,4 +10,4 @@ follow `scikit-learn`_ and `sktime`_ design principles.
 Our :ref:`roadmap` gives more details on how we try to achieve our mission.
 
 .. _scikit-learn: https://scikit-learn.org/stable/index.html
-.. _sktime: https://www.sktime.org/en/stable/index.html
+.. _sktime: https://www.sktime.net/en/stable/index.html
diff --git a/docs/source/about/roadmap.rst b/docs/source/about/roadmap.rst
@@ -33,4 +33,4 @@ We are also considering creating:
   package's testing interface.
 
 .. _scikit-learn: https://scikit-learn.org/stable/index.html
-.. _sktime: https://www.sktime.org/en/stable/index.html
+.. _sktime: https://www.sktime.net/en/stable/index.html
diff --git a/docs/source/conf.py b/docs/source/conf.py
@@ -178,9 +178,14 @@ def find_source():
             "icon": "fab fa-github",
         },
         {
-            "name": "Slack",
-            "url": "https://join.slack.com/t/skbase/shared_invite/zt-1qke3vzl2-fADjZBZadBlXsLUym5NlhA",  # noqa: E501
-            "icon": "fab fa-slack",
+            "name": "Discord",
+            "url": "https://discord.com/invite/54ACzaFsn7",
+            "icon": "fab fa-discord",
+        },
+        {
+            "name": "LinkedIn",
+            "url": "https://www.linkedin.com/company/scikit-time/",
+            "icon": "fab fa-linkedin",
         },
         {
             "name": "PyPI",
@@ -295,5 +300,5 @@ def find_source():
 intersphinx_mapping = {
     "python": ("https://docs.python.org/{.major}".format(sys.version_info), None),
     "scikit-learn": ("https://scikit-learn.org/stable/", None),
-    "sktime": ("https://www.sktime.org/en/stable/", None),
+    "sktime": ("https://www.sktime.net/en/stable/", None),
 }
diff --git a/docs/source/contribute/code_of_conduct.rst b/docs/source/contribute/code_of_conduct.rst
@@ -11,10 +11,10 @@ at all times.
 
 As an offshoot of the sktime project, we ask all members of the community to conform
 to the sktime project's
-`Code of Conduct <https://www.sktime.org/en/stable/get_involved/code_of_conduct.html>`_.
+`Code of Conduct <https://www.sktime.net/en/stable/get_involved/code_of_conduct.html>`_.
 
 If you need to report a Code of Conduct incident, reach out
-to Dr. Franz Király by email at f.kiraly@ucl.ac.uk.
+to Dr. Franz Király by email at franz.kiraly@sktime.net.
 
 .. note::
 

diff --git a/docs/source/contribute/development/developer_guide/git_workflow.rst b/docs/source/contribute/development/developer_guide/git_workflow.rst
@@ -8,7 +8,7 @@ Git and GitHub workflow
    If your not familiar with ``git`` you may want to start by reviewing
    `Git's documentation <https://git-scm.com/doc>`_ and then trying
    out the workflow. If you get stuck, chat with us on
-   `Slack <https://join.slack.com/t/sktime-group/shared_invite/zt-1cghagwee-sqLJ~eHWGYgzWbqUX937ig>`_.
+   `Discord <https://discord.com/invite/54ACzaFsn7>`_.
 
 The preferred workflow for contributing to ``skbase``'s repository is to
 fork the `main repository <https://github.com//sktime/skbase>`_ on GitHub,

diff --git a/docs/source/contribute/development/developer_guide/release_instructions.rst b/docs/source/contribute/development/developer_guide/release_instructions.rst
@@ -33,14 +33,14 @@ the month. To ensure releases go smoothly, the following steps are taken leading
 up to each release:
 
 1. 1 week before release date, update the release project board and alert
-   project contributors of upcoming release on slack.
+   project contributors of upcoming release on Discord.
 2. For major releases or substantial features, optionally extend the release cycle,
    if needed, so that the changes can be completed and incorporated in the release.
-   If a release will be delayed, notify project contributors on slack.
+   If a release will be delayed, notify project contributors on Discord.
 3. All changes to the main branch of the repository are frozen 1 day prior to the
    release. At this point only the release managers (for this release) should
    merge any pull requests. Remind core developers of the timing of the feature
-   freeze on slack when announcing the upcoming release date. Remind core developers
+   freeze on Discord when announcing the upcoming release date. Remind core developers
    of the feature freeze again 1 day prior to its start. Make sure to keep
    core developers in the loop if any delays or extensions to the feature freeze arise.
 4. If "must have" pull requests are not merged by the planned release date, the
@@ -106,7 +106,7 @@ The release process is as follows, on high-level:
    according to the install instructions (choose an arbitrary version/OS).
    If the install does not succeed or wheels have not been uploaded, urgent
    action to diagnose and remedy must be taken. All core developers should be
-   informed of the situation through mail-all in the core developer channel on slack.
+   informed of the situation through mail-all in the core developer channel on Discord.
    In the most common case, the install instructions need to be updated.
    If wheel upload has failed, the tag in 5. needs to be deleted and recreated.
    The tag can be deleted using the ``git`` command

diff --git a/docs/source/contribute/how_to_contribute.rst b/docs/source/contribute/how_to_contribute.rst
@@ -16,13 +16,13 @@ individuals looking to develop their skills.
 
 If you want to get started contributing, we recommend:
 
-- Say hello on `Slack`_
+- Say hello on `Discord`_
 - Use our :ref:`developer guide <dev_guide>` to setup a contributing environment
 - Pick a good first `issue <https://github.com/sktime/skbase/issues>`_
   to work on that will let you get familiar with our contributing process
 
 Once your first Pull Request is merged you may decide to continue contributing
-regularly. Talk with the development team on `Slack`_ about your interests and
+regularly. Talk with the development team on `Discord`_ about your interests and
 how you can best contribute to the project.
 
-.. _Slack: https://join.slack.com/t/sktime-group/shared_invite/zt-1cghagwee-sqLJ~eHWGYgzWbqUX937ig # noqa
+.. _Discord: https://discord.com/invite/54ACzaFsn7 # noqa
diff --git a/docs/source/user_documentation/installation.rst b/docs/source/user_documentation/installation.rst
@@ -196,7 +196,7 @@ References
 ----------
 
 The installation instruction are adapted from sktime's
-`installation instructions <https://www.sktime.org/en/stable/installation.html>`_.
+`installation instructions <https://www.sktime.net/en/stable/installation.html>`_.
 
 .. _Github repository: https://github.com/sktime/skbase
 .. _repository clone documentation: https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository