forty developer tools, built as static pages

tech · 2026-11-02 · 4 min

a developer usually does not need another platform to format a JSON sample, compare two timestamps or generate a UUID. They need a small tool that opens quickly, explains what it does and does not send their input somewhere else.

dev.eneawork.it is a collection of forty focused utilities for that kind of task. The tools cover generators, JSON and data, encoding and security, text, web and time, and systems. A searchable catalogue, category filters and a keyboard shortcut make the collection easier to scan than a list of unrelated bookmarks.

pages first, JavaScript second

the site is built from prerendered HTML, hand-written JavaScript, self-hosted fonts and an offline cache. It does not wait for framework hydration before the page becomes useful. The interface describes the collection as static and fast; the individual tools run in the browser, so there is no account or upload step between an input and its result.

that is a deliberate architectural choice, not a claim that JavaScript is unnecessary. The page can show its structure before the interactive code runs, and the script handles the parts that need interaction: filtering, search, keyboard navigation, copying and each tool's calculation. The site documents Ctrl+K (or Command+K) as a way to jump to a tool, with copy, sample and clear actions available close to the work.

one toolbox, not one giant tool

the utilities stay small and independent. A JSON formatter should not need the same workflow as a CIDR calculator or a timezone planner. Keeping each task focused makes the entry point simple: search for the result you need, open that tool, and leave when you are done.

the same separation has a limit. These are quick browser utilities, not a shared development environment: the site does not promise an account, synced inputs or a server-side history. If a task needs a persistent project, team workflow or integration with a production system, a focused local utility is the wrong tool.

what i wanted to optimize

the useful measure was not how many features could fit on one screen. It was how few steps sat between a question and a result, without hiding where the input goes. Static HTML gives the page a useful starting point; browser-side code keeps the tools immediate; an offline cache helps after the first visit.

forty tools can easily become forty reasons to leave. Search, categories and a shared interaction pattern turn them into one workbench, while the separate pages keep each job understandable. That is the shape of the project: not a framework for building tools, but a lightweight place to use them.