docs: Integrate content of landing page

Signed-off-by: Philipp Ahmann
Signed-off-by: Philipp Ahmann <Philipp.Ahmann@de.bosch.com>

Author: pahmann

docs/index.rst

@@ -41,9 +41,6 @@ Welcome & Overview
 
 **Welcome to the Software documentation of the SCORE project.**
 
-If this is the first time you get in touch with SCORE, the `SCORE main page <https://eclipse-score.github.io/>`__
-may be a good starting point to receive first insights of the project itself.
-
 Introduction
 ~~~~~~~~~~~~
 
@@ -84,7 +81,7 @@ Software artifacts
 
       Requirements
       ^^^
-      Analyse :ref:`Stakeholder <stakeholder_requirements>` or :ref:`Tool <tool_requirements>` requirements for
+      Analyze :ref:`Stakeholder <stakeholder_requirements>` requirements for
       the work with and implementation inside SCORE.
       Or get the complete picture on the :ref:`requirements` page.
 
@@ -140,5 +137,4 @@ Project structure and processes
       Releases <score_releases/index.rst>
       process/index
       PMP <platform_management_plan/index.rst>
-      SCORE <https://eclipse-score.github.io>
       Eclipse <https://projects.eclipse.org/projects/automotive.score>

docs/introduction/_assets/score_roadmap.drawio.svg

@@ -17,59 +17,59 @@
 Get involved
 ============
 
-How to get in contact with SCORE
---------------------------------
+How to get in contact with S-CORE
+---------------------------------
 
-If you want to get into contact with SCORE, these are your primary entry points: 
+If you want to get into contact with S-CORE, these are your primary entry points:
 
 :Project Mailing List: score-dev@eclipse.org
 
 :Architectural Discussion: `#score-project-channel-public <https://sdvworkinggroup.slack.com/archives/C083Z4VL90B>`__
 
-| **General Information / Alignment regarding SCORE as a basis for distributions & products:** 
-| Contact one of the project leads of SCORE https://projects.eclipse.org/projects/automotive.score/who
+| **General Information / Alignment regarding S-CORE as a basis for distributions & products:**
+| Contact one of the project leads of S-CORE https://projects.eclipse.org/projects/automotive.score/who
 
-The technical HOWTO regarding involvement into SCORE is described here: 
+The technical HOWTO regarding involvement into S-CORE is described here:
 https://github.com/eclipse-score/score/blob/main/CONTRIBUTION.md
 
-How to get involved into SCORE
-------------------------------
+How to get involved into S-CORE
+-------------------------------
 
-The only way to influence SCORE is TO CONTRIBUTE. Everybody can contribute – SCORE is open.
+The only way to influence S-CORE is TO CONTRIBUTE. Everybody can :ref:contribute <contribute> – S-CORE is open.
 
