Reconciled Word v2

Usage Guide

What is Reconciled Word v2?

Version 2.0 of the Reconciled Word plugin adds:

  • A Gutenberg block for inserting and configuring reconciled words in the block editor (point-and-click).
  • A fallback shortcode [reconciled_word_v2] that works even if v1 is not installed.
  • Automatic delegation: if v1 is installed and active, v2 will pass requests to v1’s renderer, ensuring consistency with older pages.

When to use v2

  • You want a visual block editing experience.
  • You need a separate shortcode from v1 so both can run side-by-side.
  • You want to maintain v1 for legacy pages but use a more editor-friendly UI for new content.

1. Gutenberg Block Usage

Block name in editor:

Reconciled Word v2

Steps:

  1. In the block editor, click the + button to add a block.
  2. Search for “Reconciled Word v2”.
  3. Insert it into your page or post.

Sidebar settings:

  • Term: The exact word/phrase from your JSON data.
    Example: Fear of the Lord
  • Show section: Choose which part to display:
    • all (default)
    • literal
    • metaphorical
    • allegorical
    • collective
  • Data file (optional): Path to the JSON file relative to the plugin folder.
    Default: data/epo_seed.json
    Example for a custom file: data/epos_theology.json

Preview in editor:

  • Shows a placeholder note that full rendering happens on the front end.
  • Saves your settings to render in PHP when the page loads.

2. Shortcode Usage

The v2 shortcode is:

[reconciled_word_v2 term="Fear of the Lord" show="all" data="data/epo_seed.json"]

Attributes:

  • term (required): Name of the term as defined in your JSON data file.
  • show (optional): all, literal, metaphorical, allegorical, collective. Default: all.
  • data (optional): Path to JSON data relative to plugin folder. Default: data/epo_seed.json.

Examples:

[reconciled_word_v2 term="Wisdom" show="literal"]

[reconciled_word_v2 term=”Truth” show=”metaphorical” data=”data/epos_philosophy.json”]

Delegation to v1:
If v1’s shortcode [reconciled_word] is available, [reconciled_word_v2] will pass its settings to v1 for rendering.

3. Data File Format (EPO Schema)

The plugin reads JSON data in the same Etymology–Polarity Object format as v1.

Example entry in data/epo_seed.json:

{
  "term": "Fear of the Lord",
  "definition_reconciled": "Filial, reverent awe before the Holy that orders cognition, affection, and will, excluding cowardly dread while preserving moral gravity.",
  "polarities": {
    "A": "Fear/Terror (boundary honesty)",
    "B": "Awe/Reverence (attraction to holiness)"
  },
  "units": {
    "tokens": ["Fear","of","the","Lord"],
    "source_languages": ["Hebrew","Greek","Latin","English"]
  },
  "divisions": {
    "literal": ["Heb. yirʾāh / yārēʾ; Gk. phobos/eulabeia; Lat. timor (filialis vs servilis)"],
    "metaphorical": ["holy ground", "fire/light", "throne/majesty"],
    "allegorical": ["beginning of wisdom", "covenant fidelity"],
    "collective": ["honor (kavod)", "piety (eusebeia)", "cowardice (rejected)"]
  },
  "provenance": {
    "canon": "Holy Bible",
    "languages": ["Hebrew","Greek","Latin","English"]
  }
}

4. Adding or Changing Data

  1. Open the data/epo_seed.json file in a text editor.
  2. Add new entries to the array in the same schema as above.
  3. Save the file.
  4. If using a different file, upload it to the plugin’s data folder and update the block or shortcode data attribute.

5. Styling

Add this CSS in Customizer → Additional CSS to style the rendered entry:

.rw-entry {
  background: #fff;
  border: 1px solid #e5e5e5;
  border-radius: 12px;
  padding: 16px;
}
.rw-entry h3 { margin-top: 0; }
.rw-entry details { margin: 8px 0; }
.rw-entry summary { cursor: pointer; font-weight: 600; }

6. Coexistence with v1

  • Both plugins can be active.
  • v2’s block/shortcode will work without interfering with v1’s [reconciled_word] shortcodes.
  • If you deactivate v1, v2 will still render entries using its own renderer.