惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Y
Y Combinator Blog
Jina AI
Jina AI
雷峰网
雷峰网
有赞技术团队
有赞技术团队
WordPress大学
WordPress大学
美团技术团队
V
V2EX
酷 壳 – CoolShell
酷 壳 – CoolShell
小众软件
小众软件
博客园 - Franky
博客园 - 三生石上(FineUI控件)
月光博客
月光博客
博客园 - 叶小钗
大猫的无限游戏
大猫的无限游戏
爱范儿
爱范儿
Hugging Face - Blog
Hugging Face - Blog
宝玉的分享
宝玉的分享
Last Week in AI
Last Week in AI
Apple Machine Learning Research
Apple Machine Learning Research
量子位
IT之家
IT之家
人人都是产品经理
人人都是产品经理
博客园_首页
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Dev Log: 2026-06-26 — Config-Driven Billing, an App-Wide ...
Nasrul Hazim Bin Mohamad · 2026-06-26 · via DEV Community
Cover image for Dev Log: 2026-06-26 — Config-Driven Billing, an App-Wide Rebrand, and Branded Error Pages

Nasrul Hazim Bin Mohamad

TL;DR

  • Pushed commercial rules (free seats, bulk seats, tax) out of code and into config + a BillingProvider contract.
  • Did a full app-wide rebrand — favicons, PWA manifest, logo components — the kind of change that's 80 files but one idea.
  • Shipped branded error pages (401–503) and a richer project overview with clickable stats.
  • Theme of the day: centralise the thing that changes, so the next change is an edit, not a hunt.

A wide day across the platform — four threads, none of them huge alone, but each one a small lesson in where a thing should live.

Thread 1 — Billing rules are data, not code

The biggest architectural thread: free-seat defaults, bulk seat purchases, and tax all moved behind a BillingProvider contract with manual and Stripe drivers. The number of free seats is now config (or a live admin setting); tax is the provider's job, delegated to Stripe Tax on the self-serve path. I wrote this one up on its own — the short version: if a value is a business decision, it doesn't belong in an if statement.

Thread 2 — An app-wide rebrand is one idea wearing 80 files

Rebranding touched favicons, Apple touch icons, maskable PWA icons, the web manifest, browserconfig, and the logo Blade components. It looks like a massive diff, but the trick is that the brand lives in one place: a couple of <x-app-logo> components and a manifest. Swap those, regenerate the icon set, and the whole app follows. TL;DR: if a rebrand means editing 80 hand-placed logos, that's the real bug — centralise the mark first, then a rebrand is a single asset swap.

Thread 3 — Error pages deserve the same care as happy paths

Added branded pages for 401 through 503. Default framework error pages are fine functionally but feel like falling off a cliff. A consistent layout with the product mark and a footer keeps users oriented even when something broke. Cheap to do, disproportionately reassuring.

Thread 4 — Make the dashboard clickable

The project overview got enriched: stats are now clickable into the thing they count, recent issues open in a new tab, and the list grew a peek flyout so you can glance at a project without leaving the page. Small UX seams, but they shave clicks off the most-used screen.

The through-line

Three of today's four threads are the same move: find the value (or asset, or layout) that changes often, give it one home, and let everything else read from there. Config for billing numbers, a logo component for the brand, a shared layout for errors. The day's diff was wide, but the principle was narrow.