posts_unified

This table merges gdocs and wordpress posts. Use this one over either the posts or posts_gdocs table if you want to query for content. This table adds several very useful convenience features: In our publishing pipeline, GDocs posts take precedence over wordpress posts with the same slug. This table likewise shows only the published gdocs post result row and hides the wordpress post row with the same slug if there is one. The Gdocs posts have a type column. This table also retrofits this type to wordpress posts. The type is one of: topic-page - modular topic pages with key insights etc article - article pages (which also contains some admin-like pages e.g. the /privacy-policy page) linear-topic-page - old style linear topic pages (formerly called entries) data-insights - the new short data insights author - author pages about-page - about pages like the team page fragment - utility page fragments like the details on demand doc or data page FAQs homepage - a special type just for the homepage The wordpressId and gdocId columns respectively can be used to a) figure out which of the two is the source for any given row and b) join to the corresponding entity. This table does not contain either archieml nor markdown content (for space reasons). If you care for those, consult the view posts_unified_with_content

[
    "Max Roser",
    "Hannah Ritchie",
    "Esteban Ortiz-Ospina",
    "Joe Hasell"
]

CREATE TABLE posts_unified (
            id INTEGER PRIMARY KEY AUTOINCREMENT,
            slug TEXT,
            title TEXT,
            type TEXT,
            publishedAt TEXT,
            updatedAt TEXT,
            authors TEXT,
            createdAt TEXT,
            publicationContext TEXT,
            gdocId TEXT,
            wordpressId INTEGER,
            FOREIGN KEY(gdocId) REFERENCES posts_gdocs(id),
            FOREIGN KEY(wordpressId) REFERENCES posts(id)
            );