Fix incorrect relative links to external modules

Author: marcprux

scripts/sync-modules.js

@@ -11,8 +11,6 @@ const replacements = [
     { search: 'https://github.com/skiptools', replace: 'https://source.skip.dev' },
     { search: '](https://skip.dev/', replace: '](/' },
     { search: '](https://skip.tools/', replace: '](/' },
-    { search: '](https://source.skip.dev/skip-', replace: '](/docs/modules/skip-' },
-    { search: '](https://source.skip.dev/skipapp-', replace: '](/docs/samples/skipapp-' },
     { search: 'href="https://skip.dev/docs/', replace: 'href="/docs/' },
     { search: '[Skip](https://skip.dev)', replace: 'Skip' }, // strip out bare links to the skip.dev root page
     { search: '[Skip Lite](https://skip.dev)', replace: 'Skip Lite' },
@@ -54,6 +52,10 @@ async function processRepositories() {
       content = content.replaceAll('src="Android/fastlane', `src="${rawBaseUrl}/Android/fastlane`);
       content = content.replaceAll('src="Darwin/fastlane', `src="${rawBaseUrl}/Darwin/fastlane`);
 
+      // replace external links to module and sample roots with the local doc
+      content = content.replace(/\]\(https:\/\/source\.skip\.dev\/(skip-[^\/]+)[\/]?\)/g, "](/docs/modules/$1)");
+      content = content.replace(/\]\(https:\/\/source\.skip\.dev\/(skipapp-[^\/]+)[\/]?\)/g, "](/docs/samples/$1)");
+
       // trim everything after the repo license
       content = content.replace(/## License[\s\S]*/i, '');
 

src/content/docs/docs/modules/skip-firebase/index.md

@@ -16,7 +16,7 @@ with the various `SkipFirebase*` modules passing the transpiled calls
 through to the Firebase Android SDK.
 
 For an example of using Firebase in a [Skip Fuse](/docs/status/#skip_fuse) app, see the
-[FiresideFuse Sample](/docs/samples/skipapp-fireside-fuse/). For a [Skip Lite](/docs/status/#skip_fuse) app, see the [Fireside Sample](/docs/samples/skipapp-fireside/).
+[FiresideFuse Sample](/docs/samples/skipapp-fireside-fuse). For a [Skip Lite](/docs/status/#skip_fuse) app, see the [Fireside Sample](/docs/samples/skipapp-fireside).
 
 ## Package
 
@@ -25,7 +25,7 @@ modules in the Firebase iOS SDK (at [https://github.com/firebase/firebase-ios-sd
 which is also mirrored in the division of the Firebase Kotlin Android gradle modules (at [https://github.com/firebase/firebase-android-sdk.git](https://github.com/firebase/firebase-android-sdk.git)).
 
 See the `Package.swift` files in the
-[FiresideFuse](/docs/samples/skipapp-fireside-fuse/) and [Fireside](/docs/samples/skipapp-fireside/) apps for examples of integrating Firebase dependencies.
+[FiresideFuse](/docs/samples/skipapp-fireside-fuse) and [Fireside](/docs/samples/skipapp-fireside) apps for examples of integrating Firebase dependencies.
 
 <!--
 An example of a Skip Lite app projects using the `Firestore` API at the model layer and the `Messaging` API at the app layer can be seen from the command:
@@ -106,7 +106,7 @@ plugins {
 }
 ```
 
-For concrete examples, see the [FireSideFuse Sample](/docs/samples/skipapp-fireside-fuse/) project.
+For concrete examples, see the [FireSideFuse Sample](/docs/samples/skipapp-fireside-fuse) project.
 {: class="callout info"}
 
 Once Firebase has been added to your project, you need to configure the `FirebaseApp` on app startup. This is typically done in the `onInit()` callback of the `*AppDelegate` in your `*App.swift` file. Here is a snippet from the FireSideFuse sample app:
@@ -333,7 +333,7 @@ open class MainActivity: AppCompatActivity {
 
 1. See Firebase's [iOS instructions](https://firebase.google.com/docs/cloud-messaging/ios/client) and [Android instructions](https://firebase.google.com/docs/cloud-messaging/android/client) for additional details and options, including how to send test messages to your apps!
 
-The [FiresideFuse](/docs/samples/skipapp-fireside-fuse/) and [Fireside](/docs/samples/skipapp-fireside/) projects are great references for seeing complete, working Skip Fuse and Skip Lite apps using Firebase push notifications.
+The [FiresideFuse](/docs/samples/skipapp-fireside-fuse) and [Fireside](/docs/samples/skipapp-fireside) projects are great references for seeing complete, working Skip Fuse and Skip Lite apps using Firebase push notifications.
 {: class="callout info"}
 
 ## Error handling

src/content/docs/docs/modules/skip-foundation/index.md

@@ -47,7 +47,7 @@ To help fill in unimplemented API in SkipFoundation:
 1. Find unimplemented API.
 1. Write an appropriate Kotlin implementation. See [Implementation Strategy](#implementation-strategy) below.
 1. Edit the corresponding tests to make sure they are no longer skipped, and that they pass. If there aren't existing tests, write some. See [Tests](#tests).
-1. [Submit a PR.](/docs/modules/skip-foundation/pulls)
+1. [Submit a PR.](https://source.skip.dev/skip-foundation/pulls)
 
 Other forms of contributions such as test cases, comments, and documentation are also welcome!
 

src/content/docs/docs/modules/skip-lib/index.md

@@ -30,7 +30,7 @@ The module is transparently adopted through the automatic addition of `import sk
 
 ## Status
 
-- SkipLib's Swift symbol files (see [Implementation Strategy](#implementation-strategy)) are nominally complete. They should declare all Swift standard library API. This is difficult to validate, however, so if you find anything missing, please [report it](/docs/modules/skip-lib/issues) to us.
+- SkipLib's Swift symbol files (see [Implementation Strategy](#implementation-strategy)) are nominally complete. They should declare all Swift standard library API. This is difficult to validate, however, so if you find anything missing, please [report it](https://source.skip.dev/skip-lib/issues) to us.
 - Unimplemented API is appropriately marked with `@available(*, unavailable)` annotations. Skip will generate an error when you attempt to use an unimplemented API.
 - In particular, a significant portion of the [collections](#collections) API is not yet implemented.
 - Unit testing is not comprehensive.
@@ -46,7 +46,7 @@ The most pressing need is to reduce the amount of unimplemented API. To help fil
 1. Find unimplemented API. Unimplemented API should be marked with `@available(*, unavailable)` in the Swift symbol files.
 1. Write an appropriate Kotlin implementation. See [Implementation Strategy](#implementation-strategy) below. For [collections](#collections) API, make sure your implementation is duplicated for `String` as well.
 1. Write unit tests.
-1. [Submit a PR.](/docs/modules/skip-lib/pulls)
+1. [Submit a PR.](https://source.skip.dev/skip-lib/pulls)
 
 Other forms of contributions such as test cases, comments, and documentation are also welcome!
 

src/content/docs/docs/modules/skip-model/index.md

@@ -56,7 +56,7 @@ Much of Skip's model support is implemented directly in the Skip transpiler. The
 
 ## Contributing
 
-We welcome contributions to SkipModel. The Skip product [documentation](/docs/contributing/) includes helpful instructions and tips on local Skip library development. When submitting code, please include unit tests in your [PR](/docs/modules/skip-model/pulls).
+We welcome contributions to SkipModel. The Skip product [documentation](/docs/contributing/) includes helpful instructions and tips on local Skip library development. When submitting code, please include unit tests in your [PR](https://source.skip.dev/skip-model/pulls).
 
 ## Model Objects
 

src/content/docs/docs/modules/skip-motion/index.md

@@ -76,7 +76,7 @@ SkipMotion is in a very early stage, and lack any playback
 controls or other customization of the animations.
 
 You are encouraged to contribute to the project or
-file an [issue](/docs/modules/skip-motion/issues)
+file an [issue](https://source.skip.dev/skip-motion/issues)
 with needs and requests.
 
 ## Size
@@ -86,7 +86,7 @@ size of the release `.ipa` and `.apk` artifacts for your project.
 
 ## Example
 
-See the [LottieDemo](/docs/samples/skipapp-lottiedemo/releases)
+See the [LottieDemo](https://source.skip.dev/skipapp-lottiedemo/releases)
 project for an example of using `SkipMotion` in a Skip App project.
 
 ## Building

src/content/docs/docs/modules/skip-script/index.md

@@ -45,7 +45,7 @@ as a dependency and a Swift source file imports the `JavaScriptCore` framework.
 
 In this case, a subset of the the Objective-C JavaScriptAPI is mimicked on the
 Kotlin side, passing the calls through to the underlying C interface to the 
-JavaScriptCore API using JNA and [SkipFFI](/docs/modules/skip-ffi/).
+JavaScriptCore API using JNA and [SkipFFI](/docs/modules/skip-ffi).
 
 
 An example of evaluating some JavaScript:

src/content/docs/docs/modules/skip-supabase/index.md

@@ -44,7 +44,7 @@ The current Supabase API coverage is currently very limited, and mostly used as
 :::
 
 Browse the test cases at
-[SkipSupabaseTests.swift](/docs/modules/skip-supabase/blob/main/Tests/SkipSupabaseTests/SkipSupabaseTests.swift)
+[SkipSupabaseTests.swift](https://source.skip.dev/skip-supabase/blob/main/Tests/SkipSupabaseTests/SkipSupabaseTests.swift)
 to see what API is supported.
 
 :::note
@@ -60,13 +60,13 @@ which is generally mirrored in the division of the Supabase Kotlin Android gradl
 ## Status
 
 This project is in a very early stage, but some amount of Auth and Database API is implemented.
-For examples of what is working, see the [SkipSupabaseTests.swift](/docs/modules/skip-supabase/blob/main/Tests/SkipSupabaseTests/SkipSupabaseTests.swift)
+For examples of what is working, see the [SkipSupabaseTests.swift](https://source.skip.dev/skip-supabase/blob/main/Tests/SkipSupabaseTests/SkipSupabaseTests.swift)
 test case, which also shows how setup can be performed.
 
-Please file an [issue](/docs/modules/skip-supabase/issues)
+Please file an [issue](https://source.skip.dev/skip-supabase/issues)
 if there is a particular API that you need for you project, or if something isn't working right.
 And please consider contributing to this project by filing
-[pull requests](/docs/modules/skip-supabase/pulls).
+[pull requests](https://source.skip.dev/skip-supabase/pulls).
 
 ### Implementation Details
 
@@ -80,6 +80,6 @@ were designed and implemented separately, and so their API shapes differ drastic
 
 For an example of some of the gymnastics that are required to achieve the goal is a single unified API,
 see the implementation of
-[SkipSupabase.swift](/docs/modules/skip-supabase/blob/main/Sources/SkipSupabase/SkipSupabase.swift).
+[SkipSupabase.swift](https://source.skip.dev/skip-supabase/blob/main/Sources/SkipSupabase/SkipSupabase.swift).
 
 

src/content/docs/docs/modules/skip-ui/index.md

@@ -2563,7 +2563,7 @@ For Android, Skip only uses named colors that you've set for "Universal" devices
 
 ### ColorScheme
 
-SkipUI fully supports the `.preferredColorScheme` modifier. If you created your app with the `skip` tool prior to v0.8.26, however, you will have to update the included `Android/app/src/main/kotlin/.../Main.kt` file in order for the modifier to work correctly. Using the latest [`Main.kt`](/docs/samples/skipapp-hello/blob/main/Android/app/src/main/kotlin/hello/skip/Main.kt) as your template, please do the following:
+SkipUI fully supports the `.preferredColorScheme` modifier. If you created your app with the `skip` tool prior to v0.8.26, however, you will have to update the included `Android/app/src/main/kotlin/.../Main.kt` file in order for the modifier to work correctly. Using the latest [`Main.kt`](https://source.skip.dev/skipapp-hello/blob/main/Android/app/src/main/kotlin/hello/skip/Main.kt) as your template, please do the following:
 
 1. Replace the all of the import statements with ones from latest `Main.kt`
 1. Replace the contents of the `setContent { ... }` block with the content from the latest `Main.kt`
@@ -3020,7 +3020,7 @@ Remember that you can use `#if SKIP` blocks to confine your `.ignoresSafeArea` c
 
 #### Enabling or Disabling Edge-to-Edge
 
-Modern SkipUI versions enable Jetpack Compose's "edgeToEdge" mode by default. If you created your app with the `skip` tool prior to v0.8.32, however, you will have to update the included `Android/app/src/main/kotlin/.../Main.kt` file to render content behind system bars. Using the latest [`Main.kt`](/docs/samples/skipapp-hello/blob/main/Android/app/src/main/kotlin/hello/skip/Main.kt) as your template, please do the following:
+Modern SkipUI versions enable Jetpack Compose's "edgeToEdge" mode by default. If you created your app with the `skip` tool prior to v0.8.32, however, you will have to update the included `Android/app/src/main/kotlin/.../Main.kt` file to render content behind system bars. Using the latest [`Main.kt`](https://source.skip.dev/skipapp-hello/blob/main/Android/app/src/main/kotlin/hello/skip/Main.kt) as your template, please do the following:
 
 1. Add the following import: `import androidx.activity.enableEdgeToEdge`
 1. Add the following line to the `MainActivity.onCreate(savedInstanceState:)` function:
@@ -3091,7 +3091,7 @@ To help fill in unimplemented API in SkipUI:
 1. Write an appropriate Compose implementation. See [Implementation Strategy](#implementation-strategy) below.
 1. Add a compiled Swift wrapper to SkipFuseUI.
 1. Write Showcase code to exercise your component. See [Tests](#tests).
-1. [Submit a PR](/docs/modules/skip-ui/pulls).
+1. [Submit a PR](https://source.skip.dev/skip-ui/pulls).
 
 Other forms of contributions such as test cases, comments, and documentation are also welcome!
 

src/content/docs/docs/modules/skip-web/index.md

@@ -32,9 +32,9 @@ struct EmbeddedWebView : View {
 
 ## Customization
 
-The [`WebView`](/docs/modules/skip-web/blob/main/Sources/SkipWeb/WebView.swift) is backed by a
-[`WebEngine`](/docs/modules/skip-web/blob/main/Sources/SkipWeb/WebEngine.swift).
-It can be configured with a [`WebEngineConfiguration`](/docs/modules/skip-web/blob/main/Sources/SkipWeb/WebEngine.swift) instance. For example:
+The [`WebView`](https://source.skip.dev/skip-web/blob/main/Sources/SkipWeb/WebView.swift) is backed by a
+[`WebEngine`](https://source.skip.dev/skip-web/blob/main/Sources/SkipWeb/WebEngine.swift).
+It can be configured with a [`WebEngineConfiguration`](https://source.skip.dev/skip-web/blob/main/Sources/SkipWeb/WebEngine.swift) instance. For example:
 
 ```swift
 import Foundation
@@ -189,7 +189,7 @@ Many delegates that are provided by `WKWebView` are not yet implemented in this
 and so deeper customization may require custom implementation work.
 To implement these, you may need to fork the repository and add it to your workspace,
 as described in the [Contributing guide](/docs/contributing/).
-Please consider creating a [Pull Request](/docs/modules/skip-web/pulls)
+Please consider creating a [Pull Request](https://source.skip.dev/skip-web/pulls)
 with features and fixes that you create, as this benefits the entire Skip community.
 
 ## Building