Add Knowledge files to main fonts repo

knowledge/README.md

@@ -0,0 +1,3 @@
+# Knowledge
+
+Watch this space.

knowledge/contributors.textproto

@@ -0,0 +1,116 @@
+contributors {
+  name: "Bram Stein"
+  personal_site: "https://www.bramstein.com"
+}
+contributors {
+  name: "Bruce Willen"
+  personal_site: "https://publicmechanics.com"
+}
+contributors {
+  name: "David Brezina"
+  personal_site: "https://rosettatype.com"
+}
+contributors {
+  name: "Doug Wilson"
+  personal_site: "https://realdougwilson.com"
+}
+contributors {
+  name: "Ellen Lupton"
+  personal_site: "https://ellenlupton.com"
+}
+contributors {
+  name: "Elliot Jay Stocks"
+  personal_site: "https://elliotjaystocks.com"
+}
+contributors {
+  name: "Erik Spiekermann"
+  personal_site: "https://spiekileaks.com"
+}
+contributors {
+  name: "Frank Rausch"
+  personal_site: "https://frankrausch.com"
+}
+contributors {
+  name: "Gerry Leonidas"
+  personal_site: "https://leonidas.net"
+}
+contributors {
+  name: "Jamie Clarke"
+  personal_site: "https://www.jamieclarketype.com"
+}
+contributors {
+  name: "Jason Pamental"
+  personal_site: "https://rwt.io"
+}
+contributors {
+  name: "Jason Santa Maria"
+  personal_site: "https://jasonsantamaria.com"
+}
+contributors {
+  name: "Jessica Hische"
+  personal_site: "https://jessicahische.is"
+}
+contributors {
+  name: "John Boardley"
+  personal_site: "https://ilovetypography.com/about"
+}
+contributors {
+  name: "Laurence Penney"
+  personal_site: "https://lorp.org"
+}
+contributors {
+  name: "Mark Boulton"
+  personal_site: "https://markboulton.co.uk"
+}
+contributors {
+  name: "Matthew Smith"
+  personal_site: "https://matthewsmith.website"
+}
+contributors {
+  name: "Micah Rich"
+  personal_site: "https://micahrich.com"
+}
+contributors {
+  name: "Mike Kus"
+  personal_site: "https://www.mikekus.com/"
+}
+contributors {
+  name: "Rosalie Wagner"
+  personal_site: "http://rosaliewagner.com"
+}
+contributors {
+  name: "Santiago Orozco"
+  personal_site: "http://typemade.com"
+}
+contributors {
+  name: "Richard Rutter"
+  personal_site: "http://clagnut.com"
+}
+contributors {
+  name: "Sam Berlow"
+  personal_site: "https://twitter.com/sberlow"
+}
+contributors {
+  name: "Thomas Jockin"
+  personal_site: "http://thomasjockin.com"
+}
+contributors {
+  name: "Thomas Phinney"
+  personal_site: "https://twitter.com/thomasphinney"
+}
+contributors {
+  name: "Trent Walton"
+  personal_site: "https://trentwalton.com"
+}
+contributors {
+  name: "Tyler Finck"
+  personal_site: "https://www.tylerfinck.com"
+}
+contributors {
+  name: "Yves Peters"
+  personal_site: "https://twitter.com/baldcondensed"
+}
+contributors {
+  name: "Viviana Monsalve"
+  personal_site: "https://www.instagram.com/_vv_monsalve_"
+}

knowledge/glossary/terms/alignment_justification/content.md

