diff --git a/README.md b/README.md
index a1693e7dd05142259e7ba8a2cee12237249d5ec1..259dd8e844807f76b3a04361b0ef722ce5e0cae4 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@ Status updates for BeagleBoard.org's Google Summer of Code program.
 
 Primary resources:
 
-* [Forum](https://forum.beagleboard.org/c/gsoc)
+* [Forum](https://bbb.io/gsocml)
 * [Live chat](https://bbb.io/gsocchat)
 * [Project documentation template](https://gsoc.beagleboard.io/project-docs-template)
 
diff --git a/conf.py b/conf.py
index 9a81ae53ad6af51161c0a2e3e499493cc8802a3d..d0d2e123a421f425eccd7c7ed818fcbfd7d9853f 100644
--- a/conf.py
+++ b/conf.py
@@ -78,13 +78,13 @@ html_theme_options = {
         },
         {
             "name": "Discord",
-            "url": "https://discord.com/invite/e58xECGWfR",
+            "url": "https://bbb.io/gsocchat",
             "icon": "fa-brands fa-discord",
             "attributes": {"target": "_blank"},
         },
         {
             "name": "Forum",
-            "url": "https://forum.beagleboard.org/c/gsoc",
+            "url": "https://bbb.io/gsocml",
             "icon": "fa-brands fa-discourse",
             "attributes": {"target": "_blank"},
         },
diff --git a/guides/contributor.rst b/guides/contributor.rst
index 5c120fc579d9f570814464ebc2ea0b53b54e0815..95adb458ace21e8f69f95b314fba12f735667f99 100644
--- a/guides/contributor.rst
+++ b/guides/contributor.rst
@@ -12,11 +12,11 @@ General requirements
 
 All projects have the following basic requirements:
 
-1. Contributors must create accounts on `OpenBeagle <https://openbeagle.org/>`_, `Discord <http://bbb.io/gsocchat>`_ and `Beagle Forum <http://bbb.io/gsocml>`_ prior to creating their application.
+1. Contributors must create accounts on our `OpenBeagle <https://openbeagle.org/>`_, `Discord <https://bbb.io/gsocchat>`_ and `Beagle Forum <http://bbb.io/gsocml>`_ prior to creating their application.
 2. All newly generated materials must be released under an `open source license <http://www.opensource.org/licenses>`_. Individual contributors shall retain copyright on their works.
-3. Contributors will demonstrate their ability to cross-compile and utilize version control software by creating a “Hello World” application and generating a pull request to `jadonk/gsoc-application <https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner>`_. For assistance, please visit `Discord <http://bbb.io/gsocchat>`_ or utilize the `Beagle Forum <http://bbb.io/gsocml>`_. The “Hello World” application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
+3. Contributors will demonstrate their ability to cross-compile and utilize version control software by creating a “Hello World” application and generating a pull request to `jadonk/gsoc-application <https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner>`_. For assistance, please visit our `Discord <https://bbb.io/gsocchat>`_ or utilize the `Beagle Forum <http://bbb.io/gsocml>`_. The “Hello World” application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
 4. All projects will produce reusable software components and will not be “what–I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <https://www.beagleboard.org/>`_ community.
-5. Contributors will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <gsoc-proposal-template>` and utilizing `Discord <http://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <https://www.beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
+5. Contributors will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <gsoc-proposal-template>` and utilizing our `Discord <https://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <https://www.beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
 6. Source code generated during the project must be released on OpenBeagle (and we’ll setup a mirror on `Github.com <http://github.com/>`_).
 7. Contributors will provide two recorded audio/video presentations uploaded to Youtube or Vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found on `http://beagleboard.org/gsoc <http://beagleboard.org/gsoc>`_. There is no requirement to show your faces or use English.
 
@@ -37,8 +37,8 @@ All projects have the following basic requirements:
 Student proposals can encompass projects based on the :ref:`ideas page <gsoc-project-ideas>`  or can include personal project ideas, 
 but should be focused on generating a sustainable and reusable open source software component. Previous Google Summer of Code projects show 
 that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even 
-if it is not on this list. We will be glad to help contributors develop ideas into projects via `Discord <http://bbb.io/gsocchat>`_ 
-and `Forum <https://forum.beagleboard.org/c/gsoc>`_. There are many potential project ideas and we will match contributors to projects 
+if it is not on this list. We will be glad to help contributors develop ideas into projects via our `Discord <https://bbb.io/gsocchat>`_ 
+and `Forum <https://bbb.io/gsocml>`_. There are many potential project ideas and we will match contributors to projects 
 based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.
 
 .. tip::
diff --git a/guides/mentor.rst b/guides/mentor.rst
index ed4bae63b0b85a2859faf44a73cd8330cf362686..746d438297988711bad19d95f5839765220f61bc 100644
--- a/guides/mentor.rst
+++ b/guides/mentor.rst
@@ -23,15 +23,15 @@ In addition to providing GSoC contributors with feedback and pointers, a mentor
 GSoC contributors integrate into their project’s community. `BeagleBoard.org <https://www.beagleboard.org/>`_ 
 assign more than one mentor to each of their GSoC contributors. Many members of `BeagleBoard.org <https://www.
 beagleboard.org/>`_ community also provide guidance to GSoC contributors without mentoring in an “official” 
-capacity, as much as they would answer anyone’s questions on `Discord <http://bbb.io/gsocchat>`_ and 
-`Forum <https://forum.beagleboard.org/c/gsoc>`_.
+capacity, as much as they would answer anyone’s questions on our `Discord <https://bbb.io/gsocchat>`_ and 
+`Forum <https://bbb.io/gsocml>`_.
 
 .. note:: 
     Official mentors can use :ref:`gsoc-project-ideas` page as template for providing their own project ideas. 
     Remember these are supposed to be for software projects that service the Beagle and general open source 
     embedded systems community, not theses, how-to guides or what I did over my summer vacation ideas.
 
-Prospective mentors, sudents will use `Discord <http://bbb.io/gsocchat>`_ and `Forum <https://forum.beagleboard.org/c/gsoc>`_ 
+Prospective mentors, sudents will use our `Discord <https://bbb.io/gsocchat>`_ and `Forum <https://bbb.io/gsocml>`_ 
 to make contact with you, so be sure to provide up-to-date information. Please feel free to add yourself on mentors page and we will monitor 
 and police that list. Acceptance as an official mentor with the ability to rate proposals and grade contributors will come via the Google system. 
 We will only approve official mentors who have a prove track record with Beagle, but welcome all community members to provide guidance to both 
diff --git a/guides/proposal.rst b/guides/proposal.rst
index 717645e9f33031214cdd46521c35aa7c5c39e2f5..e74364cc7ff9ee5bcaad67b8891fe8f267e0f8ff 100644
--- a/guides/proposal.rst
+++ b/guides/proposal.rst
@@ -19,14 +19,14 @@ not be accepted by any organization participating in GSoC. Unsuccessful proposal
 1. Try to pass off previous school projects as something to do for GSoC. The work has already done, and the project often has very little to do with `BeagleBoard.org hardware <https://www.beagleboard.org/boards>`_.
 2. Roughly a half page of “proposal” that is submitted shortly before the submission deadline. These proposals are usually little more than a name, contact information, and a statement of “I will work hard.”
 3. A generic proposal that was sent to every other GSoC org that has very few details on deliverables or schedule.
-4. A project idea that was never talked about to the `BeagleBoard.org <https://www.beagleboard.org/>`_ mentors in `Discord <http://bbb.io/gsocchat>`_ or in `Forum <https://forum.beagleboard.org/c/gsoc>`_. The proposal was submitted without ever “meeting” the Beagle community.
+4. A project idea that was never talked about to the `BeagleBoard.org <https://www.beagleboard.org/>`_ mentors in our `Discord <https://bbb.io/gsocchat>`_ or in `Forum <https://bbb.io/gsocml>`_. The proposal was submitted without ever “meeting” the Beagle community.
 
 In order to be successful, a proposal has to be relevant to `BeagleBoard.org <https://www.beagleboard.org/>`_, a proposal 
 topic that the mentors recognize (either from being proposed on :ref:`gsoc-project-ideas` page or from the topic being 
-discussed on our `Discord <http://bbb.io/gsocchat>`_ or in `Forum <https://forum.beagleboard.org/c/gsoc>`_), and sufficiently 
+discussed on our `Discord <https://bbb.io/gsocchat>`_ or in `Forum <https://bbb.io/gsocml>`_), and sufficiently 
 detailed that the mentors know exactly what you’ll be creating and when it will be done. Successful proposals are also almost 
-always shown to mentors via Discord or IRC well before the submission deadline so that the mentors can comment on it and offer 
-suggestions that improve the proposal.
+always shown to mentors via our `Discord <https://bbb.io/gsocchat>`_ or `Forum <https://bbb.io/gsocml>`_ well before the 
+submission deadline so that the mentors can comment on it and offer suggestions that improve the proposal.
 
 .. tip::
    Start your proposal early, speak with the mentors often, and dedicate an appropriate amount of time to both thinking 
@@ -41,7 +41,7 @@ To make the project proposal writing process easier for all the GSoC contributor
     Start with :ref:`gsoc-contribution-guide` to simplify the proposal writing process using OpenBeagle CI. It's always recommended to create a fork 
     of `gsoc.beagleboard.io repo on OpenBeagle <https://openbeagle.org/gsoc/gsoc.beagleboard.io>`_ and clone on your local machine. Instruction for 
     setting up Sphinx on local machine are also provided on :ref:`gsoc-contribution-guide`. For any query you can reach out on 
-    `Discord <http://bbb.io/gsocchat>`_ or `Forum <https://forum.beagleboard.org/c/gsoc>`_.
+    our `Discord <https://bbb.io/gsocchat>`_ or `Forum <https://bbb.io/gsocml>`_.
 
 You can either open your cloned `gsoc.beagleboard.io repo <https://openbeagle.org/gsoc/gsoc.beagleboard.io>`_ using Visual Studio Code on your local machine or use OpenBeagle Web IDE. Now, follow steps below to write your proposal,
 
@@ -51,7 +51,7 @@ You can either open your cloned `gsoc.beagleboard.io repo <https://openbeagle.or
 4. Check rendered version of your proposal on OpenBeagle pages, to view a rendered version of your updates you can go to ``<username>.beagleboard.org/<repo name>`` where ``username`` is your OpenBeagle username and ``<repo name>`` is the repository name you have selected while forking the project. For example, if username is ``lorforlinux`` and project name is ``gsoc.beagleboard.io`` the rendered site can be accessed live via `lorforlinux.beagleboard.io/gsoc.beagleboard.io <http://lorforlinux.beagleboard.io/gsoc.beagleboard.io>`_. 
 
 .. tip:: 
-    1. For quick review, you can share OpenBeagle pages link with mentors and community members on `Discord <http://bbb.io/gsocchat>`_ or `Forum <https://forum.beagleboard.org/c/gsoc>`_.
+    1. For quick review, you can share OpenBeagle pages link with mentors and community members on our `Discord <https://bbb.io/gsocchat>`_ or `Forum <https://bbb.io/gsocml>`_.
     2. On secondry (right) side bar you will see a **PDF download button** like shown below. Click that button on your proposal page to download PDF version of your proposal which you can submit directly on GSoC porposal submission portal.
     
        .. raw:: html
diff --git a/ideas/index.rst b/ideas/index.rst
index cb22d7ada05839892868041f83a778c5dab52d64..d00e6ee25ad3b9c9c0e665c39b2c324c27777724 100644
--- a/ideas/index.rst
+++ b/ideas/index.rst
@@ -41,8 +41,8 @@ and to automate things in the physical world.
 .. important::
 
     BeagleBoard.org is a community centric organization and we keep all of our discussion open for our
-    community on our `forum <https://forum.beagleboard.org/c/gsoc>`_. Discussion for all the project ideas, proposals or development will
-    be done via our `forum <https://forum.beagleboard.org/c/gsoc>`_ as well and must be open for everyone to access. **No
+    community on our `forum <https://bbb.io/gsocml>`_. Discussion for all the project ideas, proposals or development will
+    be done via our `forum <https://bbb.io/gsocml>`_ as well and must be open for everyone to access. **No
     direct messages should be sent to mentors or community members until unless there is a private matter.**
 
 .. grid:: 1 1 1 2
diff --git a/index.rst b/index.rst
index 041b6b1df990aeca76761048149392a5a6f40f49..2938d488873fd581a26ccbad05d6dc74f8822c5c 100644
--- a/index.rst
+++ b/index.rst
@@ -18,8 +18,8 @@ GSoC @ BeagleBoard.org
    open source developers! The 2024 student application window will be open from
    `March 18th 2024 <https://developers.google.com/open-source/gsoc/timeline#march_18_-_1800_utc>`_ to
    `April 2nd 2024 <https://developers.google.com/open-source/gsoc/timeline#april_2_-_1800_utc>`_!
-   But don't wait for then to engage! Come to our `Discord <http://bbb.io/gsocchat>`_ and
-   `Forum <https://forum.beagleboard.org/c/gsoc>`_ to share ideas today.
+   But don't wait for then to engage! Come to our `Discord <https://bbb.io/gsocchat>`_ and
+   `Forum <https://bbb.io/gsocml>`_ to share ideas today.
 
 .. youtube:: 7jD2tChhrWM
    :width: 100%
diff --git a/proposals/template.rst b/proposals/template.rst
index 45dfc3991804f1f917adfef3033edf11e0c23df8..b6c016de0024ab1c3865119c98e79d200989b1f1 100644
--- a/proposals/template.rst
+++ b/proposals/template.rst
@@ -203,7 +203,7 @@ Benefit
 ========
 
 If successfully completed, what will its impact be on the `BeagleBoard.org <https://www.beagleboard.org/>`_ community? Include quotes from `BeagleBoard.org <http://beagleboard.org/>` 
-community members who can be found on `Discord <http://bbb.io/gsocchat>`_ and `BeagleBoard.org forum <https://forum.beagleboard.org/c/gsoc/13>`_.
+community members who can be found on our `Discord <https://bbb.io/gsocchat>`_ and `BeagleBoard.org forum <https://bbb.io/gsocml/13>`_.
 
 Misc
 ====