NV ToolkitFormat · Validate · Convert

Changelog

What actually changed on NV Toolkit, newest first. Each entry is taken from the repository history for that date, so you can see when a tool arrived, when a page was consolidated or redirected, and when something was fixed.

Why this page exists

A site that keeps claiming to be “updated regularly” without ever saying what was updated is asking for trust it has not earned. This page is the record instead: dated entries, written from the commit history, describing the change rather than advertising it. It is deliberately short on adjectives — if a release only fixed a contrast ratio and a footer heading, that is what the entry says.

— New tools, consolidated pages, trust pages

  • Consolidated near-duplicate pages onto single canonical tools, with 301 redirects from the retired URLs.
  • New JSON tools: JSON builder, JSON repair, JSON size calculator, JSON Schema validator (Ajv) and a JSONPath tester.
  • New converter: vCard to JSON.
  • New CSS preprocessor converter running the real compilers — dart-sass and less.js — rather than a text approximation.
  • Dedicated direction pages for the WebP converters (to and from WebP).
  • New text tools, plus a set of worked cron expression examples.
  • Blog topic hubs so guides are grouped by subject, plus ten new guides: escaping single quotes in SQL, escaping versus parameterized queries, JSON minify versus gzip, validating JSON against a schema, YAML multi-line strings, HTML entities, Sass/SCSS/Less/Stylus, URL encoding, and two comparison pages (FreeFormatter alternatives, JSON Crack alternative).
  • Every guide now opens with a short answer, lists its sources and states how its examples were tested.
  • Related tools are now reciprocal (six per page), every tool page links its whole family and the guides that explain it, hubs open with a "Start here" row, and the footer was trimmed to the most-used links.
  • Recently used tools appear under the workbench (stored only in your browser); cron expressions can be shared as links.
  • Added this changelog, the editorial policy, /llms.txt for AI agents and a security.txt.

— AdSense remediation and content depth

  • Worked examples on tool pages are now generated by running the real transform, and a test fails the build if a published example drifts from the tool's output.
  • Expanded the written guides and added related-guide links between tools and articles.
  • Rewrote the About and Contact pages so the person behind the site, the build process and the funding model are stated plainly.
  • Added a privacy note to the tool pages restating that pasted data never leaves the browser.
  • Performance work across the site (loading, layout stability and script cost).

— Consent Mode and advertising configuration

  • Added Google Consent Mode: advertising and analytics storage stay denied by default until consent is given.
  • Moved the AdSense configuration into environment variables and published ads.txt.

— Workbench refinements

  • Refined the workbench UX shared by every text tool (toolbar, editor panes and error reporting).
  • Added a production environment configuration for deploys.

— Rebrand, performance and mobile fixes

  • Rebranded the site to NV Toolkit with new assets and icons.
  • Made transforms async and lazy-loaded the heavy parsers, so each tool downloads only the engine it needs.
  • Added a batch of new tools alongside an SEO and UI audit.
  • Fixed the mobile navigation drawer and the desktop mega-menu behavior.
  • Increased muted text contrast to meet the WCAG AA contrast ratio, and fixed the footer heading order.

— First release

  • Initial Next.js application: the registry-driven tool catalog, the shared editor workbench and the static export pipeline.
  • Set the canonical site URL and shipped the first deployment to Cloudflare Workers.

About the dates on other pages

The “last updated” date shown on a tool page or a guide, and the dateModifiedemitted in its structured data, reflect a real change to that page's content. They are not bumped site-wide on every deploy to look fresh: a rebuild, a dependency upgrade or a change to an unrelated page leaves them alone. If a date moved, the words, the example or the behavior on that page moved with it.

How each change is checked before it ships is described in the editorial policy. If something here looks wrong, or you want to know what happened to a page that used to exist, get in touch.