Content Platform

A personal brand and publishing operation I designed, built, wrote, and sell from.

kxtx is not a portfolio demo dressed up as a product. It is a working publishing operation: I write the blog, run the shop, design the products, and handle the marketing. The platform is custom because off-the-shelf tools kept getting in the way of the actual work.

The site has three parts that should not be forced into the same template: a blog, a shop, and serialized fiction. Each one gets its own data flow, presentation model, and voice.

What I made

• The brand identity, tone, and overall creative direction for the site
• All editorial content: blog posts, fiction, and marketing copy
• Original apparel designs sold through the shop

What I built

• A Markdown to JSON to UI pipeline for the blog, backed by a Python CLI that scans posts, rebuilds indexes, creates PHP stubs, and updates the sitemap in one pass
• A Shopify Storefront API integration with server-side caching, featured products, and Markdown editorial blocks on product pages
• A fiction section where each work can have its own fonts, colors, CSS, and reader treatment
• Page-level flags for loading only the JavaScript a given page needs
• A hub-and-destination design approach: indexes stay quiet, individual works get their own voice

What this demonstrates

• Custom content pipelines from Markdown to structured data to rendered UI
• PHP template architecture for hubs, posts, products, fiction, and shared layout
• API integration with caching and editorial content layered into product views
• Conditional JavaScript loading based on page-level behavior instead of global bloat
• Interface systems that let different content types have distinct presentations without breaking the platform