Elysia Tools
Navigation
Workflow Playbook
Turn one authorized procedure into a tested screenshot guide, verify image-to-step matching and privacy, and deliver reviewed HTML, print-to-PDF output and an editable project.
Hubs
This workflow is for support, training and product teams handing off one repeatable procedure. Name the application version, user role, permissions, starting state and completion evidence. A list formatter organizes supplied lines; it does not discover missing actions. Keep each instruction focused on one action and a visible result. Maintain warnings and a separate test checklist rather than accidentally importing every numbered subitem as a new step.
Use numbered instructions or blank-separated blocks that the builder can parse, then inspect the result. Bodies are plain text, not a promise of full Markdown rendering. Preserve a readable source draft and reference list outside the project. This is a playbook, not a connected automation that performs the task.
Use synthetic accounts and approved data. Website Screenshot is useful for a public page, not automatic login, clicking or full journey recording. Private states need an authorized external capture method. Other preparation tools may upload images for processing even though the guide builder keeps screenshots in the browser; do not send sensitive images to those tools.
Check actual dimensions and legibility. Crop only when the location remains understandable, retaining restricted originals separately. In the builder use a destructive mask for visible secrets, not a highlight, blur claim or removable annotation. The mask overwrites pixels and is not undone by removing annotations. It does not sanitize instruction text, filenames, prior backups or external originals. Inspect every file intended for sharing.
The builder supports up to 30 steps and PNG/JPEG/WebP images up to 10 MB each, within a 20 MB processed-image budget. Large images can be reduced; zoom the output to verify small labels. Batch import fills empty image slots in order, then adds steps: it is positional, not AI recognition. Confirm each pair after import or reordering and keep annotations clear of critical labels.
Save the editable project JSON before closing, rerunning or opening another result window. There is no autosave. Reopen the downloaded project to check actual restoration. Masking is irreversible in the working image; keep only authorized restricted recovery copies outside the shareable project.
Ask a second person to start from the documented state using an authorized test environment. Record where they hesitate, which screenshot differs and whether the expected result appears. Missing permissions, validation errors or a changed menu must lead to revised instructions and a retest, not an unexplained screenshot substitution.
Use Text Diff to inspect wording changes, but a line diff does not prove operational correctness. Markdown Link Checker can statically examine the companion reference list; it makes no network requests and does not certify the exported HTML or PDF. Check destinations and final links separately. Record deviations, pending cases and the reviewer decision.
Download standalone HTML and inspect it offline. Produce the PDF using the browser print dialog, choose Save as PDF and check page size, scaling and unwanted headers/footers. Long screenshots are tiled for printing, so inspect every fragment and page break, annotation readability and step order. A preview is not acceptance of the saved PDF.
Deliver versioned HTML, the actual reviewed PDF, editable project and source/checklist/review record as agreed. Save files locally rather than relying on temporary results. Calculate SHA-256 after final privacy review; hashes identify files, not instructional correctness. Use related workflows for broader documentation publishing, multilingual technical-document adaptation or full accessibility review. This procedure ends at a tested task guide, not certification of every application state.
Workflow playbook
Use a numbered list to organize actions and maintain a separate acceptance checklist. Inspect numbering before import; the list formatter does not infer actions or correct a procedure.
Capture public pages where appropriate, check real image dimensions and crop only for clarity. Use approved local capture for private or interactive states.
Import instructions and screenshots, manually verify positional pairing, annotate actions and apply irreversible pixel masks where needed. Save a project backup before leaving.
Compare previous and revised text, statically check a companion Markdown reference list and have another person execute the task. Verify external destinations and final outputs separately.
Website Screenshot can provide authorized public-page evidence, not a recorded user journey. Capture login, menus and sensitive states separately using an approved method; do not place credentials in URLs.
Keep enough surrounding UI to identify the action. Cropping is not secure redaction; use the builder's destructive pixel mask for visible secrets and verify all exported files and text.
Standalone HTML and a browser-produced PDF are reading artifacts. Download the project JSON for later editing and verify reopening; a PDF alone is not a reusable project.
Reopen the editable project, inspect downloaded standalone HTML and the actual print-to-PDF file, then hash the final local files with SHA-256.