Minor cleanup, docs polish

Author: alicerunsonfedora

Alidade.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved

@@ -33,3 +33,9 @@ extension CartographyMapPin.Color {
         }
     }
 }
+
+extension CartographyMapPin {
+    func resolveColor() -> SwiftUI.Color {
+        self.color?.swiftUIColor ?? .accent
+    }
+}

Alidade/Extensions/MCMapFormat/MCMapManifestPinColor+SwiftUI.swift

@@ -77,19 +77,20 @@ contributors to read through.
 ### Architecture and View Hierarchy
 
 - <doc:Architecture>
-- <doc:LegacyArchitecture>
-- ``MCMapsApp``
+- ``Alidade``
 
 ### Launch experience
-- ``DocumentLaunchView-6qz0r``
-- ``RecentDocumentsList``
-- ``DocumentLaunchViewModel``
+- ``DocumentContinuation``
+- ``DocumentLaunchView``
+- ``DocumentLaunchScene``
 
 ### Services
 
 - <doc:Integrations>
-- ``CartographyIntegrationService``
+- ``CartographyClock``
 - ``CartographySearchService``
+- ``CartographyIntegrationService``
+- ``PasteboardActor``
 
 ### Map Ornaments
 
@@ -103,9 +104,19 @@ contributors to read through.
 
 ### Pickers
 
-- ``CartographyMapPinColorPicker``
 - ``WorldDimensionPickerView``
 
+### Icons
+
+- ``SemanticIcon``
+- ``CartographyIconPicker``
+
+### Command Groups
+
+- ``MapCommands``
+- ``HelpCommands``
+- ``DebugCommands``
+
 ### Tips and Onboarding
 
 - ``LibraryOnboardingTip``
@@ -132,6 +143,4 @@ contributors to read through.
 
 ### Settings and Feature Flags
 
-- ``FeatureFlag``
-- ``FeatureFlagged``
 - ``AlidadeSettingsView``

Alidade/Resources/Alidade.docc/Alidade.md

@@ -8,13 +8,9 @@ Learn and understand Alidade's architecture and view hierarchy.
 
 ## Overview
 
-> Important: To view information about the legacy architecture, refer to
-> the <doc:LegacyArchitecture> article.
-
-Under the **Red Window** design, Alidade provides a consistent
-architecture and user interface that applies across Mac, iPhone, and iPad.
-This article will cover how the app is structured and how it interacts
-with other views.
+Alidade provides a consistent architecture and user interface that applies
+across Mac, iPhone, and iPad. This article will cover how the app is
+structured and how it interacts with other views.
 
 ### Rationale
 
@@ -29,18 +25,17 @@ portable views while leveraging what SwiftUI has to offer.
 
 ## Entrypoint
 
-Much like the legacy architecture, the main app starts at the
-``MCMapsApp`` entrypoint. Here, the ``RedWindowContentView`` is created,
-which receives the currently open file as an argument. Information about
-the current app state is passed through as an environment object,
-``RedWindowEnvironment``. This environment object contains key information
-such as which tab route is currently active, what pins should be deleted,
-etc:
+The main app starts at the ``Alidade`` entrypoint. Here, the
+``RedWindowContentView`` is created, which receives the currently open file
+as an argument. Information about the current app state is passed through
+as an environment object, ``RedWindowEnvironment``. This environment
+object contains key information such as which tab route is currently
+active, what pins should be deleted, etc:
 
 ```swift
 import SwiftUI
 
-struct MCMapsApp: App {
+struct Alidade: App {
     @State private var redWindowEnv = RedWindowEnvironment()
     var body: some Scene {
         DocumentGroup(...) { configuration in
@@ -51,8 +46,6 @@ struct MCMapsApp: App {
 }
 ```
 
-This effectively replaces the old ``CartographyMapViewModel``.
-
 At this time, any integration services are also set up. For example, the
 Bluemap integration service is provided as an environment variable to the
 view through the ``SwiftUICore/EnvironmentValues/bluemapService`` key