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.
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.
What exists today
Right now, the support section is intentionally small. The app is at a beta release candidate stage, so the first priority is building out the in-app support flow and testing it with real content before expanding the rest of the library.
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.
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.