First-party creative platform · source-reviewedCustom web publishing, content architecture and digital media

Half Tank Heart: an artist website built around verified music and approved media

A growing independent music catalog needed a coherent artist identity, discoverable music and editorial pages, approved artwork, working listening paths and a maintainable publishing process without pretending every draft recording or streaming destination was publicly released.

Half Tank Heart — original music project by Curtis Lancaster

Half Tank Heart approved transparent artist logo
Approved artist logo copied from the original source repository

First-party creative website / November 2026 source review

A place for the music, not a collection of placeholder links.

Half Tank Heart combines a release-aware recording catalog, written-source lyrics, artist stories, artwork, listening pathways and verified music destinations in an accessible static website.

Separate music-production, visualizer and lip-sync tools are still under development. This case demonstrates web publishing and media architecture; it does not claim those tools are publicly launched.

Scope

What the work covered

  • Python static-site generator with accessible HTML and progressive-enhancement JavaScript
  • Fourteen selected recording pages with verified Spotify destinations and editorially sourced lyrics
  • Nine music stories, four illustrated listening paths and separate song-versus-release artwork
  • Original approved artist photos, avatar and transparent logo with source provenance
  • Canonical URLs, Open Graph previews, JSON-LD, sitemap, robots and keyboard-readable navigation
  • Automated source validation, content exclusions and documented static deployment checks
  • Cross-brand references to original game soundtrack development without an unverified soundtrack release claim

Case detail

Publishing depends on verification, not the size of the archive

The November 20 source snapshot exposes fourteen selected recordings with verified Spotify destinations and excludes nine withdrawn or unpublished recordings. That distinction is enforced in the generated public catalog, navigation, lyrics, visuals and sitemap.

Case detail

A music website needs more than a generic discography

The implementation connects recording detail pages with contextual written-source lyrics, nine editorial stories, four guided listening paths, separated release and track artwork, an artist bio, press materials and platform links. The final recordings still require a separate word-for-word lyric check.

Case detail

Brand assets have a traceable source

The website repository carries the approved transparent logo, musician photographs and illustrated avatar as distinct asset types. Optimized song artwork preserves its Drive source and checksum record rather than treating a generated approximation as the original.

Case detail

Source work and production acceptance are separate

Python build and test commands, deployment scripts, accessibility QA and origin checks document the release process. Related audio, visualizer and lip-sync tooling is being developed in separate repositories; a code commit is not proof those tools are available to artists or visitors.

See the same pattern?

Start with the current website or system—not a predetermined package.

Use the free website review for a public baseline or book a call when the issue includes hosting, campaigns, CRM, access, migrations or delivery operations.

CallFree reviewFind a starting point