Home

Editorial

modu.tools Editorial

modu.tools Editorial maintains guides and tool documentation for the site. Pages ship when the copy matches the live tools and cites sources for published rules and limits.

modu.tools Editorial is the brand name for the people who write and maintain this site’s guides and tool documentation. It is not a separately marketed consultancy and we do not publish a headcount, named staff roster, or credential list. When a page needs an author byline, it points here: modu.tools Editorial.

What we publish

The Korean writing toolkit (character and byte counting, Revised Romanization, messaging limits) and the developer data workbench (JSON, CSV, YAML, URL encoding, Base64, hashing) are the primary subjects. Each public guide is meant to answer a concrete question a reader already has—how many bytes a Hangul syllable takes in UTF-8, why a CSV opens with mojibake in Excel, how Revised Romanization treats tensification—rather than to pad word count.

Tool pages explain what the browser-local UI actually does. If a control, limit, or error message is not in the shipping code, it does not belong in the copy.

How we research

Claims about language rules, messaging products, encodings, and web platform APIs are tied to primary sources that appear in guide frontmatter. Typical citations include:

  • National Institute of Korean Language materials: Hangul Orthography, the Revised Romanization of Korean, the Standard Korean Language Dictionary, and Online Ganada answers when a spacing edge case needs an official reply
  • Kakao Business documentation and SOLAPI guides for KakaoTalk / AlimTalk and SMS-style byte limits
  • RFCs such as 3986 (URI), 4180 (CSV), 4648 (Base64), 8259 (JSON), 3629 (UTF-8)
  • MDN and the WHATWG URL Standard for encodeURIComponent and form encoding behavior
  • NIST and related security publications when we discuss hash algorithms

We quote limits and rules as those documents state them on the date we checked. Product UIs change; when a vendor page and a gateway disagree, the guide says so instead of inventing a single “correct” number.

How examples are verified

Worked examples in guides and tool docs are checked by running the same logic the site ships—or an equivalent Node/browser API—before publication. URL percent-encoding samples are compared to encodeURIComponent / URLSearchParams. JSON, CSV, and YAML examples are parsed with the project’s tool modules. Hash digests are compared to Web Crypto or crypto digests. Geometry claims for the image tool use the same crop and resize helpers as the page. If an example cannot be reproduced, it is removed or rewritten.

Dates, updates, and corrections

Every guide carries published and updated fields. The updated date moves when substantive wording, tables, or limits change—not for trivial typography alone. The changelog records what shipped in each round so readers can see what changed without digging through git.

If you find an error, email contact@modu.tools with the page URL, the sentence that looks wrong, and a primary source when you have one. We aim to review reports and reflect confirmed fixes in the guide and the changelog. We do not invent staff names on correction notices; updates stay under this editorial brand.