The first change was smaller than the idea it eventually supported.
I stopped sending the manuscript as an attachment and put the reading experience behind a link.
That sentence makes the decision sound obvious. It was not. A link could open a landing page, a document, a comment-heavy workspace, or a place that asked the reader to learn a new system before seeing the book. I was not trying to make an internet version of a file. I was trying to give a reader and me one place to look at the same words.
I was still working with an unfinished manuscript and a few people whose responses could change it. The practical problem was familiar: a reader would have a copy, I would have another copy, and a useful thought would have to cross the gap between them. The first solution was to change the starting point instead of improving the instructions around the attachment.
The attachment was the wrong starting point
With a file, the reader received an object. With a link, the reader could open a place.
That difference was more useful than it sounds. I could send the link, open it myself, and look at the same passage the reader was seeing. If the text changed, I could update the reading surface without creating another attachment for every small revision. A reader did not need to decide which copy to download or keep open before beginning.
The link did not make the manuscript finished. It made the reference less fragile. Instead of explaining a location through a chapter label or a copied sentence, I could ask the reader to return to the page where the words were already present. The passage did not have to travel inside every response.
I noticed a small change in my own work. I spent less time translating messages back into the manuscript and more time asking what the reader had seen. That was not because the page had solved revision. It had removed one piece of clerical work that had been standing between a note and the sentence it meant.
The first useful property of the web page was not speed or novelty. It was sameness. The reader and I could start from the same text without passing a new copy back and forth.
One detail mattered more than I expected: the reader could leave and return without asking me which file was current. The link did not guarantee that every return would feel identical; the manuscript was still in motion. But it gave the reader a stable invitation rather than a sequence of attachments. I could say, in effect, start here, and the words would be waiting there. That was a different kind of handoff—less like sending a package, more like leaving a door open while the room was being arranged.
That distinction helped me see why the page felt more like a solution than a workaround. It was not just reducing clicks. It was changing what counted as the unit of exchange.
A link is not yet a reading experience
The first page was easy to make look functional. A title, a column of text, and a way to move through the manuscript were enough to prove that a browser could display it. They weren’t enough to make someone want to stay.
I kept coming back to the difference between opening a document and entering a book. A document can be useful even when it announces all of its controls. A book asks for a little more quiet. The reader should be able to follow an argument without feeling that every sentence is waiting to be inspected, marked, or discussed.
That constraint changed how I thought about the first reader. I did not want a collaborative document with a book placed inside it. I wanted the text to remain the main thing on the page, while still leaving a clear route back to a conversation when a reader had something to say.
This was a modest target. I wasn’t trying to design for every kind of reading behavior. I wanted to find out whether a shared page could hold the ordinary sequence: open the text, read for a while, notice something, and make it possible for another person to see what prompted the response.
The shared page changed my job
An attachment made me responsible for moving copies. The page made me responsible for keeping one reading place understandable.
That did not mean the text stopped changing. It meant the change had a home. When I revised a paragraph, the next conversation could begin from the same reading surface rather than from a new file whose relationship to the old one had to be explained. The reader could come back to the manuscript without treating each visit as a fresh handoff.
The effect was especially clear in small exchanges. A reader could point to a passage, and I could open it before replying. If the surrounding paragraph mattered, it was there. If the wording had changed, we had a visible reason to ask which version the response belonged to. The page did not answer every question, but it gave the questions somewhere to start.
I also stopped thinking of the link as a delivery shortcut. It was becoming a shared reading surface: a place where more than one person could open the text without each person having to reconstruct the conditions of the conversation.
That was the first concrete answer to the problem I had been circling. The reader did not need another way to carry a file. The reader needed a common place where the book could remain visible while the work around it continued.
The first solution created a new tension
The page solved one kind of distance and exposed another problem. Once I had a shared surface, it was tempting to put every useful action directly beside the text.
Notes, comments, revision cues, and response controls all had an obvious reason to be nearby. But each addition made the page more like a review workspace. A reader could still read, yet the page began to suggest that reading was mainly a search for things to mark.
I noticed this in the simple moments. When the text was quiet, a reader could follow the chapter as a chapter. When the page made every possible response visible, the reader had to keep deciding whether to continue reading or stop and work on the manuscript. The shared surface helped the conversation, but it could also let the conversation take over.
The answer was not to remove the connection between text and response. That connection was why we built the page. The question was how to keep the reading experience from becoming a permanent review meeting.
I had expected the first web reader to remove friction. It did, but it also created a new tradeoff that was impossible to ignore: the same place had to be clear enough for a response and calm enough for reading.
What the web page actually solved
The web page was not a perfect book, and it was not a theory of what books should become. It was a small practical correction.
It gave the reader and the writer a shared starting point. It made a passage easier to find without turning every message into a location report. It let the manuscript remain changeable without making every change another detached object. Most importantly, it kept the text in the conversation instead of asking people to carry it back into the conversation.
I was still learning what belonged on the page and what belonged around it. The first reader answered the narrow question I could ask: could a web page make reading and responding feel like related acts? The answer was yes, but only if the page still behaved like a place for reading.
That shared reading surface eventually made something else possible. ReaderPub can now measure reading progress and interest for individual books, giving authors and publishers signals they can use when planning what to do next to promote a book.
That was enough to move the work forward. A manuscript could prove a link was useful, but it couldn’t tell me whether the page worked as a book. I needed a real book to find out.