Clarify that Theia is not a VS Code fork (#695)

fixed #694

Signed-off-by: Jonas Helming <[email protected]>

src/components/index/Features.js

@@ -64,7 +64,10 @@ const features = [
     {
         img: <img src={Html} alt="Modern Tech" />,
         title: "Modern Tech",
-        paragraphs: ['Theia is based on a state-of-the-art web-based  technology stack. It provides language support via LSP and DAP. Further, it can host VS Code extensions and provides full terminal access.']
+        paragraphs: [
+            'Theia is built on a modern web technology stack, offering language support via LSP and DAP, hosting VS Code extensions, and providing full terminal access.',
+            'While it reuses components from VS Code, such as the Monaco editor, Theia is an independent platform with a modular architecture—not a fork of VS Code.'
+        ]
     }
 ]
 

src/components/index/TheiaIDEExtensible.js

@@ -51,7 +51,12 @@ const TheiaIDEExtensible = () => (
         <Styled>
             <section className="products">
                 <h2 className="heading-tertiary">Extensible and Open</h2>
-                <p>The Theia IDE is built upon the highly modular <a href="./">Theia platform</a>, enabling the integration of custom extensions and the creation of fully tailored tools (see examples below). <a href="./">Explore the Theia Platform</a> and learn how to create custom tool offerings with ease!</p>
+                <p>
+                    The Theia IDE is built upon the highly modular <a href="./">Theia platform</a>, enabling the integration of custom extensions and the creation of fully tailored tools (see examples below). <a href="./">Explore the Theia Platform</a> and learn how to create custom tool offerings with ease!
+                </p>
+                <p>
+                    While Theia incorporates certain components from Visual Studio Code, such as the Monaco editor, it is <a href="https://eclipsesource.com/blogs/2024/07/12/vs-code-vs-theia-ide/">independently developed</a> with a unique, modular architecture, <b>Theia is not a <a href="https://eclipsesource.com/blogs/2024/12/17/is-it-a-good-idea-to-fork-vs-code/">fork of VS Code</a></b>.
+                </p>
                 <br></br>
                 <Swiper
                     modules={[Navigation, Autoplay]}

src/docs/composing_applications.md

@@ -23,6 +23,10 @@ The detailed list of prerequisites is located at the main Theia repository:
 
 A Theia app is composed of so-called Theia extensions. Each extension resides in its own npm package.
 An extension provides a set of features, e.g. widgets, commands, handlers, etc. for a specific functionality. The Theia project itself ships a number of extensions for common features, e.g. for editors, terminals, the project view etc. You can resue these existing extensions by just adding them to you custom Theia application. Additionally, you can add arbitrary VS Code extensions to your application, again for reusing existing features already available, such as Git support. Finally, you can then extend and customize your Theia application with your own features, which you can implement as [Theia extensions or VS Code extensions](/docs/extensions).
+
+While Theia incorporates certain components from Visual Studio Code, such as the Monaco editor, it is independently developed with a modular architecture and is **not a [fork of VS Code](https://eclipsesource.com/blogs/2024/12/17/is-it-a-good-idea-to-fork-vs-code/)**. This distinction allows adopters to innovate and fully tailor their tools without limitations. For a deeper comparison, see [Theia IDE vs VS Code](https://eclipsesource.com/blogs/2024/07/12/vs-code-vs-theia-ide/) and [Eclipse Theia vs VS Code OSS](https://eclipsesource.com/blogs/2023/09/08/eclipse-theia-vs-code-oss/).
+
+
 In this guide, we will create a Theia application with a number of existing Theia extensions and one (generated) custom Theia extension. Please also refer to our [documentation on how to create custom Theia extensions](/docs/authoring_extensions) to learn more on how to create your own Theia extensions. Finally, also see [our guide on how to add VS Code extensions to your custom Theia application](/docs/authoring_vscode_extensions).
 
 ## Project Layout

src/docs/project_goals.md

@@ -36,6 +36,9 @@ Theia is an extensible and adaptable framework. Extensibility in this context me
 
 Theia provides the ability to host VS Code extensions. This allows adopters to benefit from features that are provided as VS Code extensions and make them part of their tool offering. It also allows end users of Theia-based tools to install additional features, if the adopter providing a tool allows users to do so. When applicable, the default Theia UX aligns with the VS Code UI, although adopters can deviate from this.
 
+While Theia incorporates certain components from Visual Studio Code, such as the Monaco editor, it is independently developed with a unique, modular architecture, and is **not a fork of VS Code**. This distinction ensures that Theia remains a fully adaptable and customizable framework, offering adopters freedom to innovate. For a deeper comparison, see [Theia IDE vs VS Code](https://eclipsesource.com/blogs/2024/07/12/vs-code-vs-theia-ide/) and [Eclipse Theia vs VS Code OSS](https://eclipsesource.com/blogs/2023/09/08/eclipse-theia-vs-code-oss/).
+
+
 ## Use Standards And Don’t Reinvent The Wheel
 
 Theia uses/reuses industrial standard technologies and practices whenever applicable. This keeps the scope of the project minimal and decreases the maintenance cost. This applies to the use of frameworks and development tools as well as to general concepts such as UX.