Last updated on July 6, 2026
Elements currently occupy an ambiguous position between standalone content, reusable narrative components, and semantic relationship structures. Several parallel tasks have emerged around shortcode rendering, dynamic embedding, metadata inheritance, relationship tracking, visual presentation, featured-in systems, chapter extraction workflows, and contextual attribution. These issues are all manifestations of a larger unresolved architectural question regarding the nature of Elements themselves.
This task will:
- Define the formal ontology of Elements within the platform.
- Determine whether Elements should remain lightweight content-only entities or support structured metadata.
- Establish a single content reuse strategy (dynamic rendering, static duplication, or hybrid synchronization).
- Create relationship systems that track where Elements are used and surface reverse contextual attribution through Featured In and related-content interfaces.
- Determine how Elements should visually appear throughout the CPT ecosystem and whether they should share presentation layers with Chapters and Fragments.
- Evaluate how Elements participate in narrative assembly systems, semantic composition, footnotes, references, and larger interpretive structures.
- Clarify when content should exist as an Element versus a Fragment or Chapter.
- Normalize frontend rendering behavior while preserving relationship integrity even when Elements are not publicly displayed.
- Support future extraction of reusable narrative units from existing Chapters and Fragments.
The goal is not immediate standardization, but discovery of the correct compositional model through continued Element creation and experimentation. Implementation decisions should emerge from observed usage patterns rather than assumptions inherited from Chapters, Fragments, or WordPress content structures.