please create Logseq/Entity/Article/Blog as a more specific entity. In general, I prefer Person/<Name>/Blog/<YY>/<MM>/<slug>, with a readwise-url if one exists.
please create Logseq/Entity/Series. A Series should be combined with another entity to represent a sequence. By default, Series should appear in the Logseq namespace after the entity type and before the entity, and the parts of the series will appear clustered by the series as well as in order on the filesystem when sorted Lexicographically. For example, while Logseq/Entity/Book would imply that Philip Pullman's book His Dark Materials should have a page at Person/Philip Pullman/Book/95/The Golden Compass, if a page is both a Book and a Series entity, it should then be rightly be placed instead at Person/Philip Pullman/Book/Series/His Dark Materials/<Appropriately Zero-Padded ordinal>/95/The Golden Compass, or Person/Philip Pullman/Book/Series/His Dark Materials/95/1 - The Golden Compass. If a page is both a Podcast and a Series entity, similar rules should apply, and similar combinations for other entities that form a series. 1 here is an optional appropriately zero-padded ordinal. If the series currently terminates in n digits of ordinal references, then all instances should be zero padded to n digits so that sorting them lexicographically does not perturb the intended order. The intention of the ordinal is to aid in memorization or identification. In the case of a podcast, an ordinal number should never be given unless the podcast's published feed and/or title references that ordinal number such that one can google "<podcast name> episode <number>" and reliable get to the episode in the top hits. Hard requirement: the entity definition for a series must not imply that "series" is particular to books and podcasts and must be stated in a way that generalizes across the garden to its applications elsewhere. Books and podcasts may be used in the entity definition as examples as long as they are accompanied by examples that are not Books and Podcasts.
please create Logseq/Entity/File/Format as a light-weight entity specifically for file formats, for example, docx, PDF, ePub. A page that is a file format entity should list things such as operating systems that support it, it's basic structure, the standards that it represents, the evolution over time, etc.
create Logseq/Entity/Time/Year as an entity meant to model a particular year, while also modeling decades and centuries. For example, 19/5/9 should be aliased to 1959 and represent the year 1959. Then 19/5 should be aliased to 1950s, and 19/0 should be aliased to 1900s and 19 should be aliased to 1900-1999.
update Logseq/Entity/Time/Year to indicate that logseq-created-time-year:: should be the logseq property that is used to point to a particular time and year. This is applicable broadly speaking - Books, Movies, Podcasts, Essays, Musical Compositions, Works of Art, etc. Update downstream entity definitions as well to mention this precedent. Create Logseq/Entity/Time/Year/Todos with logseq todos for pages to backfill and their explanation.
By adding prominent Knowledge Gardeners to the garden