Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New Architecture landing page #3072

Merged
merged 7 commits into from
Apr 20, 2022
Merged

New Architecture landing page #3072

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
82b5b36
First draft of landing page
lindboe Apr 13, 2022
a8870eb
Add migration and backwards compatibility links
lindboe Apr 13, 2022
c40141a
lint fix
lindboe Apr 13, 2022
82ee07b
Restructure slightly, leaning more on context from Why a New Architec…
lindboe Apr 14, 2022
dda80ca
Don't need md in links
lindboe Apr 14, 2022
70bb694
Suggested rewording
lindboe Apr 14, 2022
849495a
Rephrase pillar summaries
lindboe Apr 14, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
27 changes: 21 additions & 6 deletions docs/the-new-architecture/landing-page.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,11 +3,26 @@ id: landing-page
title: Introduction
---

This section is the entry point for the new guide’s documentation.
It contains some basic information about the New Architecture: its pillars, the version from which it has been made available and other very high-level information. Then, it should present the guide’s structure itself.
Starting in version 0.68, React Native provides the New Architecture, which offers developers new capabilities for building highly performant and responsive apps. Visit [Why a New Architecture](why) to learn more about what drove the decision to re-architect, and the benefits it provides.

This section should also contains a sort of Driving guide based on the user use-cases:
In order to achieve these benefits, we had to rethink how Native Modules and Native Components work. This led us to develop the [Pillars of the New Architecture](pillars):

- New user: link to how to use the new [app template](use-app-template)
- New Library developer: link to the [pillars](pillars)
- Old library developer/app developer: link to [the migration guide](../new-architecture-intro)
- [TurboModules](pillars-turbomodules), a framework to support efficient and flexible integration with native code
- [Fabric renderer and components](pillars-fabric-components), which offer improved capabilities, cross-platform consistency, and performance in rendering
- [CodeGen](pillars-codegen), which generates boilerplate C++ required by the New Architecture, via static typing in JavaScript

## Get started with the New Architecture

### For app developers

To **create a new app** using the New Architecture, head over to [Creating a New Architecture App](use-app-template), which will get you up and running in a few quick steps with the new app template.

To **migrate an existing app** to the New Architecture, follow [Adopting the New Architecture](../new-architecture-intro).

### For library maintainers

First, read up on the core concepts outlined in the [Pillars](pillars) section.

Then, for a **how-to guide** on supporting the New Architecture, check out the [Migration](../new-architecture-library-info) guide.

For information on **supporting both the Old and New Architectures**, see the [Backwards Compatibility](backward-compatibility) guide.