Skip to main content
Enter REZICS

Posts

Carry articles, wikis, reviews, replies, and chapter content so that every publication retains identity, context, and traceable versions.

Current statusAvailable

Article details, Portable Text bodies, global/Realm context switching, interaction bars, reply discussions, and other foundations are implemented.

Core purpose

A publication is not merely an isolated page. A Post carries Unit identity, multilingual content, creative attribution, subjects, tags, Realm publication context, history, replies, and interactions. Articles, wikis, reviews, replies, chapters, and pictures all use a shared publication protocol, then add the rules of their own product role.

What is available now

  1. Create Portable Text titles, summaries, and rich-text bodies with links, spoilers, images, and Unit mentions.
  2. Show article details with author or publisher, relative time, type, and multilingual body content.
  3. Provide an interaction status bar, reply entry point, and shared participation context.
  4. Switch between global and Realm reading contexts; the desktop view has a Realm sidebar and mobile uses a selector.
  5. Show work and entity subjects, related content, and replies.
  6. Publish the same Post to multiple Realms without transferring it.

Realm publication context

Realm context answers which community perspective a reader is viewing. Entering from a Realm retains that context; entering from the global view can select another Realm where the Post has been published. Removing a Realm removes the publication relation, not the Post itself.

Portable Text and Blocks

A body is not raw JSON. It is wrapped in a document with _type: "portable-text", stable _key values, and version semantics. Block documents define storage, API, cache, rendering boundaries, and revalidation. This permits mentions, custom blocks, metrics, and more presentation forms.

In development

Draft editing for published content, more Post surfaces built through Block Schema, Q&A and question-Post relationships, and mature default-context behavior for multiple Realms remain in development or planning.

Relationships and boundaries

A Post is not a work Unit or a Content Structure. Chapters reuse the same Post protocol, but every occurrence in a structure has its own node identity. Short replies use reply relations; formal revisions use editing and History. These mechanisms do not replace one another.

Continue through the product network

WikisConnect shared knowledge about works, people, and worlds to real subjects so revisions, sources, community context, and navigation can evolve together.Picture PostsUse one or more ordered images as the subject of a publication while retaining title, description, source, attribution, and work relationships.ReviewsKeep a complete judgment, scores, reviewed subject, and Realm context together so readers can understand why someone evaluated a work that way.
Enter REZICS