Hosted interactive publications A Partner in Publishing product
Send us the file you already have. We host it as a publication people read: pages that turn, every word searchable, print resolution under zoom, links that still work, and a record of how far each reader got.
Live Electrical Systems Based on the 2026 NEC, published for ATP Learning.
Plate 01The viewer
The book behaves like a book: a cover, then spreads, turning under the reader's hand. It answers like a web page: addressable, searchable, linkable, embeddable. Nothing asks the reader to download a file first.
Cover first, then spreads
Pages turn the way print turns. Wide screens get two-page spreads, phones get single pages.
Every page has its own link
A link ending in #page/12 opens the book already on page
twelve, so you can point a customer at one figure.
Re-rendered at print resolution
Zooming redraws the page rather than magnifying a picture of it, so small type in specs and tables stays sharp.
Full text, jump to the page
Every word in the document is searchable, and each result takes the reader straight to the page it sits on.
Hyperlinks stay live and get counted
Web links, buttons, and email addresses built into the PDF keep working, and every click is recorded.
Slide-out table of contents
A contents panel plus a thumbnail strip along the bottom, for readers who skim before they read.
Light or dark, the reader's choice
The viewer follows whatever the reader's device is already set to, and stays legible in both.
One script tag
Drop the book into a page you already have, or send the link on its own. Both are the same publication.
Plate 02The benchPre-publication checks
A viewer is easy. A viewer that never loses a figure is the actual work. Below is what runs on every title we publish, what happens on the titles where nobody runs it, and what we do instead. This is the part a reader never sees and always feels.
The convenient compression presets flatten transparency and silently delete any image carrying a soft mask (the layer that tells a page which parts of a picture show through). The page publishes with a blank rectangle where the figure was, and nothing anywhere reports it.
We compress with explicit settings that keep those images, and we never trust a preset to decide. The file gets smaller. The artwork stays.
One dropped figure deep in a long book is invisible until a reader finds it, and by then it is your name on the cover, not our process, taking the hit.
Once the book is built, it is compared page by page with the file you sent. A missing figure or a dropped photograph is caught here, by us, and not three weeks later by a reader who assumed the book was broken and closed it.
Links vanish in conversion without a single error message. A chapter quietly stops sending anyone anywhere, and the numbers read as disinterest rather than breakage.
We count the live links in the source PDF and confirm the finished book carries the same number. If one went missing in processing, the count says so before anybody clicks it.
Covers, contents spreads, and calls to action sometimes set their visible text in an unusual embedded font format that web viewers quietly refuse to draw. The words are simply not there when the page renders.
Those specific pages get flattened to images, so the words you designed are the words on screen. The rest of the book stays live text, searchable and sharp.
A handful of transparency heavy pages come out wrong on one engine and right on the other. Betting the whole book on a single engine means accepting a few broken pages and hoping nobody lands on them.
The viewer carries both and decides page by page, so the four pages that need the second engine get it and the other three hundred are untouched.
A large file that has to arrive in full before anything appears reads as broken. Readers leave during the wait, and the ones on a phone leave first.
Page one paints while the rest of the file is still arriving. Nobody sits watching a progress bar to find out whether the thing was worth opening.
Hosted viewers fall apart at the edges: a blank screen while loading, nothing sensible when a search finds no matches, a dead end when something fails.
Loading, empty, and error states are drawn on purpose rather than left to the browser. Motion backs off for a reader who has asked their system to reduce it. Keyboard focus is visible. Touch targets are large enough to hit on a train.
Seven checks, every title, no exceptions Nothing publishes on a maybe
Plate 03The askOn every page
Send a PDF and the conversation ends at the download. The reader is alone with a file, and whatever you wanted to ask them is in an email they have already scrolled past.
A publication keeps the ask in the frame. That button is pinned to the book, so it is there on page three and still there on page forty, and the closing spread makes the ask outright. Each title can point at its own form, so a request arrives with the title already attached.
Plate 04Getting publishedThree steps
No web version to commission, no reformatting request coming back at you, no new platform for your team to learn. The print file you already have is the input.
Step 01
Any print-ready PDF: a catalog, a sample chapter, a report, a lookbook. Print layout is fine. Crop marks are fine. We do not need a web version.
Step 02
We compress it without losing artwork, brand it to match you, wire the links and the contents, and verify every page against your original.
Step 03
It goes live under your own name, ready to send, to deep-link straight to a page, or to embed in a page you already run.
Plate 05In productionLive now
Electrical Systems Based on the 2026 NEC, published for ATP Learning. Spec tables, wiring figures, and code references, all of it searchable, all of it sharp at full zoom, all of it counted. Open it on your phone if you want the honest test.