Release v1.2.0: Newspaper-style layout with major UI refinements

This release transforms PING into a sophisticated newspaper-style digital
publication with enhanced readability and professional presentation.

Major Features:
- New FeaturedPostHero component with full-width newspaper design
- Completely redesigned homepage with responsive newspaper grid layout
- Enhanced PostCard component with refined typography and spacing
- Improved mobile-first responsive design (mobile → tablet → desktop → 2XL)
- Archive section with multi-column layout for deeper content discovery

Technical Improvements:
- Enhanced blog post validation and error handling in lib/blog.ts
- Better date handling and normalization for scheduled posts
- Improved Dockerfile with correct content volume mount paths
- Fixed port configuration (3025 throughout stack)
- Updated Tailwind config with refined typography and newspaper aesthetics
- Added getFeaturedPost() function for hero selection

UI/UX Enhancements:
- Professional newspaper-style borders and dividers
- Improved dark mode styling throughout
- Better content hierarchy and visual flow
- Enhanced author bylines and metadata presentation
- Refined color palette with newspaper sophistication

Documentation:
- Added DESIGN_BRIEF_NEWSPAPER_LAYOUT.md detailing design principles
- Added TESTING_RESULTS_25_POSTS.md with test scenarios

This release establishes PING as a premium publication platform for
AI orchestration and contextual intelligence thought leadership.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

content.bak/posts/2025/02/2025-02-24-latentspace.md

@@ -0,0 +1,37 @@
+---
+title: "Why Latent Space Isn't Enough — and What We're Building Instead"
+description: "Everyone's talking about the next generation of Retrieval-Augmented Generation (RAG) platforms. Latent Space is one of the most polished contenders, offering streamlined tools for building LLM-powered apps. But here's the problem: RAG as we know it is incomplete."
+date: "2025-02-25"
+publishDate: "2025-02-25T10:00:00.000Z"
+author:
+  name: "Anthony Rawlins"
+  role: "CEO & Founder, CHORUS Services"
+tags:
+  - "Retrieval Augmented Generation"
+  - "Gen AI"
+  - "rag"
+featured: false
+---
+
+**The Latent Space Value Proposition**
+Latent Space provides a developer-friendly way to stitch together embeddings, retrieval, and workflows. If you’re building a chatbot or a knowledge assistant, it helps you get to “Hello World” quickly. Think of it as an **accelerator for app developers**.
+
+**The Limits**
+But once you go beyond prototypes, some cracks show:
+
+* Context is retrieved, but it isn’t structured in a reproducible or queryable way.
+* Temporal information — what was true *when* — isn’t captured.
+* Justifications for why something was retrieved are opaque.
+* Context doesn’t move fluidly between agents; it’s app-bound.
+
+**What We’re Doing Differently**
+Our approach (Chorus + BZZZ + UCXL) starts from a different premise: **context isn’t an app feature, it’s infrastructure**.
+
+* We treat knowledge like an addressable space, not just an embedding lookup.
+* Temporal navigation is first-class, so you can ask not only “what’s true” but “what was true last week” or “what changed between versions.”
+* Provenance is baked in: retrieval comes with citations and justifications.
+* And most importantly: our system isn’t designed for a single app. It’s designed for a network of agents to securely share, query, and evolve context.
+
+**Conclusion**
+Latent Space is a great product for teams shipping today’s RAG-powered apps. But if you want to build **tomorrow’s distributed AI ecosystems**, you need infrastructure that goes beyond RAG. That’s what we’re building.
+Why Latent Space Isn’t Enough — and What We’re Building Instead