Servers & infrastructure Practical
Sending email yourself, or handing it over
Run your own mail server and the invoice is near zero — you pay in deliverability instead. Which is cheaper depends on what one enquiry is worth to…
Technote
9 articles· Servers & infrastructure · Founders
Servers & infrastructure Practical
Run your own mail server and the invoice is near zero — you pay in deliverability instead. Which is cheaper depends on what one enquiry is worth to…
Servers & infrastructure Practical
If a customer tells you the site is down, you are already late. Deciding what to watch and how to be alerted takes about half an hour.
Servers & infrastructure Practical
If you sell online in Korea, displaying business registration details is a legal requirement — and it is also the first thing a visitor about to pay looks…
Servers & infrastructure Intro
A website solves a specific set of problems. If you are not yet at that stage, validating demand another way is faster and teaches you more.
Servers & infrastructure Intro
Domains are cheap; changing one is not. The choices that cause trouble years later share a pattern, and all of them are checkable before you buy.
Servers & infrastructure Intro
You do not move because a VPS is better — you move because something is blocked. The signals are specific, and what grows after the move is responsibility,…
Servers & infrastructure Intro
Installing takes five minutes; the ten minutes after it decide the next year. One search-visibility setting in particular keeps your site out of search entirely if you miss…
Servers & infrastructure Intro
Comparing monthly rates alone never matches what you actually spent after a year. Traffic, backups, mail and renewal pricing sit outside the headline figure — count them first.
Servers & infrastructure Intro
Knowing what this choice decides later saves you the cost of moving a year from now — the difference between shared hosting and a server most of all.
Cited
Topics outside WordPress are collected on Dongji Communication Tech Insights, run by the same team. The summaries below are quoted from the originals; the titles link to them.
Working with AI
Writing a CLAUDE.md — teaching an AI coding assistant your project
AI coding tools such as Claude Code, Cursor and Copilot do better work the more precisely they know your project. Here is a structure and a set of principles that hold up.
Working with AI
Prompting an AI for UI design — drafting with Claude and GPT
Asking an AI to "make a nice button" gets you a disappointing button. Structured prompts that carry constraints, references and a defined role get you the design you meant.
Themes & plugins
SCSS from the ground up — variables through module structure
The core syntax of SCSS (Sass) and what it solves that plain CSS cannot: variables, nesting, mixins, @use and module structure — organised around patterns you can use immediately.
Themes & plugins
Design tokens and theme colour systems — brand identity in SCSS variables
How to turn a colour palette from a pile of hex codes into a system that means something — semantic token structure and SCSS variable patterns, from a real project.
Performance optimization
Designing a responsive typography system — the science of readability
Hard-coded pixel font sizes are over. Type scales, fluid sizing with clamp(), Korean webfont optimisation and line-height ratios — building typography that reads well on any screen.
Development workflow
From Figma to SCSS — a designer-developer handoff guide
Minimising what gets lost between a Figma file and the code: extracting tokens, naming components, keeping the spacing system in sync — the whole workflow, step by step.