Library and editor
This web editor is maintained separately from the upstream WireViz project. The library reference describes WireViz 0.4.1, the version bundled with the editor. Editor guides describe the controls in this web application. A library feature may be available through YAML without having a dedicated canvas control.
Documentation sources
The reference is checked against the bundled WireViz source, its syntax documentation and tested examples. The upstream syntax reference, tutorials and source provide additional context. Explanations and editor workflows here are maintained alongside the application source so updates can be reviewed together.
Runtime and licenses
WireViz is distributed under GPL-3.0. Its Python package runs in Pyodide; Graphviz WASM renders the output. The complete runtime notices are available in third-party licenses. The optional native service is described in the library CLI guide; it is not a server backend for the hosted editor.
Connector artwork
The included connector illustrations come from Fritzing and SparkFun sources. The library retains original assets, revision information, credits and license texts. See artwork credits. Electrical pin IDs are defined separately from graphical SVG objects; an illustration does not by itself specify the pin functions or guarantee compatibility with a physical part.
Website analytics
We use Vercel Web Analytics and PostHog to understand visits to the editor and documentation. PostHog records page views and which editor actions are used (exporting a file, copying or saving YAML, editing a design), not the content of your harness. Harness YAML is sent only when you submit an order request, so the harness can be quoted. Uploaded images are never sent.
Example designs
Example YAML files are small, tested demonstrations of WireViz syntax. They show how to describe a harness, not a qualified design for a specific electrical load. Confirm the actual connector orientation, pinout and wire requirements for your application.
Accounts and saved designs
Signing in is optional. Account access uses Neon Auth; saved designs store the owner ID, name, original YAML text, revision counter and timestamps in a Neon database. Authentication records contain the email and session information needed for account access. Designs are private to their owner. Saving does not store uploaded images, canvas positions or a history of earlier versions.
Your email is used for sign-in, not automatic marketing enrollment. A temporary YAML draft is written to this browser only when you request a sign-in email; it can be recovered during the sign-in flow for up to one hour. Successful saving clears that draft.