Skip to main content
Enter REZICS

Zones & Docks

Compose custom surfaces from Block Schema, search conditions, and navigation for web-novel libraries, light-novel libraries, work wikis, and personalized discovery.

Current statusIn development

Zone identity, search conditions, navigation structure, wiki Zones, and Realm/Unit Dock foundations are implemented; full theming and self-service composition remain in development.

Core purpose

A Zone organizes a content surface around user needs. Unlike a Realm, content usually appears because it matches search and filters, not because the Zone owns it or holds a fixed membership relationship.

Docks are common sidebar or auxiliary-block surfaces for Units. Realm tabs, books, media, software, and other detail pages can insert controlled blocks at designated positions while retaining their official product sections.

Block Schema is the shared foundation

Zone pages, navigation, and Docks use block documents with _type, _key, and version semantics. Portable Text, full Post views, Unit lists, feeds, menus, and search templates each have closed schemas, parsing rules, permissions, and failure states; arbitrary JSON never executes in a client.

Products they can serve

  1. Catalogue Zones for book, web-novel, published-book, light-novel, comics, film, or software libraries.
  2. Work wikis organized by menus, wiki Posts, and search blocks across works and books.
  3. Personalized discovery from trusted search templates for popular, recommended, or tag combinations.
  4. Special subjects such as large series, game modules, or cross-media worlds, without copying shared content into every Zone.

Foundations available now

Zone identity, search conditions, navigation content structure, wiki Zone routes and administration, and Realm/Unit Dock reading, editing, and rendering exist. Blocks revalidate owner, viewer, visibility, and referenced targets.

In development

Full themes, self-service composition, more blocks, reusable cross-owner block Units, mobile Dock placement, and large search projections remain in development. Low-frequency blocks require controlled lazy loading so no page pays for every component.

Relationships and boundaries

A Zone is not a Realm, tag, collection, or fixed page. It composes queries and presentation while content identity and ownership remain on the source Unit. A block document becomes a Unit only when independent authorship, publication, visibility, or cross-owner reuse genuinely requires it.

Continue through the product network

Realm Reader CommunitiesBuild long-term community contexts around works, genres, and shared interests, helping readers move from finding works to finding genuine fellow readers.Content FeedsCompose work, post, and community updates into sourced, contextual, continuously paginable streams—not an indiscriminate timeline.Cross-language booklistsCarry one reader’s selection, order, and context across languages while presenting works each reader can understand and reach.
Enter REZICS