Skip to content

Latest commit

 

History

History
116 lines (101 loc) · 8.82 KB

File metadata and controls

116 lines (101 loc) · 8.82 KB

Handlebars Template Flow Hierarchy

Key Template Categories

Core Infrastructure Templates

  • search-results-template: Root template handling master record iteration
  • common_template_list: Generic list handler for all collection types
  • common_template_result: Generic individual item renderer
  • common_template_result_inner: Core item structure with fields and metadata

Master Record Structure

  • master_panel_heading: Master record header with ID and basic info
  • master_main: Main content area with tabbed interface
  • master_tabs: Navigation tabs based on page layout configuration

Category Panels (based on page layout)

  • category_panel_details: Core participant info (player_info, contacts, addresses)
  • category_panel_trackers: Tracker history and status
  • category_panel_activity_logs: Process workflows and case management
  • category_panel_external_ids: Real-world identifier systems
  • category_panel_dynamic_models: Runtime-generated data structures

Dynamic Templates (generated per configuration)

  • [model-name]-list-template: Collection view for each model type
  • [model-name]-result-template: Individual item view for each model type
  • activity-log-[type]-result-template: Specific activity log type renderers

Interactive Components

  • edit_item_button: Edit mode toggle
  • rank_button: Record ranking/priority
  • activity_log_common_template_show_button: Activity log navigation
  • model_reference_button_container: Cross-model relationship buttons

Field Rendering

  • common_template_result_fields: Field collection iterator
  • common_template_result_field: Individual field with label and value
  • field_value_substitution: Tag substitution for field values
  • update_metadata: Created/updated timestamps and user info

The template system uses Handlebars partials extensively, with {{> template_name}} calls creating the hierarchical structure. Each level can access parent context data and apply ReStructure-specific filters for user access controls, field visibility rules, and tag substitutions.