@@ -0,0 +1,20 @@
+
+In paragraphs of (western) [text](/glossary/text_copy), alignment refers to the invisible vertical line(s) implied by a block of [type](/glossary/type), which aids readability. When type is left-aligned, each new line begins from the same point on the X axis.
+
+<figure>
+
+![Three blocks of text, each with different alignment: The first is left-aligned, the second center-aligned, and the third right-aligned. Each block has a line showing where the alignment resides.](images/thumbnail.svg)
+
+</figure>
+
+If the text is right-aligned, the invisible vertical line sits to the right-hand side of the paragraph; if the text is center-aligned, the line sits in the center of the paragraph. It’s possible to have the text aligned to both left *and* right; this is known as justified text.
+
+<figure>
+
+![A justified block of text, with lines showing how the text aligns to both left and right sides. The last line, consisting of just one word, is an orphan and is highlighted.](images/Alignment_justification_2.svg)
+
+</figure>
+
+Because justification adds space between words, it often creates unsightly gaps and rivers in the text. This can be avoided with the liberal use of [hyphenation](/glossary/hyphenation) to avoid word spaces that are too wide or too long.
+
+Justified text can appear neater because of its uniform alignment. However, the last line of a paragraph in justified text will not be justified; this makes the occurrence of [orphans](/glossary/widows_orphans) more problematic, since they interrupt this perceived neatness.

knowledge/glossary/terms/alignment_justification/term.textproto

@@ -0,0 +1,5 @@
+name: "Alignment & justification"
+excerpt: "In paragraphs of (western) text, alignment refers to the invisible vertical line implied by a block of type. Justified text is aligned to both left and right margins."
+related_lessons: "working_with_hanging_punctuation"
+related_lessons: "understanding_measure_line_length"
+related_lessons: "avoiding_widows_orphans"

knowledge/glossary/terms/all_caps/content.md

@@ -0,0 +1,11 @@
+
+When [text](/glossary/text_copy) is set in only [uppercase](/glossary/uppercase_lowercase) letters, it’s commonly abbreviated as all-caps. All-caps text can be hard to read unless that text is very short, so it’s best to keep it brief, such as for titles or emphasis. Don’t use it for [body](/glossary/body) text. At any but the larger sizes, we often add additional [tracking/letter-spacing](/glossary/tracking_letter_spacing) to all-caps type that’s longer than two or three characters—this helps improve overall readability.
+
+<figure>
+
+![The phrase “QUIET is the new LOUD”. The all-caps word “QUIET" set in large type requires no tracking. The all-caps word “LOUD"—set much smaller—has additional tracking to aid readability. Lines highlight this setting.](images/thumbnail.svg)
+<figcaption>The all-caps word “QUIET" set in large type requires no tracking. The all-caps word “LOUD"—set much smaller—has additional tracking to aid readability.</figcaption>
+
+</figure>
+
+If you have to use uppercase text within body text, consider using [small caps](/glossary/small_caps). Small caps are designed to feel more at home with the rest of the lowercase type and won't “shout” so much at the reader.

knowledge/glossary/terms/all_caps/term.textproto

@@ -0,0 +1,4 @@
+name: "All-caps"
+excerpt: "Text set entirely in uppercase letters."
+related_lessons: "introducing_alternate_glyphs"
+related_lessons: "choosing_reliable_typefaces"

knowledge/glossary/terms/alternates/content.md

@@ -0,0 +1,15 @@
+
+Alternates (also known as alternate [characters](/glossary/character) or alternate [glyphs](/glossary/glyph)) are substitute letterforms that supplement the default character set.
+
+They usually serve one of two purposes:
+
+1. To add variety to repeated characters (for example, you might use multiple alternate glyphs in text that’s meant to appear hand-lettered, or hand-distressed).
+2. To account for the end user’s preference for different characteristics, such as the more unusual z and g glyphs in [Yanone Kaffeesatz](https://fonts.google.com/specimen/Yanone+Kaffeesatz).
+
+<figure>
+
+![The phrase “ziggy, meet ziggy” set in a sans serif typeface that has alternate glyphs enabled for the z and g characters in the second version of “ziggy.”](images/thumbnail.svg)
+
+</figure>
+
+Accessing alternates can be achieved via [OpenType](/glossary/open_type) either on a per-glyph level or by applying a [stylistic set](/glossary/stylistic_sets) to an entire piece of text. Contextual alternates, if enabled, can intelligently appear according to which glyphs they sit next to.