[Guide - The New Architecture] Pillars

Author: Riccardo Cipolleschi

docs/the-new-architecture/pillars.md

@@ -3,8 +3,27 @@ id: pillars
 title: What Compose the New Architecture
 ---
 
-This section recalls the main pillars from the new-architecture-intro section.
+The New Architecture is composed mainly by two pillars:
 
-It contains a pointer to the `Migration` section and it specifies that these pillars work only when the new architecture is enabled. It also points to the prerequisites.
+- [TurboModules](pillars-turbomodules)
+- [Fabric Components](pillars-fabric-components).
 
-It describes how the following sections are organized.
+TurboModules are the preferred way to create libraries that leverage some platform specific API. Fabric Components are the preferred way to create reusable UI components, providing a native experience to the users.
+
+The main goal of this section is to drive the reader through a step-by-step guide to create their first TurboModule or Fabric Component.
+
+The next sections contain an high-level overview of the pillars, together with the steps to create them. To create one of these pillars, the steps are:
+
+1. Define a JavaScript specification using Flow or TypeScript.
+1. Configure the dependencies management system to generate code from the provided spec.
+1. Implement the Native code.
+1. Integrate the code in the app.
+
+Finally, we dive a little deeper into the [CodeGen](pillars-codegen) process that is required to create all the C++ types and files used by our components, including some useful steps to work comfortably while developing the component.
+
+:::caution
+To integrate a TurboModule or a Fabric Component in an app, the app has to run with the New Architecture enabled.
+
+To create a new app adopting the New Architecture, refer to the [Using the App Template](use-app-template) section.
+To migrate an existing app to the New Architecture, refer to the [Migration](/docs/new-architecture-intro) guide.
+:::