The original idea behind the creation of the Newton Glossary was to provide a single, accessible resource for terminology related specifically to the Newton.
A significant number of the terms found in the glossary were initially compiled between 2001 and 2004 by Grant Hutchinson. Numerous sources were used, along with help from knowledgable folks such as Paul Guyot, Victor Rehorst, and countless members of the NewtonTalk community.
Although it’s quite out of date, Morgan Aldridge has maintained a searchable version of the glossary as part of the United Network of Newton Archives.
At one point there was also a Newton Book version of the glossary. We’ll see if we can make that happen again.
Join The Fun!
As with any specialized compendium, the contents are never completely finished. All suggestions, corrections, complaints, and pull requests will be happily accepted. If possible, please use the project’s issue tracker for any input you might have.
Before submitting new terms or suggestion corrections to existing entries, please take a moment to familiarize yourself with the official style guide (which itself is a work in progress).
We ♥ Words
Other glossarial references we love.
- A Devil’s Dictionary of Educational Technology by Bryan Alexander
- Apple Style Guide by Apple
- Dictionary of Canadianisms on Historical Principles by Stefan Dollinger
- Free Online Dictionary of Computing by Denis Howe
- Green’s Dictionary of Slang by Jonathon Green
- Glossary of Archival & Records Terminology by Richard Pearce-Moses
- Glossary of Common Type Terminology by FontShop
- Glossary of Eye Terminology by Barbara Cassin
- Jargon File by Eric S. Raymond
- Neoglossary by Riccardo Mori
- Rands Management Glossary by Michael Lopp
- Typograph.Glossary by Nicole Arnett Phillips
This iteration of the glossary is formatted in Markdown using plain text files and published using Kirby — an extensible content management system built on PHP.
We run our stylesheets through CSSLint because tidy code is better code … and we don’t mind getting our feelings hurt.
The entire project resides in a public GitHub repository, providing easy access for contributors, relatively pain-free upkeep, and peace of mind.
To add a bit of spit and polish to our Kirby experience, we use the following handy dandy plugins.
- Alphabetise by Russ Baldwin
- Cachebuster by Bastian Allgeier
- Kirby GA by Jens Törnell
- Kirby Meta Tags by Pedro Borges
- Kirby Paperback Export by Grant Hutchinson
- Kirby XML Sitemap by Pedro Borges
And finally, god bless BBEdit.