PostgreSQL 18 documentation, §39.3: stored query results, REFRESH MATERIALIZED VIEW and the sales-summary example. Institutional software documentation.
Section 2.5, font-size property and the following note: scalable-font EM scaling, apparent size and ink bounds. Working draft consulted 2026-11-03.
FreeType Glyph Conventions II, sections 1–2: digital points, device resolution, pixels per em and scaling design coordinates.
University of Waterloo mirror of the 1997 Adobe glossary. Entries ascender, descender and x-height are used here; the archived encoding and software descriptions are historical, not current guidance.
PostgreSQL 18, tutorial section 3.2: named query and interface abstraction. CREATE VIEW reference: www.postgresql.org/docs/18/sql-createview.html ; Description and Automatically Updatable Views: nonmaterialized semantics and limits on updates.
FreeType Glyph Conventions III, sections1–3: baseline, logical pen, bearings and advances; section4: grid-fitting changes metrics.
OpenType baseline-tag registry: horizontal versus vertical layout and the romn, hang, math and ideographic baselines.
AAPCS64, sections 5.1 and 5.10.1: fundamental type alignment and aggregate layout. Distinct from the existing AAPCS32 record.
Verified locator: Author-hosted paper: byline Jon M. Kleinberg, existing Jon Kleinberg article reused. §2, hubs/authorities and normalized updates; abstract states eigenvector connection.
Verified locator: Crawling, Indexing and Serving search results; distinguishes discovery, processing and ranking.
Verified locator: Authors: Christopher D. Manning, Prabhakar Raghavan, Hinrich Schütze. Chapter1 opening definition, inverted index; Chapter8 precision/recall. Indexed author-hosted chapter nlp.stanford.edu/IR-book/html/htmledition/boolean-retrieval-1.html verified.
PostgreSQL 18, section 51.5 and 51.5.1: candidate scans, join methods, estimated costs and heuristic search.
GNU Binutils, Using as, §4.1 Background. Official implementation manual: object-file sections, linker address assignment and relocation records; no individual page byline.
Official FAQ: encoded combining characters, diacritic use across languages and the distinction from user-perceived characters.

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 5. . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact