lil’ bit more info

Author: ryanflorence

docs/index.md

@@ -13,8 +13,14 @@ The router at the top of your app determines which features are available to the
 - **Data**: Everything from declarative but adds data features like loaders, actions, and pending states. If you're using `createBrowserRouter`, you're using data.
 - **Framework**: Let React Router do it all with efficient bundling, code splitting, server rendering, and advanced type safety. If you're using `routes.ts`, you're using the framework.
 
+Each API doc will list which modes in which it's available with this:
+
+[MODES: framework, data, declarative]
+
 ## Declarative
 
+[modes: declarative]
+
 [Get Started](./start/library/installation) with Declarative routing.
 
 Like previous versions, React Router can still be used as a simple, declarative routing library. Its only job will be matching the URL to a set of components, providing access to URL data, and navigating around the app.
@@ -39,6 +45,8 @@ ReactDOM.createRoot(root).render(
 
 ## Data
 
+[modes: data]
+
 [Get Started](./start/library/installation) building a custom framework with a data router.
 
 The framework features are built on top of lower-level APIs in React Router. You can use these APIs directly for a lighter-weight usage of React Router, but you'll need to set up your own bundling and server rendering (if you want it).
@@ -92,6 +100,8 @@ Using a data router, you now have access to nearly every runtime API in React Ro
 
 ## Framework
 
+[modes: framework]
+
 Building on top of the data mode, React Router can be used maximally as your React framework. In this setup, you'll use the React Router CLI and Vite bundler plugin for a full-stack development and deployment architecture. This enables React Router to provide a large set of features most web projects will want, including:
 
 - Vite bundler and dev server integration