Sandbox/Version demo/2.0: Difference between revisions

Content deleted Content added

Inline

@@ Line 10: / Line 10: @@
 __NOINDEX__
-{{Warning|1=This is a '''sandbox demonstration''' of the wiki's versioning system. It is not real documentation. See [[Sandbox/Version demo]] for the latest version.}}
+{{Warning|1=This is a '''sandbox demonstration''' of the wiki's copy-on-write versioning system. See [[Sandbox/Version demo]] for the full comparison.}}
 == Notification system (v2.0) ==
@@ Line 54: / Line 54: @@
 * Basic retry logic
+== What you're observing right now ==
-== Still missing ==
+This is the '''second frozen fork'''. Notice:
-* No templating engine (messages still hardcoded)
-* No delivery receipts / read tracking
+* The version dropdown (in the badge strip) shows "2.0" selected.
-* No batching (100 users = 100 individual sends)
+* Selecting "1.0" takes you to the [[Sandbox/Version demo/1.0|earlier fork]]. Selecting "4.0 (latest)" takes you to the [[Sandbox/Version demo|canonical page]].
+* The Cargo table stores <code>IntroducedIn=2.0</code>, <code>DeprecatedIn=3.0</code>, <code>Status=frozen</code>.
+'''Key insight:''' In Docusaurus, when you shipped version 2.0, you ran <code>npm run docusaurus docs:version 2.0</code> and it copied ''every single page'' into <code>versioned_docs/version-2.0/</code> — even pages that hadn't changed. In this wiki, only the pages whose content ''actually diverged'' get a fork. Everything else continues to be served from the single canonical page.
 [[Category:Sandbox]]