docs: introduction doc updates (#527)

* docs: introduction doc updates

* update

* Update website/src/docs/getting-started/introduction.md

---------

Co-authored-by: Michał Pierzchała <[email protected]>

Author: szymonrybczak

website/src/docs/configuration.md

@@ -47,8 +47,8 @@ It's intentional design decision to explicitly define platforms, bundlers etc, s
   // Optional: Additional commands
   commands?: Array<Command>;
 
-  // Optional: Configure remote cache provider. Currently supports: 'github-actions' or null
-  remoteCacheProvider?: 'github-actions' | null;
+  // Optional: Configure remote cache provider. Currently supports: 'github-actions' or custom provider (function).
+  remoteCacheProvider?: 'github-actions' | () => RemoteBuildCache |  null;
 
   fingerprint?: {
     // Additional source files/directories to include in fingerprint calculation

website/src/docs/getting-started/introduction.md

@@ -1,6 +1,6 @@
 # Introduction
 
-Rock is a toolkit designed to accelerate React Native app development for enterprise teams. It provides a CLI and Remote Cache system (currently integrated with GitHub Actions) to make your team's development workflow more efficient.
+Rock is a toolkit designed to accelerate React Native app development for enterprise teams. It provides a CLI and Remote Cache system to make your team's development workflow more efficient.
 
 :::info OK I want to try it!
 If you feel like skipping this intro section and try it out in existing Community CLI project, head over to [Quick start](/docs/getting-started/index).
@@ -30,14 +30,14 @@ Using anything other than the Community CLI is not an option for them currently.
 We build the framework with a clear focus: to serve large teams and complex apps. These projects require flexibility, the ability to host everything on their own, deploy to as many platforms as possible, and decrease onboarding time. That's why our engineering design choices focus on:
 
 - **Modular design**—add your supported platforms and plugins, and integrate existing tools; you can build around our framework
-- **Self-hosting**—use your own infrastructure without relying on third-party cloud vendors; whether you're using GitHub Actions or soon Amazon S3 and BitBucket, we got you covered.
+- **Self-hosting**—use your own infrastructure without relying on third-party cloud vendors; whether you're using GitHub Actions or Amazon S3 and BitBucket, we got you covered.
 - **Incremental adoption**—easily migrate from Community CLI or an existing native app.
 
 ## The CLI
 
 We've created a new CLI from scratch with a focus on seamless migration from the Community CLI. Most projects can replace their local build and run experience with our CLI in under 10 minutes.
 
-Its core part is modular configuration mechanism allowing for customizing the capabilities (and soon also DX) to your needs through a system of plugins and replaceable parts of the build chain, such as: bundler, platforms, remote cache provider, or helpers exposed through variety of npm packages.
+Its core part is modular configuration mechanism allowing for customizing the capabilities to your needs through a system of plugins and replaceable parts of the build chain, such as: bundler, platforms, remote cache provider, or helpers exposed through variety of npm packages.
 
 :::info Developer Experience
 For the best DX we focus on our CLI to be entrypoint to that system. In the future we imagine you can interact with it through other tools, like Shopify's Tophat, AI agent, or a custom CLI you already have and control.
@@ -90,10 +90,9 @@ We've simplified the interface by removing redundant flags:
 
 The Remote Cache is an optional but powerful feature that speeds up your development workflow. It acts as a centralized storage for native app builds that can be retrieved either manually or through our CLI. The cache can be hosted on various platforms:
 
-- GitHub Actions (currently supported)
-- Amazon S3 (coming soon)
-- Cloudflare R2 (coming soon)
-- Your own CI artifacts
+- GitHub Actions
+- Amazon S3
+- Cloudflare R2
 - Custom providers
 
 :::note
@@ -105,7 +104,7 @@ Out of the box we support storing artifacts on GitHub Actions and we're working
 1. For each build, we calculate a unique hash (fingerprint) with [`@expo/fingerprint`](https://docs.expo.dev/versions/latest/sdk/fingerprint/) that represents your project's native state
 2. This hash remains stable across builds unless you:
    - Modify native files
-   - Change native dependencies
+   - Change dependencies with native code
    - Update scripts in package.json
 3. When you make JavaScript-only changes, the hash stays the same
 4. The CLI checks for matching builds in:
@@ -129,4 +128,4 @@ We provide a set of reusable GitHub Actions that handle:
   - Android: keystore (AAB)
 - Automatic re-signing of builds with fresh JS bundles on PR updates
 
-Learn more about [GitHub Actions configuration](/docs/remote-cache/github-actions/configuration).
+Learn more about [GitHub Actions configuration](/docs/github-actions/configuration).