Support for Siteimp
Clear, practical help for using Siteimp, with more support material being added as the beta release candidate settles.
Support built around the application
In-App Support
The first support section now live is In-App Support , a growing library of page-by-page guidance that mirrors the help built directly into the application.
These documents are designed to answer three simple questions: what is this page for, what can I do on it, and how do I use it? If you are learning the app or trying to understand a specific workflow, start there.
Using support inside Siteimp
Using In-App Support
The Using In-App Support section explains how Siteimp’s built-in help system works, including how to open the HelpDrawer, read page-specific support documents, run diagnostics, and contact technical support from inside the app.
These guides focus on the support workflow itself. They explain what happens when a support request is prepared, what information can be included, how Formimp delivers requests, and how diagnostics help turn support into a clearer conversation.
Local support tools
Siteimp Log Workbench
The Siteimp Log Workbench is a browser-only support tool for formatting, inspecting, filtering, saving, and comparing Siteimp NDJSON logs locally.
It is designed for support cases where a user has copied or saved a Siteimp run log and wants to inspect it before sharing anything. Files are read by the browser, logs are not uploaded to Siteimp, and saved workbench logs stay in the browser's local storage until cleared.
What support will look like
Siteimp is now close enough to release that support content needs to be treated as part of the product, not an afterthought. This section will grow alongside the application and focus on practical help rather than filler.
Page-by-page guidance
Each support document will explain a single screen or workflow in plain language, with a focus on what the page is for, what you can do there, and how it fits into the larger application.
Direct support from the app
Siteimp includes direct support contact inside the application itself. That means users can ask for help from the screen they are already on, instead of trying to describe the interface from memory.
Website and app working together
The support material published here is also designed to support the in-app experience. Over time, the web and application versions will reinforce each other instead of drifting apart.
Local-first support tools
Some support problems are easier to understand with structured data. Siteimp support tools are designed to help users inspect files locally before deciding what, if anything, they want to share.
What exists today
Right now, the support section is intentionally focused. The app is at a beta release candidate stage, so the priority is building support surfaces that are useful immediately: in-app help and local tools for real support workflows.
In-App Support
A dedicated support section for the screens and workflows built into Siteimp itself. This is the first major support surface and will grow one page at a time.
Using In-App Support
A practical guide to the support experience inside Siteimp, including the HelpDrawer, technical support requests, diagnostics, and Formimp delivery.
Siteimp Log Workbench
A browser-only NDJSON formatter and support workbench for Siteimp run logs. Paste a log or open a local file, then format records, filter by event code or operation ID, save logs locally, and compare saved logs.
Why this section exists
Siteimp is a local-first Windows application for inspecting websites, monitoring changes, and collecting evidence about content, performance, accessibility, and best practices. A tool like that needs support content that is just as deliberate as the product itself.
That means support here is not just a parking lot for troubleshooting notes. It is part of the product experience. Good support should make the application easier to understand, easier to trust, and easier to use well. This section is being built with that goal in mind.
The support tools follow the same idea. When a log or diagnostic file can help explain what happened, users should be able to inspect it locally first, understand what they are looking at, and share only what is useful.