The Mayfield Handbook of Technical and Scientific Writing is what happens when a serious reference book gets poured directly into the web without being turned into a subscription product.
Open the Mayfield Handbook at MIT
Written by Leslie C. Perelman, Edward Barrett and James Paradis, the handbook survives on MIT’s web servers as a large hypertext reference for technical communication. Its table of contents alone is enormous.
The opening sections cover the fundamentals: accuracy, clarity, conciseness, coherence, audience, document purpose, outlining, drafting, revision, review, collaborative writing, ethics and document design.
Then it keeps going.
There are sections for memoranda, meeting documents, literature reviews, laboratory reports, research reports, consulting reports, proposals, manuals, procedures, theses, oral presentations, email, websites, hypertext, résumés and notebooks. Other chapters deal with figures, tables, flowcharts, paragraphs, sentence problems, word choice, punctuation, mechanics and citation styles.
In other words, it is not a blog post titled “17 Tips for Better Technical Writing.” It is an actual handbook.
Hypertext used exactly as intended
The format is especially interesting now because it demonstrates a very straightforward use of the web: take a large reference work and break it into directly linked topics.
Need advice on writing for technicians instead of managers? There is a link. Need a section on overloaded sentences, dangling modifiers, schematic diagrams or research-report structure? There is a link. Need to remember how a technical document’s front matter differs from its body and end matter? Also a link.
Nothing forces the reader through a predetermined path. The table of contents is the interface.
That feels obvious, but modern publishing has spent years trying to make reference material behave like feeds. The Mayfield Handbook does the opposite. It assumes the reader has a problem and wants to get to the relevant page quickly.
It is also a useful artifact of early academic web publishing. Universities put substantial instructional material online because distributing knowledge was part of the point, not because every page needed to be monetized separately.
The design has aged. The information architecture has not.
For students, engineers, developers and anyone who writes documentation, the site remains surprisingly practical. More importantly for web historians, it shows how well plain linked documents can age when the structure is good and nobody decides the whole thing needs to become an app.