{"path":"/guide/how-it-works/wf-store/corpora","content":{"title":"One corpus, many content types","summary":"Everything's pages, templates and other assets share a corpus; tags supply their meaning.","breadcrumbs":"[All topics](/guide) / [About Everything](/topics/about-everything) / [How Everything works](/guide/how-it-works) / [wf-store](/guide/how-it-works/wf-store)","body":"A **corpus** is wf-store's top-level collection of assets, tags and retrieval state. Everything deliberately uses one corpus for its wiki content, including articles, page templates, media and related assets.\n\nIt does not require one corpus for pages and another for templates. Nor does it maintain a second page registry. That would introduce coordination work without improving the basic reading experience.\n\nInstead, **tags** describe the kind of asset, its logical identity, its route, its publication state and its collection membership. Page revisions retain immutable source while tags govern which revision appears to a public reader.\n\nThis lets the wiki contain many topics and many different kinds of content without fragmenting the underlying storage model. A topic is a way of browsing, not a separate storage boundary.\n\nwf-store's internal generations, chunk locations and retrieval structures are implementation details. They do not become durable public page IDs or URLs. See [The tag model](/guide/how-it-works/tag-model) and [Assets, components and renditions](/guide/how-it-works/wf-store/assets) for the details.","navigation":"[wf-store](/guide/how-it-works/wf-store) · [Ingestion and search readiness](/guide/how-it-works/wf-store/readiness)","related":[{"title":"The tag model","url":"/guide/how-it-works/tag-model"},{"title":"Assets and renditions","url":"/guide/how-it-works/wf-store/assets"},{"title":"Security and ownership","url":"/guide/how-it-works/security"}]}}