| 开发者 | robertjbecraft |
|---|---|
| 更新时间 | 2026年8月31日 23:58 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.3 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
gazette_entrygazette_entry_kindgazette_relationship[[Target Entry]]gazette_entry can carry metadata such as:
gazette_entry_kind. The plugin can seed default kinds such as Location, Character, Organization, Culture, Technology, Creature, Vessel, Document, Artifact, Event, Reference, and Story. These terms are used to classify entries and can drive public archive indexes.
Relationships
GazetteBuilder supports a controlled relationship vocabulary for describing how one entry connects to another. Relationship types are defined as posts in gazette_relationship and include a relationship ID, canonical name, inverse label, source/target entry types, symmetry settings, multiple-relationship settings, and forward/inverse display rules.
Relationships are declared per Entry using the format:
Relationship Name: Target Entry
For example:
Located in: Syrtis Major
Member of: Royal Geographical Society
These declarations are resolved against actual Entries on the site. When a declaration resolves, the source Entry displays a forward relationship link, and the target Entry automatically displays a reverse (inverse) listing of every Entry that points to it, using the relationship's configured inverse label. No separate declaration is needed on the target Entry.
Reverse relationship listings are alphabetized with letter dividers and jump navigation, rendered in a multi-column layout. The number of columns is configurable from GazetteBuilder → Options (1-6, default 2).
Story support
Stories are built by organizing entries through a shared Story ID and sequence position. This allows the plugin to group sequential content into a story arc, expose landing and continue flow for readers, protect unreleased entries behind a release model, and redirect readers away from unavailable story steps.
Semantic references
GazetteBuilder supports inline semantic links using the syntax [[Target Entry Name]]. When a matching published entry exists and is release-eligible, the reference is rendered as a link. Otherwise it remains plain text or unresolved, depending on site configuration.
Timeline and display features
The plugin supports timeline-driven output with the [gazette_timeline] shortcode, including types, min, max, orientation, and summary attributes. Entries are included in published timelines when they have valid sort data, release visibility, and relevant metadata.
Entry-type indexes
For entry types marked as indexable, the plugin exposes public archives such as /entry-type/location/ and /entry-type/character/, sortable by title or release date.
Import workflow
GazetteBuilder includes ZIP-based import support for packaged worldbuilding content, including Markdown entry files, media files, front matter metadata, story and release metadata, timeline sort values, semantic reference data, and relationship declarations. The importer validates packages before creating content and reports invalid input instead of silently importing broken data.
Release model
GazetteBuilder supports a release-aware visibility model: published Entries with no Release Date are immediately readable, future Release Dates keep otherwise published Entries hidden until they become available, and Story Entries redirect readers away from unavailable steps.
/wp-content/plugins/gazettebuilder directory, or install the plugin through the WordPress plugins screen directly.No. Entries use the standard WordPress editor, with additional GazetteBuilder metadata fields added to the edit screen.
Yes. Each Entry can have a Release Date. Entries with an empty release date are immediately readable; Entries with a future release date remain hidden until that time.
Define a Relationship Definition from the GazetteBuilder → Relationship Definitions screen, then declare relationships on an Entry using the format Relationship Name: Target Entry.
Yes. GazetteBuilder supports importing ZIP packages containing Markdown entry files, media, and front matter metadata from the GazetteBuilder → Import screen.