added architecture page based on dk.org

Signed-off-by: bidi <bidi@apidemia.com>

Author: bidi47

config/autoload/local.php.dist

@@ -80,13 +80,14 @@ return [
     // and is routed in Light\App\RoutesDelegator. Re-adding it here registers the path twice.
     'routes' => [
         'page' => [
-            'contact'  => 'contact',
-            'api'      => 'api',
-            'admin'    => 'admin',
-            'queue'    => 'queue',
-            'light'    => 'light',
-            'frontend' => 'frontend',
-            'dotboost' => 'dotboost',
+            'contact'      => 'contact',
+            'api'          => 'api',
+            'admin'        => 'admin',
+            'queue'        => 'queue',
+            'light'        => 'light',
+            'frontend'     => 'frontend',
+            'dotboost'     => 'dotboost',
+            'architecture' => 'architecture',
         ],
     ],
     'twig'   => [

src/Page/templates/page/api.html.twig

@@ -63,7 +63,10 @@
             </div>
 
             <div class="pipeline">
-                <div class="pipeline-label"><span>Request lifecycle</span></div>
+                <div class="pipeline-label">
+                    <span>Request lifecycle</span>
+                    <span><a href="{{ url('page::architecture') }}">All 19 stages →</a></span>
+                </div>
                 <div class="pipeline-track">
                     <div class="pl-packet" aria-hidden="true"></div>
                     <div class="pl-step"><span class="name">CORS</span><span class="tag">mezzio-cors</span></div>
@@ -227,9 +230,22 @@
                     </div>
                     <p class="lede">Scheduled work that refuses to trample itself.</p>
                     <p class="desc">
-                        Console commands are registered through <code>dot-cli</code> on top of Symfony Console. The file
-                        locker, enabled by default, writes a lock file per command so a second instance cannot start
-                        while the previous run is still going - the safeguard cron jobs usually lack.
+                        Console commands are registered through <code>dot-cli</code> on top of Symfony Console, and
+                        <code>php ./bin/cli.php route:list</code> prints every endpoint the application exposes. The
+                        file locker, enabled by default, writes a lock file per command so a second instance cannot
+                        start while the previous run is still going - the safeguard cron jobs usually lack.
+                    </p>
+                </div>
+
+                <div class="card" style="--accent:var(--brand-red)">
+                    <div class="card-top">
+                        <div><span class="kicker">Operations · Mail</span><h3>Transactional email</h3></div>
+                    </div>
+                    <p class="lede">Account mail that works before you configure anything.</p>
+                    <p class="desc">
+                        <code>dot-mail</code> wraps Symfony Mailer with templated messages, so account activation and
+                        password reset send out of a fresh install. It joins the request flow only where it is needed -
+                        the rest of the pipeline is unchanged whether a route sends mail or not.
                     </p>
                 </div>
 
@@ -305,12 +321,19 @@
                     API versions. The same codebase evolves gradually and clients are given notice, instead of every
                     change forking into another branch you have to keep alive.
                 </p>
+                <p class="lede">
+                    The mechanism is <code>DeprecationMiddleware</code>: mark a handler with the
+                    <code>#[ResourceDeprecation]</code> attribute and the response carries <code>sunset</code> and
+                    <code>link</code> headers, so a client learns an endpoint is retiring from the endpoint itself
+                    rather than from a changelog it never read.
+                </p>
                 <p class="lede">
                     Full versioning stays reserved for major, format-level changes - the cases where it genuinely earns
                     its maintenance cost. The two approaches are not mutually exclusive.
                 </p>
                 <div class="hero-ctas">
                     <a class="btn btn-ghost" href="https://docs.dotkernel.org/api-documentation/v6/tutorials/api-evolution/" target="_blank" rel="noopener">API evolution guide</a>
+                    <a class="btn btn-ghost" href="{{ url('page::architecture') }}">Where it sits in the pipeline</a>
                 </div>
             </div>
             <div class="callout">