Sandbox/Version demo/1.0: Difference between revisions
From OHC Network Wiki
More languages
More actions
Content deleted Content added
OHC identity seed |
OHC identity seed |
||
| Line 10: | Line 10: | ||
__NOINDEX__ |
__NOINDEX__ |
||
{{Warning|1=This is a '''sandbox demonstration''' of the wiki's versioning system. It |
{{Warning|1=This is a '''sandbox demonstration''' of the wiki's copy-on-write versioning system. It represents a fictional "v1.0" snapshot to show how frozen forks behave. See [[Sandbox/Version demo]] for the full comparison.}} |
||
== Notification system (v1.0) == |
== Notification system (v1.0) == |
||
| Line 36: | Line 36: | ||
* No opt-out mechanism |
* No opt-out mechanism |
||
* High latency on actions that triggered emails |
* High latency on actions that triggered emails |
||
These limitations were addressed in [[Sandbox/Version demo/2.0|version 2.0]]. |
|||
== What you're observing right now == |
|||
This frozen page demonstrates several things: |
|||
# '''The blue banner above''' — auto-generated by <code><nowiki>{{Version switcher}}</nowiki></code> when <code>status=frozen</code>. It links you back to the canonical (latest) page. |
|||
# '''The metadata badges''' — show "CARE 1.0 – 2.0", meaning this content was valid from 1.0 until it was superseded in 2.0. |
|||
# '''The global dropdown''' (top of the badge strip) — lets you jump to any version. Try selecting "4.0 (latest)" to return to the canonical page. |
|||
# '''<code>__NOINDEX__</code>''' — this page is invisible to search engines. Only the canonical page ranks. |
|||
In Docusaurus, this same "old version" content would be a full copy of the '''entire''' documentation tree — even the 95% of pages that didn't change between 1.0 and 2.0. Here, only this one page exists as a fork because only this page's content diverged. |
|||
[[Category:Sandbox]] |
[[Category:Sandbox]] |
||
Latest revision as of 04:32, 5 July 2026
⚠️ Warning
This is a sandbox demonstration of the wiki's copy-on-write versioning system. It represents a fictional "v1.0" snapshot to show how frozen forks behave. See Sandbox/Version demo for the full comparison.
Notification system (v1.0)
In version 1.0, notifications were minimal:
- Single channel: email only
- No user preferences — all users received all notifications
- Plain text, no templates
- Sent synchronously during request handling (blocked the UI)
Configuration
NOTIFICATIONS_ENABLED = true
SMTP_HOST = mail.example.com
That was it. Two environment variables.
Known limitations
- No delivery tracking
- No retry on failure
- No opt-out mechanism
- High latency on actions that triggered emails
These limitations were addressed in version 2.0.
What you're observing right now
This frozen page demonstrates several things:
- The blue banner above — auto-generated by
{{Version switcher}}whenstatus=frozen. It links you back to the canonical (latest) page. - The metadata badges — show "CARE 1.0 – 2.0", meaning this content was valid from 1.0 until it was superseded in 2.0.
- The global dropdown (top of the badge strip) — lets you jump to any version. Try selecting "4.0 (latest)" to return to the canonical page.
— this page is invisible to search engines. Only the canonical page ranks.
In Docusaurus, this same "old version" content would be a full copy of the entire documentation tree — even the 95% of pages that didn't change between 1.0 and 2.0. Here, only this one page exists as a fork because only this page's content diverged.