Skip to content

Bonumark Stream v0.6.0

Latest

Choose a tag to compare

@jimlunsford jimlunsford released this 13 Aug 15:10

Bonumark Stream v0.6.0

Bonumark Stream v0.6.0 is the next public GitHub release after v0.5.77.

This release brings together the work completed since the last public release without turning the release notes into a package-by-package development diary. The major changes are first-class Profiles, Theme Architecture 2.0, a rebuilt Midnight Ledger reference theme, stronger link-preview and SEO boundaries, upgrade hardening, and improved Profile image delivery.

Highlights

First-class Profiles

Profiles are now a full public identity surface with:

  • headline, About, Now, location, interests, and flexible links
  • Featured Work for published Stream Posts, Pages, and validated external URLs
  • cover images and Profile photo galleries
  • optional public activity details
  • canonical Profile URLs
  • Open Graph, Twitter, and structured Person/ProfilePage identity metadata
  • owner-controlled Profile export to JSON, Markdown, and original local Profile media

Theme Architecture 2.0

Bonumark Stream themes remain code-free, but they can now control validated composition as well as CSS presentation.

Layout Schema 1 supports four public surfaces:

  • Profile
  • Stream Card
  • Site Header
  • Home

Themes arrange registered core components through private JSON layout files. Core still owns behavior, data, routing, permissions, forms, publishing, media, comments, likes, SEO, accessibility semantics, and component rendering.

There is no expression language and themes cannot ship PHP, JavaScript, arbitrary HTML templates, SQL, routes, callbacks, or other executable application logic.

Existing CSS-only themes remain supported through fixed legacy composition fallback.

Midnight Ledger

Midnight Ledger is now the single bundled/default reference theme and uses the complete four-surface Theme Architecture 2.0 stack.

The release includes the responsive Home, Stream Card, Site Header, and Profile work completed during the architecture rebuild, including mobile refinement, canvas alignment, Profile layout resilience, and the current finished Profile composition.

Link-preview and SEO hardening

External preview metadata is kept separate from local document SEO. Remote page titles stay remote, local site-name suffixes are not injected into external link-preview titles, and reusable fragments are no longer processed as if they were complete Bonumark documents.

Profile image delivery

Profile cover and gallery images now use bounded responsive candidates. When the server supports WebP encoding, Profile media can expose modern-format picture sources while retaining safe JPEG/PNG fallbacks.

The Profile cover receives preload/high-priority treatment, while below-fold Profile gallery images remain lazy and low priority.

Upgrade and package hardening

The built-in upgrader continues to support Bonumark Stream v0.4.0 and newer.

The package preserves configuration, database records, Stream Posts, Pages, drafts, scheduled posts, revisions, comments, accounts, media, uploads, settings, analytics, API tokens, scheduled-task history, Local Places, custom themes, and other owner data.

Database changes from v0.5.77

Upgrading from the previous public release adds three migrations:

  • 0015_profile_identity_foundation.php
  • 0016_profile_featured_work.php
  • 0017_profile_photos.php

These create Profile storage and add Featured Work and Profile photo-gallery fields. Existing Stream Post and Page content is not rewritten.

Upgrade notes

Back up the site files and database before upgrading a production installation.

Direct upgrades from v0.1.x, v0.2.x, and v0.3.x development packages are not supported. Those older builds require a fresh v0.6.0 install.

Documentation cleanup

The GitHub-facing documentation has been reorganized for this release:

  • README.md is now a product landing page instead of a development timeline.
  • Root CHANGELOG.md tracks public GitHub releases.
  • _bonumark_stream/CHANGELOG.md retains detailed package-by-package development history.
  • docs/UPGRADING.md puts v0.6.0 upgrade guidance first while retaining older internal notes for maintainer traceability.
  • Architecture and theming documentation describe the current v0.6.0 contracts instead of narrating every intermediate implementation pass.