-Active Contributions to the SCORE project are the basis for getting involved. The SCORE Project works according to 
-the Eclipse Project Handbook and has named and elected project leads and committers (see https://projects.eclipse.org/projects/automotive.score/who). 
-Direction of the SCORE project is discussed and decided in the project lead circle, technical direction is created and prediscussed in the tech 
-lead circle. Meeting notes are transparent via the SCORE github organization. (see https://github.com/orgs/eclipse-score/discussions)
+Active Contributions to the S-CORE project are the basis for getting involved. The S-CORE Project works according to
+the Eclipse Project Handbook and has named and elected project leads and committers (see https://projects.eclipse.org/projects/automotive.score/who).
+Direction of the S-CORE project is discussed and decided in the project lead circle, technical direction is created and upfront in the tech
+lead circle. Meeting notes are transparent via the S-CORE github organization. (see https://github.com/orgs/eclipse-score/discussions)
 
-We aim to build a safety ready full stack architecture, where components fit to each other in 
+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
 :ref:`feature roadmap and architecture <releases>`
 and a :ref:`rigid software development process <process_description>`
-(currently under development). 
+(currently under development).
 
-Contributions to the SCORE project must therefore follow the technical direction of the project and the SCORE 
-architecture. All work in SCORE will therefore follow a
+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
 :need:`Contribution Request Guideline <gd_guidl__contr_request_guideline>`.
-Features on the roadmap of SCORE are defined, Contribution Requests create the basis for individual contributions from
-within the SCORE project and also from the outside.
+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.
 
-You can make proposals for new features or architectural building blocks besides the active contribution requests. 
-Those will not by default be part of the next release of SCORE, because the SCORE release roadmap will strictly 
-comply with the contribution request structure. 
-We plan to have the initial contribution request structure available in the SCORE GitHub until Q1 / 2025.
+You can make proposals for new features or architectural building blocks besides the active contribution requests.
+Those will not by default be part of the next release of S-CORE, because the S-CORE release roadmap will strictly
+comply with the contribution request structure.
+We plan to have the initial contribution request structure available in the S-CORE GitHub until Q1 / 2025.
 
 We plan to incorporate a staging area for such contributions, but
-in the initial phase of the SCORE project (until end of 2025) the focus will be primarily on building a valid 1.0 
+in the initial phase of the S-CORE project (until end of 2025) the focus will be primarily on building a valid 1.0
 release. Feel free to reach out via the communication channels above.
 
-If you think about your contribution to SCORE, the `Feature Request overview <https://github.com/orgs/eclipse-score/projects/4/views/1>`_
+If you think about your contribution to S-CORE, the `Feature Request overview <https://github.com/orgs/eclipse-score/projects/4/views/1>`_
 is the best place to start.
 
-Based on successful code contributions to the SCORE roadmap, further steps in involvement (like becoming a committer) 
+Based on successful code contributions to the S-CORE roadmap, further steps in involvement (like becoming a committer)
 will be handled according to the rules of the Eclipse Foundation Project Handbook.
 We value real code based collaboration and will judge new potential contributors and committers mainly on the validity of their work.
-Active and sustaining contributions are the basis for the ability to shape SCORE.
+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
 :need:`Contribution Request Guideline <gd_guidl__contr_request_guideline>`.

docs/introduction/_assets/score_roadmap.svg

@@ -80,7 +80,7 @@ including hardware specific peripherals.
 Target Picture of Core Stack - PRELIMINARY
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The following image shows platform architecture in more details including surroundings as  
+The following image shows platform architecture in more details including surroundings as
 Board support package (BSP) and HW specific.
 
 .. image:: _assets/score_architecture_core_stack_target_picture.png
@@ -95,13 +95,12 @@ Roadmap
 
 Here you can find the preliminary roadmap of the project:
 
-.. image:: _assets/score_roadmap.svg
+.. image:: _assets/score_roadmap.drawio.svg
    :alt: project roadmap
    :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 follow this link to get the latest state of the planning. 
+Please be aware, that the roadmap is transferred to and maintained in the `GitHub project <https://github.com/orgs/eclipse-score/projects/13/views/2>`_.
+Please follow this link to get the latest state of the planning.
 
 MVP Phase
 ^^^^^^^^^
@@ -111,30 +110,30 @@ The main goals of the *MVP Phase* are following:
 * establish a working infrastructure, that enables every developer of the project to specify
   requirements and architecture, implement code and test it accordingly.
 * set-up project structure, that covers all aspects of the open source software development including
-  cooperation between developers and teams, planning, creation of the roadmaps and coordination meetings.
-* define a software development process compliant to ISO 26262:2018, that is a prerequiste for any other software development in the project.
+  cooperation between developers and teams, planning, creation of the roadmap and coordination meetings.
+* define a software development process compliant to ISO 26262:2018, that is a pre-requisite for any other software development in the project.
 
 A lot of preparation was already done in the background, therefore we are quite optimistic to finish the *MVP Phase*
-latest in the beginning of 2025.  
+latest in the beginning of 2025.
 
 Alignment Phase
 ^^^^^^^^^^^^^^^
 
-In the *Alignment Phase* the main goal is to align on the feature architecture and requirements of the *SCORE Platform v1.0*.
+In the *Alignment Phase* the main goal is to align on the feature architecture and requirements of the *S-CORE Platform v1.0*.
 Additionally it is important to define the roadmap and the order, in which the features should be implemented.
 
 Development Phase
 ^^^^^^^^^^^^^^^^^
 
 The *Development Phase* is the phase, where the implementation of the main modules of the platform should happen.
 The most important milestone here is the *Release v0.5*, that should contain the basic modules, e.g *IPC*.
-The *Release v0.5* milestone will show, whether previously defined software development process will work and how big is the acceptance and 
+The *Release v0.5* milestone will show, whether previously defined software development process will work and how big is the acceptance and
 the interest of the automotive community to the project.
 
 Series Stability & Evolution Phase
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-In this phase the project should be in an well established state and accepted by the community. Continious development
+In this phase the project should be in an well established state and accepted by the community. Continuous development
 of the features is taking place.
 
 How we Work
@@ -143,15 +142,13 @@ How we Work
 Meetings
 ^^^^^^^^
 
-The following regular meetings (and corresponding meeting minutes) are held as part of the project:
-
-- `Project Leader Circle <https://github.com/orgs/eclipse-score/discussions/categories/project-lead-circle>`_
+Regular meetings (and corresponding meeting minutes) are held as part of the project:
 
-- `Technical Leader Circle <https://github.com/orgs/eclipse-score/discussions/categories/technical-leader-circle>`_
+- `Teams & Circles <https://github.com/orgs/eclipse-score/discussions>`_
 
-The dates will be announced via the score-dev@eclipse.org mailing list.
+Typically teams and circles meet weekly.
 
-We plan to start regular exchange in the scope of the *SCORE* project in December 2024.
+A public meeting calendar for the *S-CORE* project is in preparation.
 
 Partners
 ^^^^^^^^