docs: update links from landing page to score

Implements: #17
Signed-off-by: Philipp Ahmann <[email protected]>

Author: pahmann

docs/get_involved.rst

@@ -47,13 +47,13 @@ lead circle. Meeting notes are transparent via the S-CORE github organization. (
 
 We aim to build a safety ready full stack architecture, where components fit to each other in 
 automotive grade Software Quality and performance. To achieve this, we follow a strict
-`feature roadmap and architecture <https://eclipse-score.github.io/score/score_releases/index.html#releases>`_
-and a `rigid software development process <https://eclipse-score.github.io/score/process/index.html#process-description>`_
+`feature roadmap and architecture <https://eclipse-score.github.io/score/main/score_releases/index.html>`_
+and a `rigid software development process <https://eclipse-score.github.io/score/main/process/index.html>`_
 (currently under development). 
 
 Contributions to the S-CORE project must therefore follow the technical direction of the project and the S-CORE 
 architecture. All work in S-CORE will therefore follow a
-`Contribution Request Guideline <https://eclipse-score.github.io/score/process/guidance/contribution_request/index.html>`_.
+`Contribution Request Guideline <https://eclipse-score.github.io/score/main/contribute/contribution_request/contribution_request.html>`_.
 Features on the roadmap of S-CORE are defined, Contribution Requests create the basis for individual contributions from
 within the S-CORE project and also from the outside.
 
@@ -75,4 +75,4 @@ We value real code based collaboration and will judge new potential contributors
 Active and sustaining contributions are the basis for the ability to shape S-CORE.
 
 Making active code contributions via the contribution request process described in the
-`S-CORE project handbook <https://eclipse-score.github.io/score/platform_management_plan/project_management.html>`_.
+`S-CORE project handbook <https://eclipse-score.github.io/score/main/platform_management_plan/project_management.html>`_.

docs/index.rst

@@ -126,8 +126,8 @@ In general, all tooling is made available as open source and comes either from o
 or is developed in the context of the *S-CORE* project. The whole infrastructure is based on a build system called
 `bazel <https://bazel.build/>`_. All workflows such as cloning the repositories, building the software,
 generation of documentation, testing and much more are automated using bazel. This provides every project user with
-the same user experience. To start working with bazel in the *S-CORE* project, you should check
-this `introduction page <https://github.com/eclipse-score/blob/main/README.md>`_.
+the same user experience. To start working with bazel in the *S-CORE* project to build software and documentation, 
+you should check this `introduction page <https://github.com/eclipse-score/score/blob/main/README.md>`_.
 
 For documenting the process, requirements and architecture we rely on `sphinx <https://www.sphinx-doc.org/en/master/>`_ and it's extension
 `sphinx-needs <https://www.sphinx-needs.com/>`_. For small diagrams we use `PlantUML sphinx-needs extensions <https://sphinx-needs.readthedocs.io/en/stable/directives/needuml.html>`_,
@@ -151,7 +151,7 @@ Here you can find the preliminary roadmap of the project:
    :align: center
 
 
-Please be aware, that this roadmap will be also transfered to the `GitHub project <https://github.com/orgs/eclipse-score/projects/1>`_.
+Please be aware, that this roadmap will be also transfered to the `GitHub project <https://github.com/orgs/eclipse-score/projects/13>`_.
 Please follow this link to get the latest state of the planning. 
 
 MVP Phase