Using CERMM

Documentation

Runbooks, how-tos, the network, vendors. Written in Markdown, kept on the server with every version, and linked to the machines they're about.

Writing

• Markdown, with HTML where you need it. Callouts, code blocks with Copy, task lists and a table of contents.
• Folders (type a new one to make it), tags and pins.
• Images: paste, drop or upload. Raster images only (no SVG), checked by their first bytes, up to 15 MB. Images from other sites become links.
• n on Docs starts a new doc; e edits the one you're reading.

An empty Docs offers templates (Runbook, How-to, Vendor): structure only, no sample content. You need the Edit docs privilege to write.

Versions and two people at once

• Every save is a version. The last 50 are kept; History shows them and puts one back.
• A save names the version it started from. If someone else saved in between, you're asked: copy mine, or save anyway. Nobody overwrites anyone by accident.
• An unsaved edit is kept in your browser until you save it.

Linked to machines

• A device's page lists its docs, and docs that mention it by name.
• New runbook on a device's page starts one filled in with what CERMM knows: address, OS, hardware.

Safe to show

Rendered Markdown is cleaned (DOMPurify) before it's shown, and uploaded images are served sandboxed. Docs are in the title bar's search and in the audit log.