Update docs

Author: ejsmith

docs/guide/configuration.md

@@ -1,5 +1,9 @@
 # Configuration Options
 
+::: tip You Probably Don't Need This
+Foundatio Mediator works out of the box with sensible defaults — most projects never need to configure anything beyond `services.AddMediator()`. Only reach for the options below when you want to change a specific default behavior.
+:::
+
 Foundatio Mediator provides two types of configuration: **compile-time configuration** via the `[assembly: MediatorConfiguration]` attribute that controls source generator behavior, and **runtime configuration** via the `AddMediator()` method that controls mediator behavior.
 
 ## Compile-Time Configuration (Assembly Attribute)

docs/guide/getting-started.md

@@ -52,6 +52,10 @@ Console.WriteLine(result); // Pong: Hello
 
 That's it. No interfaces, no base classes, no registration — the source generator handles everything at compile time with near-direct-call performance.
 
+::: tip Zero Configuration Required
+The defaults are optimized for the most common use cases. You do **not** need `[assembly: MediatorConfiguration]` — it exists only as an escape hatch when you want to change a specific default behavior. See [Configuration](./configuration) for the full list of options.
+:::
+
 ## Async Handlers
 
 Handlers can be async and accept additional parameters resolved from DI:
@@ -108,6 +112,19 @@ HTTP methods, routes, and parameter binding are all inferred from message names
 app.MapMyAppEndpoints(logEndpoints: true);
 ```
 
+Need to customize a specific endpoint? Use the `[HandlerEndpoint]` attribute:
+
+```csharp
+public class TodoHandler
+{
+    [HandlerEndpoint(Route = "/todos/search", HttpMethod = "GET")]
+    public Task<Result<Todo[]>> HandleAsync(SearchTodos query) { /* ... */ }
+
+    [HandlerEndpoint(Streaming = EndpointStreaming.ServerSentEvents, SseEventType = "todo")]
+    public async IAsyncEnumerable<Todo> Handle(SubscribeToTodos msg) { /* ... */ }
+}
+```
+
 See [Endpoints](./endpoints) for route customization, OpenAPI metadata, authorization, and more.
 
 ## Result Types
@@ -168,7 +185,16 @@ await foreach (var evt in mediator.SubscribeAsync<OrderCreated>(cancellationToke
 }
 ```
 
-This is ideal for streaming endpoints where each client needs its own live feed. See [Dynamic Subscriptions](./streaming-handlers#dynamic-subscriptions-with-subscribeasync) for the full API.
+Subscribe to **all** published notifications at once using `INotification`:
+
+```csharp
+await foreach (var evt in mediator.SubscribeAsync<INotification>(cancellationToken: ct))
+{
+    Console.WriteLine($"{evt.GetType().Name} published");
+}
+```
+
+You can also subscribe to a custom marker interface (e.g., `IDispatchToClient`) to receive a targeted subset — no bridging layer or relay pipeline needed. See [Dynamic Subscriptions](./streaming-handlers#dynamic-subscriptions-with-subscribeasync) for the full API.
 
 ## Middleware
 

docs/guide/handler-conventions.md

@@ -107,7 +107,7 @@ public class OrderProcessor { }
 ```
 
 ::: tip Use Handler for Everything
-Unlike some libraries that distinguish between "handlers" and "consumers," Foundatio Mediator treats both identically. The `Consumer` suffix exists purely to ease migration from libraries like MassTransit. For new projects, use `Handler` consistently for commands, queries, and events alike.
+Unlike some libraries that distinguish between "handlers" and "consumers," Foundatio Mediator treats both identically. The `Consumer` suffix exists purely to ease migration from other mediator and message bus libraries. For new projects, use `Handler` consistently for commands, queries, and events alike.
 :::
 
 ## Method Naming Conventions

tests/Foundatio.Mediator.Tests/PublishInterceptorGenerationTests.cs

@@ -34,6 +34,8 @@ public async Task Publish(IMediator mediator) {
         Assert.Contains("InterceptsLocation", publishInterceptor.Source);
         Assert.Contains("GetPublishHandlersForType", publishInterceptor.Source);
         Assert.Contains("Mediator)mediator).Registry", publishInterceptor.Source);
+        // Should fan out to dynamic subscribers
+        Assert.Contains("TryWriteSubscription", publishInterceptor.Source);
         // Should have exception aggregation
         Assert.Contains("AggregateException", publishInterceptor.Source);
         // Should pass mediator to handlers
@@ -71,6 +73,8 @@ public async Task Publish(IMediator mediator) {
         Assert.Contains("InterceptPublishAsync_UserRegistered_", publishInterceptor.Source);
         Assert.Contains("GetPublishHandlersForType", publishInterceptor.Source);
         Assert.Contains("Mediator)mediator).Registry", publishInterceptor.Source);
+        // Should fan out to dynamic subscribers
+        Assert.Contains("TryWriteSubscription", publishInterceptor.Source);
         // TaskWhenAll should have task array and sync completion check
         Assert.Contains("var tasks = new", publishInterceptor.Source);
         Assert.Contains("IsCompletedSuccessfully", publishInterceptor.Source);
@@ -107,6 +111,8 @@ public async Task Publish(IMediator mediator) {
         Assert.Contains("InterceptPublishAsync_ItemDeleted_", publishInterceptor.Source);
         Assert.Contains("GetPublishHandlersForType", publishInterceptor.Source);
         Assert.Contains("Mediator)mediator).Registry", publishInterceptor.Source);
+        // Should fan out to dynamic subscribers
+        Assert.Contains("TryWriteSubscription", publishInterceptor.Source);
         // FireAndForget should use Task.Run
         Assert.Contains("Task.Run", publishInterceptor.Source);
         // And swallow exceptions