How to use ronutz

The tools

Every tool in the catalogue computes in your browser and sends nothing anywhere: paste or type the input and the result appears, with an Example button that fills a known-good input and a Clear button beside it. The tools index opens three ways in: paste what you have, and the box lines up the tools that recognise the shape of what you pasted; choose by what you need to do (decode, understand, compute, build, check); or follow a workflow that takes one thing from tool to tool, a CIDR to a firewall rule, a certificate to the headers a browser enforces.

The index has three floors, stated on the page: the main floor, where every tool has a fixed shape and golden test vectors; the green room, for tools whose form is still settling; and the red room, the one place a tool can send your input out, to the official service named on screen, and only when you ask. Each tool has a documentation page, readable as a web page or as Markdown, and the same logic is described as an API with a machine-readable specification.

Start with:The tools index · Paste what you have · The API

Learn

The Learn library is the explanation behind the tools: articles grouped by subject, in the same taxonomy the tools use, each citing the documentation it was written from and linking the tools that compute what it describes. The hub can be read two ways, Guided or Directory. Guided asks what you want to do (understand a subject, learn something in order from the start, prepare for an exam, work with a particular platform, find a definition fast) and sends you to the right door; Directory lists every article by subject in reading order.

Around the articles sit the Article series, subjects told in order from an opener through their parts; the Stories, longer pieces that argue a point; The Practice, about the work rather than the technology (triage, escalation, change, the human side); the Glossary, with a definition for every term the articles and tools use; and the People, the engineers and authors behind the protocols. In any article, the first mention of a technical term carries a dashed underline you can hover or tap for a short definition; that hint can be switched off in Settings.

Start with:The Learn hub · Article series · The glossary · The Practice

Study guides and certification guides

A study guide is a reading path: the articles to read, in order, with one sentence saying what you will understand at the end, grouped into families (protocols and foundations, identity and security, application delivery, vendor platforms). Each path opens on its first article, and every article in it links back to the path, so you can leave and return without losing your place.

The certification guides are the same material arranged against a vendor exam: the exam's own code and objectives, with the articles and tools that cover each objective. They are reading plans, not exam dumps; where an objective has no coverage yet the guide says so in its place, and a build check fails if one is left silent, which is how the gaps stay visible when the exams change.

The page opens with the training series: fundamentals in order, one level at a time, each a set of modules with a stated outcome, its parts in reading order and the tools to practise on, and a page of its own that starts it. That makes five ways to read in order, each with its own job: a training series takes one level of a curriculum, module by module; an article series tells one subject from its opener through its parts; a reading path gathers published articles toward one understanding; a certification guide maps one exam's objectives to the articles that cover them; a story argues one case across several pieces.

Start with:The training series · The study guides · The certification guides

The vendor hubs

A vendor hub is one page per vendor family that gathers everything the site holds for it: the tools that decode or compute that vendor's formats, the articles grounded in its documentation, its place on the industry record and its lineage of acquisitions and renames. If you work on one platform all day, its hub is the page to bookmark.

Where the author teaches a vendor's official courses, the hub says so and links the training page, which routes to Red Education; where he does not, the hub says nothing about teaching, by rule. Naming a vendor on this site is never a claim of a relationship with it.

Start with:All the hubs · Training

The industry record

The industry record is a chronology of the organisations that built networking and security, in the order their stories begin, each with its founding year, its sources and, where it applies, who bought whom and for how much. Six ways in sit before the list: follow a company, follow a lineage, explore an era, the Brazilian ecosystem, where the author's own path crossed it, and the people. Each is a filtered view with its own address, so it can be shared.

The career chapters are the author's own record, one chapter per company he worked inside or alongside, with the credentials of each; the people timeline runs from the voltaic pile to the present. A method page states the rules every entry follows (what counts as a source, what founded means, how an acquisition is recorded, what is done with an uncertain date) and names the build checks that enforce them. A correction route on the contact page is one click from every entry.

Start with:The industry record · The career chapters · How the research is done

Search and shortcuts

The search field in the header, or Ctrl K, opens a dialog that searches tools, articles, guides and pages at once; the pills under the field narrow it to one kind. A hub's own field searches only that hub's world, and a section's field (The Practice, The Roles) only that section, with an Only in pill that one click widens again. Search runs in your browser against an index built with the site; no query leaves your device.

A handful of single-key shortcuts work on every page: press ? to see them, and rebind any of them in Settings. The human sitemap lists every page by world, for the times a map beats a search box.

Start with:Settings and shortcuts · The sitemap

Privacy and what stays on your device

The site sets no cookies and runs no third-party analytics or trackers. Your theme, your language, your shortcut bindings, the glossary-hint preference and a short reading trail live in your browser's local storage, on your device only, and are never sent anywhere; clearing site data restores the defaults. The privacy page lists every key the site writes, by name, and what the server counts in aggregate.

The site is a progressive web app: once visited, your browser can keep it available, and because the tools compute locally they keep working offline. The stats page shows what is most read, from the aggregate counts; the colophon says how the site is built and what every number on it is computed from.

Start with:The privacy page · Stats · Colophon