u/Fun-Penalty4762

Data Source: OECD Comparative Tax Revenue Statistics

OECD Data Explorer: https://data-explorer.oecd.org/vis?df[ag]=OECD.CTP.TPS&df[ds]=dsDisseminateFinalDMZ&df[id]=DSD_REV_COMP_OECD@DF_RSOECD

Tools Used:
OECD MCP - for data extraction
PointViz - for visualization

Data Source: OECD Family Database, Table SF1.1.B - Households by number of children (2024) - https://webfs.oecd.org/Els-com/Family_Database/SF_1_1_Family_size_and_composition.pdf

Built with: PointViz (https://pointviz.co)

Interactive Chart: https://www.pointviz.co/c/9ikkejsr

Data Source: OECD Government at a Glance — Public Finance Main Indicators
OECD Data Explorer: https://data-explorer.oecd.org/vis?df[ag]=OECD.GOV.GIP&df[ds]=dsDisseminateFinalDMZ&df[id]=DSD_GOV@DF_GOV_PF_YU&dq=A..GGD.PT_B1GQ.S13.YU.PF

Tools Used:
OECD MCP (https://oecd-mcp.com) — for data extraction

PointViz (https://pointviz.co) — for visualization

Interactive Chart: https://www.pointviz.co/c/j6k4fi8z

Data Source: OECD Analytical House Prices Indicators — Price-to-Income Ratio (2015–2024)
🔗 OECD Data Explorer: https://data-explorer.oecd.org/vis?df[ag]=OECD.ECO.MPD&df[ds]=dsDisseminateFinalDMZ&df[id]=DSD_AN_HOUSE_PRICES@DF_HOUSE_PRICES&dq=.A.HPI_YDH.IX&pd=2015,2024

Tools Used:
• OECD MCP (https://oecd-mcp.com) — for data extraction
• PointViz (https://pointviz.co) — for visualization

Interactive Chart: https://www.pointviz.co/c/fgbxt6v0

After my last post on household wealth distribution, the top comment pointed out something really worth noticing: "Why is Denmark's wealth inequality so high when its income Gini is so low?"

This scatter plot maps both measures for 29 OECD countries to answer exactly that.

Income (what you earn year to year) and wealth (the assets you own) are fundamentally different things.

A crucial caveat for Denmark: OECD's standard wealth stats exclude occupational pension wealth for cross-country comparability (source: OECD WDD main concepts). Because Denmark has a massive mandatory occupational pension system, OECD research explicitly notes that including this pension wealth "significantly lowers wealth inequality in Denmark" (source: OECD, Mapping trends and gaps in household wealth across OECD countries, 2025).

I've been working on a component library for Vue 3 called dlbcodes/ui. It's built on Headless UI with CVA variants and semantic CSS tokens, compound components, that sort of thing. Docs are at https://ui.dlbcodes.com

The thing I keep testing is whether a shared library forces every product to look the same. So I built two templates with it that are meant to feel like different products:

https://assistant.dlbcodes.com/app is soft and conversational, a consumer AI assistant UI.

https://console.dlbcodes.com is a dense Vercel-style dashboard.

Same components underneath, opposite aesthetics. Curious whether that reads or whether the shared DNA is still obvious.

I also put a few of the components into a catalog where you can actually interact with them: https://www.zephr.dev/p/dlbcodes/zephr You can change the props, read the source, and swap the background to see how they hold up on light, dark, and busy surfaces.

What I'd genuinely like to know:

What's missing that you'd expect in a library like this?

Where does it feel unfinished or not thought through?

I've been building a component library (Vue 3, Tailwind v4, Headless UI) with a token-first theming approach, and I wanted a way to actually test how it holds up under different palettes when it's doing real work, not just rendering swatches.

So I built a playground. Edit any semantic token, or pick a preset, and the whole thing reskins live: not just isolated components, but full composed pages like a login screen, and a pricing page.

Playground: https://dlbcodes-playground.vercel.app/
Docs: https://my-design-system-beta.vercel.app/

How the theming is structured, since that's the part I'd most like to discuss:

Two token layers. A primitive palette feeds semantic tokens (--color-bg-surface, --color-text-primary, and so on). You theme by overriding the semantic layer, so "brand color" or "surface" is a single override, never a find-and-replace across components.

Pages are composed from the same components. The login and pricing pages are built entirely from the library's primitives (Panel, Field, Button, Disclosure). The playground's own customizer UI is too.

Runtime CSS variables. Overrides apply instantly with no rebuild, which is what makes the live reskin possible and keeps theming out of the JS layer.

I'll be upfront about where it's at: the component set is still maturing (no Table or dark mode yet), and the API will move between versions. Not pitching it as production ready.

What I'd genuinely like feedback on:

Does the two-layer approach (override semantic, leave primitives alone) match how you'd architect theming, or would you structure it differently?

When you build real pages from a design system, what makes components feel like they compose well versus fight you?

Anything in the playground that breaks or looks wrong under a custom palette?

Last thing, low stakes: it's currently called my-design-system, which is a placeholder. If anyone has a name that isn't terrible, I'm listening.

I want to test whether a problem I think I'm seeing is real or just in my head.

The idea: a tool where you upload a phone photo of your product, pick a visual style (warm lifestyle, studio backdrop, UGC vibe, that kind of thing), and 30 seconds later you get a polished version you could post on Instagram, Pinterest, or your listing. No photographer, no editing skills, no setup.

The pitch in one line: turn a quick phone shot into something that actually looks like a brand spent money on it.

Below is one example of what I mean. Left is the original phone photo. Right is what came out.

What I'd love to know:

Is this something that would actually save you time, or does your current workflow handle this fine? Is product photography the kind of headache that bugs you weekly, or is it a once-a-month thing? Would you pay for something like this, would you only use it free, or would you not use it at all?

Whatever you think, even if the answer is "this isn't a real problem," that's exactly the feedback I need.

If anyone wants to try it on one of your own products, leave a comment and I'll generate a couple of versions for you and send them back in the thread. No catch.

I want to test whether a problem I think I'm seeing is real or just in my head.

The idea: a tool where you upload a phone photo of your product, pick a visual style (warm lifestyle, studio backdrop, UGC vibe, that kind of thing), and 30 seconds later you get a polished version you could post on Instagram, Pinterest, or your listing. No photographer, no editing skills, no setup.

The pitch in one line: turn a quick phone shot into something that actually looks like a brand spent money on it.

Below is one example of what I mean. Left is the original phone photo. Right is what came out.

What I'd love to know:

Is this something that would actually save you time, or does your current workflow handle this fine? Is product photography the kind of headache that bugs you weekly, or is it a once-a-month thing? Would you pay for something like this, would you only use it free, or would you not use it at all?

Whatever you think, even if the answer is "this isn't a real problem," that's exactly the feedback I need.

If anyone wants to try it on one of your own products, leave a comment and I'll generate a couple of versions for you and send them back in the thread. No catch.

Spent the last few weeks building picdash.co . It's a tool for small brands to make trending product photos for Instagram without learning Photoshop or paying $40-100 to a designer every time.

Upload a product photo, pick a "scene" (photo studio, warm lifestyle, Y2K chrome, outdoor, etc.), wait 30 seconds, download. The twist is I add new scenes every week based on what's actually trending on Instagram and TikTok, so users don't have to figure out what's in style.

It went live last week. I'm at 9 scenes, 5 free generations to try, and three paid tiers ($19, $49, $99 per month).

I'm at the stage where I genuinely can't tell anymore if the product is good. I've stared at it too long. So I'd really value an outside eye.

Before/after examples: https://imgur.com/a/uTECB9R

Try it:

1. If you saw this on Twitter or Instagram, would you click it?
2. If you tried it and the result was good, would $19/month feel reasonable for 30 photos?

And anything else you'd want to tell me. Especially the things that would make you bounce.