Content operations
| Property or method | Purpose |
|---|---|
select(...fields) |
Starts a fluent query; .from(collection) binds its collection. No arguments selects all prepared metadata. |
query |
Collection namespace: query.posts.findMany(options?) and query.posts.findFirst(options?). |
count(collection, options?) |
Filtered parent count before pagination. |
readBody(collection, id) |
Retained text or undefined; missing entries reject. |
render(collection, id) |
{ html, headings }; missing or unrenderable entries reject. |
Await a fluent builder directly or call .all() / .execute() to return an array. .first() returns one entry or undefined; .count() returns the matching parent count. from() is available only after select().
The relational namespace uses columns, with, where, orderBy, limit, offset, and adjacent options. Omitting columns returns all prepared metadata. Relationships, bodies, and rendered output remain explicit requests.
Generated types
Both the physical server entry and content-query:server export CollectionKey, CollectionData<"posts">, and Collections as types. CollectionData includes the ID, validated metadata, and computed fields.
Keep runtime imports on the server. See querying content and rendering content for usage.