A considered layout
Cards and sections follow the content. Long explanations get room; small facts stay compact.
Give your reports, guides, and proposals an editorial finish. Explore the design language, the workflow, and the source specimen.
The purpose is not simply to save a file as PDF. It is to preserve the content, build a readable structure, and deliver an editable source alongside the final document.
The WhatIfIt repository is being prepared. Public installation and downloads are not available yet. Explore the example and local tools in the meantime.

Cards and sections follow the content. Long explanations get room; small facts stay compact.
Use diagrams for relationships and tables for comparison. Keep directions, labels, and data meaningful.
Arabic and English deserve deliberate composition. Keep technical identifiers readable in mixed-language pages.
Executive reports, practical guides, proposals, handbooks, and technical explainers are the intended use cases. Supply approved copy, trusted data, clear audience needs, and any non-negotiable constraints.
Document rendering requires a suitable runtime, file access, a browser-based renderer, and available fonts. A future release will declare its exact dependencies and verified host support. This site does not install or execute the skill.
This is not a PDF signature, redaction, form-filling, or exact-facsimile tool. A well-designed document does not certify the accuracy of its source. Review facts and output separately, and obtain approval before external delivery.
Start with a brief. Leave with a better way to work.