Typography
Stacklists
Sentences and words do not exist by themselves
Sentences and words do not exist by themselves, but have natural, inevitable, unavoidable interactions with their surrounding spaces, words, and other sentences. Sentences are not independent of their spatial context, and interactions can create meanings and harms. Sentences survive content-indifferent and content-hostile spacings, but surviving is not thriving. Text space should not be owned and governed by generic productions grids, which make for convenient production but inconvenient meaning. Space can and should be content-responsive, actively contributing to meaning – forever practices in poetry, maps, math, computer code, comics, theater/movie scrips, posters. Subtle visual spacing differentiates and clarifies sentences, and meaning becomes more consequential, memorable, retrievable.
Central-axis text
Central-axis provides a clear signal of the next line, so that readers and speakers don't have to search on the left margin, sometimes accidentally skipping down a line. Ragged-left typography is used for dialogue in novels and scripts. In central-axis, each line is activated at both left and right margins – unlike squared-off conventional text. Readers/speakers are aware of the length of the next line at both its beginning and end. That knowledge may also help readers detect the pace and rhythm of the words, as in reading poetry aloud.
The pernicious issue with pangrams
The far more pernicious issue with pangrams, as a means for evaluating typefaces, is how poorly they portray what text actually looks like. Every language has a natural distribution of letters, from most to least common, English famously beginning with the
E
that accounts for one eighth of what we read, and ending with theZ
that appears just once every 1,111 letters. Letter frequencies differ by language and by era — theJ
is ten times more popular in Dutch than English; biblical English unduly favors theH
thanks to archaisms like thou and sayeth — but no language behaves the way pangrams do, with their forced distribution of exotics. Seven of the most visually awkward letters, theW
,Y
,V
,K
,X
,J
, andZ
, are among the nine rarest in English, but pangrams force them into every sentence, guaranteeing that every paragraph will be riddled with holes. A typeface designer certainly can’t avoid accounting for these unruly characters, but there’s no reason that they should be disproportionately represented when evaluating how a typeface will perform.To abandon control
In print the designer is god. An enormous industry has emerged from WYSIWYG, and many of the web’s designers are grounded in the beliefs and practices, the ritual of that medium. As designers we need to rethink this role, to abandon control, and seek a new relationship with the page.
The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn’t have the same constraints, and design for this flexibility. But first, we must “accept the ebb and flow of things.”
Typographic grid
Just one of many examples of beautiful typography and layout throughout the book. Love the page design.
A state of energetic repose
Read the text before designing it.
Discover the outer logic of the typography in the inner logic of the text.
Make the visible relationship between the text and other elements (photographs, captions, tables, diagrams, notes) a reflection of their real relationship.
Give full typographic attention even to incidental details.
Invite the reader into the text.
Reveal the tenor and meaning of the text.
Clarify the structure and the order of the text.
Link the text with other existing elements.Induce a state of energetic repose, which is the ideal condition for reading.
Simple forms
The concept that “the simpler the form of a letter the simpler its reading” was an obsession of beginning constructivism. It became something like a dogma, and is still followed by “modernistic” typographers.
This notion has proved to be wrong, because in reading we do not read letters but words, words as a whole, as a “word picture.” Ophthalmology has disclosed that the more the letters are differentiated from each other, the easier is the reading.
Without going into comparisons and the details, it should be realized that words consisting of only capital letters present the most difficult reading—because of their equal height, equal volume, and, with most, their equal width. When comparing serif letters with sans-serif, the latter provide an uneasy reading. The fashionable preference for sans-serif in text shows neither historical nor practical competence.
Typography exists to honor content
In a world rife with unsolicited messages, typography must often draw attention to itself before it will be read. Yet in order to be read, it must relinquish the attention it has drawn. Typography with anything to say therefore aspired to a kind of statuesque transparency. Its other traditional goal is durability: not immunity to change, but a clear superiority to fashion. Typography at its best is a visual form of language linking timelessness and time.
The higher courts
Refer typographic disputes to the higher courts of speech and thinking.
Type is idealized writing, and its normal function is to record idealized speech. Acronyms such as CD and TV or USA and UFO are set in caps because that is the way we pronounce them. Acronyms such as UNESCO, ASCII, and FORTRAN, which are pronounced not as letters but as words, are in the process of becoming precisely that. When a writer accepts them fully into her speech and urges readers to do likewise, it is time for the typographer to accept them into the common speech of typography by setting them in lower case. Other acronymic words, such as laser and radar, have long since traveled the same road.
Pure but silent
Architects build perfectly proportioned kitchens, living rooms and bedrooms in which their clients will make, among other things, a mess. Typographers likewise build perfectly proportioned pages, then distort them on demand. The text takes precedence over the purity of the design, and the typographic texture of the text takes precedence over the absolute proportions of the pure but silent page.
An end in itself
Typography, like language, is more important to me for what it allows to happen than for anything it accomplishes on its own. I hope that in writing a book on the subject I have not given the impression that either typography or design is an end in itself.
Respect
Respect the text first of all, the letterforms second, the type designer third, the foundry fourth.
The needs of the text should take precedence over the layout of the font, the integrity of the letterforms over the ego of the designer, the artistic sensibility of the designer over the foundry’s desire for profit, and the founder’s craft over a good deal else.
A gradual refinement
The steel rail is an artifact whose form has been carefully optimized. This gradual refinement of the design was done not by a single brilliant engineer but by more than a century of industrial evolution. The rail was never meant to be an object of beauty, but its cross section has all the elegance of fine typography.
The Elements of Typographic Style
A Book by Robert BringhurstTo Make a Book, Walk on a Book
An Essay by Craig ModThe ability of the physical world — a floor, a wall — to act as a screen of near infinite resolution becomes more powerful the more time we spend heads-down in our handheld computers, screens the size of palms. In fact, it’s almost impossible to see the visual patterns — the inherent adjacencies — of a physical book unless you deconstruct it and splay it out on the floor.
Web Design is 95% Typography
An Article by Oliver Reichenstein95% of the information on the web is written language. It is only logical to say that a web designer should get good training in the main discipline of shaping written information, in other words: Typography.
What of the lowly page number
An Article by Marlon J. EttingerStatement of intent, chronological guidepost, or cheap trick to inflate the length of a text, page number placement is anything but an afterthought. Behind these innocuous and overlooked symbols, I found many stories to be told.
Care for the Text
An Article by Robin RendleWhenever I’m stuck pondering the question: "How do I make this website better?" I know the answer is always this: Care for the text.
Without great writing, a website is harder to read, extremely difficult to navigate, and impossible to remember. Without great writing, it’s hardly a website at all. But it’s tough to remember this day in and day out—especially when it’s not our job to care about the text—yet each and every <p> tag and <button> element is an opportunity for great writing. It’s a moment to inject some humor or add a considerate note that helps people.
…These are the details that make a good website great.
In search of visual texture
An Article by Rachel PruddenI’m now more inclined to attribute Looseleaf’s power to its visual texture than to some cognitive media-style abstraction. And the visual texture owes more to the beauty (yes, beauty!) of the original pdfs from the Vasulka Archive. Perhaps the demo is best understood not as a prototype generic tool, but as a specific curated experience in its own right, with form and content claiming equal importance in its overall success.
Even so, I think there are some general lessons that can be drawn from this demo:
- Content is not inert
- Visual texture lets content breathe
- Visual texture lets the eye wander without losing itself
Chartwell
A FontThis set of tools for easily creating graphs is conveniently disguised as a set of fonts. OpenType features are used to interpret and visualize the data. The data remains as editable text, allowing for painless updates.
Whomst styles?
An Article by Robin SloanThis is a “whostyle”: an attempt to carry the ~timbre~ of an author’s voice, in the form of their design sensibility, through into a quotation. It’s the author who defines their whostyle; the quoting site just honors it, a frame around their words.
I think the whostyle makes a few arguments. Among them:
- Text is more than a string of character codes. Its design matters, typography and layout alike; these things support (or subvert!) its affect, argument, and more.
- The web should be more colorful and chaotic, along nearly every dimension. The past five years have brought a flood of new capabilities, hugely expressive — let’s use them!
- Quoting is touchy, and anything you can do to cushion it with respect and hospitality is a plus.
Unicode Arrows
A Fragment by Rachel Binx↬ welcome to the best part of the unicode spec ↫
APL386 Unicode
A Font by Adám BrudzewskyAPL font based on Adrian Smith's APL385 font with a fun, whimsical look, inspired by Comic Sans Serif.
APL (named after the book A Programming Language) is a programming language developed in the 1960s by Kenneth E. Iverson. Its central datatype is the multidimensional array. It uses a large range of special graphic symbols to represent most functions and operators, leading to very concise code. It has been an important influence on the development of concept modeling, spreadsheets, functional programming, and computer math packages. It has also inspired several other programming languages.
The Design of Design
What's Wrong With This Model?
A ChapterDesign process models: A summary argument
- A formal design process model is needed, to help organize design work, to aid communication in and about projects, and for teaching.
- Having a visual, geometric representation of a design process model is crucial, for designers are spatial thinkers. They will most easily learn, think about, share, and talk in terms of a model with a clear geometric picture.
- The Rational Model of design occurs naturally to engineers.
- The linear, step-by-step Rational Model is highly misleading. It does not reflect what real designers do, or what the best design thinkers identify as the essence of the design process.
- The bad model matters. It has led to the too-early binding of requirements, leading in turn to bloated products and schedule/budget/performance disasters.
- The Rational Model has persisted in practice despite its inadequacies and plenty of cogent critiques. This is because of its seductive logical simplicity, and because builders and clients needs “contracts."
- Several alternative models have been proposed. I find Boehm’s Spiral Model the most promising. We need to keep developing it.
The spiral model
The spiral shape certainly suggests progress. It associates successive repetitions of the same activity. The geometric shape is easily understood and memorable. The model emphasizes prototyping, starting with user-interface prototypes and user testing long before an operational prototype is possible.
Since a development model is principally used by developers, I believe having it designer-centered is entirely appropriate. With Boehm and against Denning and Dragon, I advocate frequent but not continuous interaction with representative users, with successive prototypes as the vehicles.
I strongly believe that way forward is to embrace and develop the Spiral Model.
A grossly obese set of requirements
Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun.
The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing.
Requirements proliferation
Any attempt to formulate all possible requirements at the start of a project will fail and would cause considerable delays. — Pahl and Beitz, Engineering Design
As Project Manager, I had to reject the requirements document as totally impractical, and have a quite small team of architects, marketers, and implementers extract the essence.
Requirements proliferation must be fought, by both birth control and infanticide.
The architectural contracting model
It is the necessity for contracts, whether within an organization or between organizations, that forces the too-early binding of goals, requirements, constraints. The pressure for a complete and agreed-upon set of requirements run into the hard fact, that it is essentially impossible to specify any complete and accurate set of requirements for any complex system except in iterative interaction with the design process.
How have the centuries-old building design disciplines handled this perplexity? Fundamentally, by a quite different contracting model.
- The client develops a program, not a specification, for the building.
- He contracts with an architect, usually on an hourly or percentage basis, for services, not for a specified product.
- The architect elicits from the client, the users, and other stakeholders a more complete program, which does not pretend to be a rigid contractable product specification.
- The architect does a conceptual design that approximates the reconciliation of program and the constraints of budget, schedule, and code. This serves as a first prototype, to be conceptually tested by the stakeholders.
- After iteration, the architect performs design development, often producing more detailed drawings, a 3-D scale model, mockups, and so on. After stakeholder iteration, the architect produces construction drawings and specifications.
- The client uses these drawings and specifications to enter into a fixed-price contract for the product.
Notice how this long-evolved model separates the contract for design from the contract for construction. Even when both are performed by the same organization, this separation clarifies many things.
The rational model of design
Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it.
The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community.
Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI.
In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design.
Design process models
Any systematization of the design process is a great step forward compared to "Let's just start coding, or building." It:
- Provides clear steps for planning a design project
- Furnishes clearly definable milestones
- Suggests project organization and staffing
- Helps communication within the design team
- Is readily teachable to novices, and tells novices facing their first design assignments where to begin.
The Rational Model in particular brings yet more advantages. The early explicit statement of goals, secondary desiderata, and constraints helps a team avoid wandering, and it breeds team unification on purposes. Planning the whole design process before starting coding or formal drawings avoids many troubles and much wasted effort. Casting the process as a systematic search of a design space broadens the horizon of the individual designers and lifts their eyes far beyond their previous personal experiences.
But the rational model is much too simplistic, even in Simon's richly developed version.
The dual ladder
The first task for growing designers, as opposed to managers, is to craft a proper career path for them, one whose compensation and sociological status reflect their true value to the creative enterprise. This is commonly called the dual ladder. It it easy to give corresponding salaries to corresponding rungs, but it requires strong proactive measures to give them equal prestige: equal offices, equal staff support, reverse-biased raises when duties change.
Why does the dual ladder need special attention? Perhaps because managers, being human, are inherently inclined to consider their own tasks more difficult and important than design and need to deliberately assess what makes creativity and innovation happen.
A platonic ideal
As the architecture design progressed, I observed what at first seemed quite strange. For the architecture team, the real System/360 was the Design Concept itself, a Platonic ideal computer. Those physical and electrical Model 50, Model 60, Model 70, and Model 90 things under construction out on the engineering floors were but Plato’s shadows of the real System/360. The real System/360’s most complete and faithful embodiment was not in silicon, copper, and steel, but in the prose and diagrams of IBM System/360 Principles of Operation, the programmer’s machine language manual.
I had a similar experience with the View/360 beach house. Its Design Concept came to be real long before any construction began. It persisted through many versions of drawings and cardboard models.
The design concept
Is there positive value to recognizing an invisible Design Concept as a real entity in design conversations? I think so.
First, great designs have conceptual integrity—unity, economy, clarity. They not only work, they delight, as Vitruvius first articulated. We use terms such as elegant, clean, beautiful to talk about bridges, sonatas, circuits, bicycles, computers, and iPhones. Recognizing the Design Concept as an entity helps us to seek its integrity in our own solo designs, to work together for it in team designs, and to teach it to our youth.
Second, talking frequently about the Design Concept as such vastly aids communication within a design team. Unity of concept is the goal; it is achieved only by much conversation.
Thus, moviemakers use storyboards to keep their design conversations focused on the Design Concept, rather than on implementation details.
The Idea
The design is thus the mental formulation, which Sayers calls “the Idea,” and it can be complete before any realization is begun. Mozart’s response to his father’s inquiry about an opera due to the duke in three weeks both stuns us and clarifies the concept.
For most human makers of things, the incompletenesses and inconsistencies of our ideas become clear only during implementation. Thus it is that writing, experimentation, “working out,” are essential disciplines for the theoretician.
The boldest decisions
In retrospect, many of the case studies have a striking common attribute: the boldest design decisions, whoever made them, have accounted for a high fraction of the goodness of the outcome. These bold decisions were made due sometimes to vision, sometimes to desperation. They were always gambles, requiring extra investment in hopes of getting a much better result.
Intuition and systems
Systematic design excluding intuition yields pedestrian follow-ons and knock-offs; intuitive design without system yields flawed fancies. How to weld intuition and systematic approach? How to grow as a designer? How to function in a design team?