Version 1.9.0
This major platform release establishes the permanent SPM Release Notes System: a reusable publishing template, dedicated version archive, dual-date history, editorial and search metadata, release-specific navigation, and a tested record of the platform's growth.
Release Highlights
One Permanent Template
Every new release begins with the same approved SPM structure, design, metadata, navigation, and quality baseline.
A Reconstructed Platform History
Thirteen earlier milestones now document the path from version 1.1.1 through 1.8.2.
Dedicated Release Architecture
/release-notes/
Release notes moved out of the Blog hierarchy into their own permanent top-level destination. The previous /blog/release-notes/ address redirects visitors to the new location.
One Folder Per Release
Each release uses /release-notes/<version>/index.html and a matching canonical URL. Individual pages remain easy to share, index, analyze, and maintain.
Release Navigation Replaces Blog Distractions
The general blog sidebar was replaced by an On This Release menu and chronological release history, keeping every supporting link relevant to the document being read.
Reusable SPM Template
Release Identity at a Glance
The hero presents version, stability, summary, historical release date, publication date, author, and release type in one recognizable SPM card.
Scannable Without Becoming Shallow
Release Highlights serve everyday readers, while labeled feature sections, technical foundations, testing notes, and Known Limitations preserve the detail required for a dependable platform record.
Shared SPM Components
Universal navigation, Control Center, cookie consent, content sharing, Back to Top, footer, search panel, translation, accessibility, and glass styling remain part of the standard page foundation.
Dual-Date Standard
Historical Milestone Date
spm:release-date records when the platform work reached its historical milestone, even when the release-note page is written later.
Document Publication Date
spm:published-date, Open Graph article time, and Schema.org datePublished record when the release-note document itself becomes public.
Revision Date Preserved Separately
spm:updated-date, Open Graph modified time, and Schema.org dateModified identify later document maintenance without rewriting the original milestone.
Editorial and Search Metadata
Search identity: Every page uses spm:source-type="spm_page", a version-specific source ID, spm:content-type="release_note", status, author, version, release type, summary, description, tags, credit, language, and the spm_general_v1 metadata standard.
Public discovery: Canonical, description, Open Graph, X card, featured image, publication times, and Schema.org TechArticle data provide consistent signals for browsers, social platforms, and search systems.
Editorial classification: Release Note is a first-class content type rather than being hidden inside a general Article classification.
Theme and Component Compatibility
Light and Dark Tested
Every reconstructed release was installed and tested in both themes. The purple hero now explicitly keeps its copy white, with a lavender version accent, regardless of the surrounding page theme.
Theme Flash Prevented
An early theme initializer normalizes the stored os value to auto and applies the proper Bootstrap theme before the page is presented.
Verified Bootstrap Icon Names
The invalid bi-radio reference was removed from the standard. Radio actions use the supported bi-broadcast-pin icon.
Repeatable Publishing Workflow
New pages: A newly created version uses the base filename spm-release-notes-<version>.html. Updated deliverables add -revN so browsers, downloads, and local copies can distinguish the corrected file.
Required checks: Page structure, unique IDs, internal anchors, JSON-LD, inline JavaScript, metadata values, dates, canonical URLs, version references, icon names, stale content, and the SPM no-em-dash standard are validated before delivery.
Production confirmation: Each page is then installed and tested in Light and Dark themes, followed by sidebar and pagination updates across the archive.
Reconstructed Release History
The completed archive now documents 1.1.1 Original Platform Update; 1.2.0 Internet Radio Player; 1.3.0 Responsive Media Carousel; 1.4.0 Theme System; 1.4.1 Global Experience and Privacy; 1.5.0 Image Gallery Engine; 1.5.1 Expanded Gallery Experiences; 1.5.2 Navigation and Accessibility Utilities; 1.6.0 Control Center; 1.7.0 Editorial Engine Foundation; 1.8.0 Search Database Foundation; 1.8.1 Search Ingestion and Source Integration; and 1.8.2 Production Content Inventory.
Version 1.9.0 becomes the fourteenth page and documents the release system that made the permanent archive possible.
Known Limitations
Release hub delivered
The redesigned release hub and complete selectable archive were delivered after this release. This historical limitation is now resolved.
Cross-page navigation currently requires coordinated updates
Publishing a new release requires adding its entry to earlier sidebars and adding a Next link to the previously newest page. These steps are repeatable but remain manual.
Historical notes depend on preserved evidence
Reconstructed releases are limited to available project records, implementation files, test results, and approved decisions. Details that cannot be supported should not be added merely to make a release appear more complete.
The template does not replace editorial review
Consistent structure and automated checks reduce mistakes, but release scope, technical accuracy, plain-language explanations, limitations, and final production approval still require human review.