Books, short overviews and speaker cards

Answered 5 October 2026: all three recommendations accepted. These were three choices from the older seven-item additions question. The old card recommended excluding all seven together. Its examples mix complete documents, reusable templates and finished graphics. They need separate answers.

The recorded decisions settle these meanings. They do not change existing records or approve the remaining identity vocabulary.

Question	Recommendation
How should eBooks be found?	Add Book as the whole-piece type, with eBook as a searchable digital edition.
Does One-Pager deserve its own type?	Yes: a concise, standalone overview. Keep its actual page count separately.
Does Speaker Card deserve its own type?	Yes: a designed introduction to a speaker, usually for an event or session.

No further answer is needed for these three choices. Email Header, Blog Header Image, Social Post Graphic and Wallpaper have a separate graphics and intended-use review. They remain unapproved.

1. A book and its digital edition

Already decided: a complete document can be collected with its pages. Selected useful parts can also be browsed independently while retaining their connection to the document. Versions, publications and captures remain distinct.

Recommendation: add Book for a complete publication organized as a book, including a collected volume of essays or interviews. Make eBook a searchable description of its digital edition. The approval covers the broader Book type explicitly; the old additions card alone did not establish that. A report does not become a book just because someone downloads it as a PDF.

Checked example: Opensource.com's An open world offers the same named collection in PDF and EPUB. The inspected PDF cover, contents and introduction present a collected volume of essays and interviews. Under this recommendation, you could find it through Books or eBooks. Its component articles keep their own meaning. Their relationship to separately published articles needs evidence rather than an automatic duplicate merge.

The supplied GitHub guidelines provide the counterexample: their asset folders include eBook Covers. A cover graphic is not the complete book. A link to a book, a screenshot of its cover or a landing page offering it also keeps its own identity.

Alternative: add eBook as its own whole-piece type. That is a familiar browsing name, but we would still need to connect equivalent print and digital editions and avoid treating each file encoding as a new creative work. Leaving both names out would keep the document accessible but give people no defined book-specific entrance.

What your answer affects: collection must distinguish the complete publication from its cover and download page. Classification must inspect the document, not infer its type from a file extension. Queries and trackers must preserve the Book/eBook distinction, while citations identify the actual edition and page inspected. A changed layout may be a useful version; an equivalent encoding alone does not prove a new work. Exact storage and conversion rules remain for the audit.

2. A One-Pager is a concise overview

Already decided: types describe the whole piece. Several types may apply when each genuinely fits. Rich descriptions and defined search choices can coexist.

Recommendation: add One-Pager for a concise, standalone overview intended to communicate the essentials of a subject quickly. It commonly fits on one page or a two-sided sheet. Its actual page count remains a separate, literal fact. The name is not a promise that every captured file contains exactly one page, and a filename alone cannot establish the type.

Checked example: the Kiva and OpenAI ChatGPT Basics handout has “One-Pager” in its filename but contains two PDF pages. Both were inspected. It presents a compact introduction, practical uses and prompting guidance. The recommendation would make it findable as a One-Pager while honestly showing two captured pages. The publisher's wording is supporting context, not sufficient classification evidence by itself.

Counterexample: the first page extracted from an Annual Report is not automatically a One-Pager. Neither is a one-page invoice, a cover or a blank reusable layout. A brief summary that depends on the missing rest of a document is not a standalone overview.

Alternative: keep One-Pager as a searchable presentation description alongside another applicable type, instead of adding a type. That follows the approach already chosen for list-based articles and Q&A presentation. I lean toward a type here because the complete overview is a useful deliverable to find in its own right; you can choose the presentation approach without losing the browse path. A strict one-page-only filter could exist separately under either option.

What your answer affects: extraction must retain all pages, including a reverse side, and distinguish the document from a selected page. Prompts need inclusion and exclusion examples. Search should separate “One-Pager” from “exactly one page.” Product, audience, company and campaign relationships require their own evidence; the document's brevity supplies none of those links.

3. A Speaker Card and the template used to make it

Already decided: Template is on the approved content-type list. The open question is the finished artifact, not whether reusable templates are allowed.

Recommendation: add Speaker Card for a designed graphic introducing a speaker in connection with an event, talk or session. It can combine a name, portrait, role and session information. It can appear on a website, social post or event screen; those appearances do not define a different type each time.

Checked example: page 62 of the supplied GitHub Brand Guidelines 2025 shows its Asset Generator with a Speaker Card option. The visible example combines a portrait, talk title and branding. This is a template preview inside a guideline document, not evidence that a finished card was published. Under the recommendation, a separately collected finished card could have the Speaker Card type. A reusable source would retain its Template meaning, with a derivation relationship only when supported.

Counterexample: a portrait by itself does not establish a speaker card. A photograph showing that graphic on an event screen remains a photograph linked to what it depicts. The guideline page containing the preview remains part of the guideline document.

Alternative: use a broader applicable graphic type and record speaker-introduction purpose as a searchable description. This keeps fewer types, but the purpose needs a definition and consistent search support to preserve this research path. Neither choice turns every graphic into a Key Visual or proves sponsorship from a logo.

What your answer affects: capture must separate the preview, reusable source, finished card and its publications. Analysis must not invent the speaker's identity, employer, maker credit or event membership from appearance alone. Multiple speakers or related sessions must remain possible. Saved collections and cited answers should open the artifact actually collected, with links to related evidence.

What happens next

The evidence note preserves the original question, inspected examples, selected database checks and remaining technical work. The four intended-use additions remain tracked individually in that separate review. The review desk retains every other packet and the later comprehensive schema, pipeline and workflow audit.

Headings, exact storage and existing-record mappings remain to verify. The other four additions are not approved by these answers.

Prepared 5 October 2026.

The review date below records a consistency check against the linked decisions and evidence. It does not change the dates or limits of the source inspections, or certify the complete database and pipeline.

Last reviewed 5 October 2026.