How To - Proof websites in Ziflow
Summary: Ziflow allows you to create and review website proofs.There are two types - a simple website snapshot and a live website capture which allows the reviewer to interact as if it were a normal http page.
Available for: Any Ziflow user can create website proofs and any reviewer with view rights can open such proofs.
Where is the feature applied? Website proofs can be created by entering a website URL into the “Review a website” box during the proof creation process. You can choose to take a snapshot or view live content.
How does it work?
Once a website proof has been created you can enter the Proof Viewer to see how it looks. You'll notice that a website snapshot looks exactly the same as any standard image proof. You can begin to review using all the available proofing tools.
You'll notice a small bar at the bottom of the proof viewer.
Proofing live website captures
When proofing live website captures you must remember about few differences in Proof Viewer. First thing you are going to notice in the case of the live website capture proof is small bar at the bottom of the Proof Viewer.
- Interactive mode - allows you to switch between interactive and panning mode. When the arrow button is blue then interactive mode is on. It means that you can browse the proof as it was a normal website (play videos, interact with all the content). If you try to draw a markup or use any other proofing tool, the proof will remain in the panning mode and browsing won’t be possible (interactive mode button will be greyed out). Once the interactive mode is switched back on you can start browsing the proof.
- Refresh - reloads the whole proof to the initial http/s address.
- Website resolution - this option allows you to display the proof in other screen resolutions so you can see how the website looks on other devices. There are over a dozen different options to choose from.
- Ziflow is hosted securely. To support non-secure sites, hosted over http, we proxy the site through our servers. Sometimes, if a site has full URLs, the site loads that content from the viewer. If a website proof has a lot of full URLs, the information isn't proxied via our servers, but loaded directly instead. When the Proof Viewer is trying to load HTTP content in an HTTPS site, the browser blocks it. There are two ways to 'fix' this problem:
- Change the paths to be relative or absolute, but not full
- Host the site under HTTPS (securely)
- Live website captures that contain a hash sign in the URL are not supported. The reason, is we proxy the site via our servers, and anything behind the # in the URL doesn't reach our backend.