add breadcrumb back to guides and convert codegen to unix file

Author: lunaleaps

docs/appendix.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Appendix
 
 ## I. Terminology

docs/backwards-compat-fabric-component.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Fabric Components as Legacy Native Components
 
 > [!Note]

docs/backwards-compat-turbo-modules.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Turbo Modules as Legacy Native Modules
 
 > [!Note]

docs/backwards-compat.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Backwards Compatibility
 
 Creating a backward compatible module is important to provide a library that works in both the **Old Architecture** and the **New Architecture**. Not all the users of your library will immediately jump on the New Architecture ship: it is a good thing that they will be able to use your library even if they are still using the old architecture.

docs/codegen.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Supporting Custom C++ Types
 
 By default C++ Turbo Native Modules support [bridging functionality](https://github.com/facebook/react-native/tree/main/packages/react-native/ReactCommon/react/bridging) for most `std::` standard types.

docs/cxx-custom-types.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Enable the New Architecture for Apps
 
 This page will help you create or migrate a React Native app that uses the New Architecture.

docs/enable-apps.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Enable the New Architecture for Libraries: Android
 
 Once you have defined the JavaScript specs for your native modules as part of the [prerequisites](./enable-libraries-prerequisites.md), set up the configuration of the Codegen, and follow the Android/Gradle setup, you are now ready to migrate your library to the new architecture. Here are the steps you can follow to accomplish this.

docs/enable-libraries-android.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Enable the New Architecture for Libraries: iOS
 
 You have defined the JavaScript specs for your native modules as part of the [prerequisites](./enable-libraries-prerequisites.md), and you are now ready to migrate your library to the New Architecture. Here are the steps you can follow to accomplish this.

docs/enable-libraries-ios.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Enable the New Architecture for Libraries: Prerequisites
 
 The following steps are prerequisites to ensure your modules and components are ready for the New Architecture.

docs/enable-libraries-prerequisites.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Fabric Native Components
 
 A Fabric Native Component is a Native Component rendered on the screen using the [Fabric Renderer](https://reactnative.dev/architecture/fabric-renderer). Using Fabric Native Components instead of Legacy Native Components allows us to reap all the of the **New Architecture**:

docs/fabric-native-components.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # React 18 & React Native
 
 This page describes how to use React 18 with React Native using the React Native's New Architecture.

docs/react-18.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Troubleshooting
 
 This page contains resolutions to common problem you might face when migrating to the New Architecture.

docs/troubleshooting.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Cross-Platform Turbo Native Modules with C++
 
 This guide shows you how to implement a Turbo Native Module using C++ only, a way to share the same implementation with any supported platform (Android, iOS, macOS or Windows).

docs/turbo-modules-xplat.md

@@ -1,3 +1,5 @@
+[../README.md#Guides](../README.md#guides)
+
 # Turbo Native Modules
 
 If you've worked with React Native, you may be familiar with the concept of [Native Modules](https://reactnative.dev/docs/native-modules-intro), which allow JavaScript and platform-native code to communicate over the React Native "bridge", which handles cross-platform serialization via JSON.