Mngr: Created page with "= [Subsystem Name] – Technical Implementation Documentation = This page documents the actual implementation of this subsystem in Drupal. It is not about design intentions, but about how the system is configured, where it lives, and how to maintain or debug it. == 1. Purpose == Describe in 2–3 lines what this subsystem is supposed to do. Example: * Provides a read-only publisher view of a record. * Displays the asset table for the selected node. == 2. Where It Is..."

2026-04-03T10:17:37Z

Created page with "= [Subsystem Name] – Technical Implementation Documentation = This page documents the *actual implementation* of this subsystem in Drupal. It is not about design intentions, but about how the system is configured, where it lives, and how to maintain or debug it. == 1. Purpose == Describe in 2–3 lines what this subsystem is supposed to do. Example: * Provides a read-only publisher view of a record. * Displays the asset table for the selected node. == 2. Where It Is..."

New page

= [Subsystem Name] – Technical Implementation Documentation =
This page documents the *actual implementation* of this subsystem in Drupal.
It is not about design intentions, but about how the system is configured,
where it lives, and how to maintain or debug it.

== 1. Purpose ==
Describe in 2–3 lines what this subsystem is supposed to do.
Example:
* Provides a read-only publisher view of a record.
* Displays the asset table for the selected node.

== 2. Where It Is Implemented ==
List exact Drupal UI locations and file paths.

=== 2.1 Drupal UI Locations ===
* Content type: <code>[Content Type Name]</code>
* Manage fields: <code>[Field Name]</code>
* Manage form display: <code>[Form Mode]</code>
* Manage display: <code>[View Mode]</code>
* View: <code>[View Name] → [Display Name]</code>
* Block placement: <code>[Theme] → [Region]</code>

=== 2.2 Custom Code Locations (if any) ===
* Module: <code>custom_[module_name]</code>
* File: <code>src/Plugin/.../...</code>
* Hook: <code>hook_form_alter()</code> or similar

=== 2.3 CSS Overrides (if any) ===
* File: <code>themes/custom/[theme]/css/[file].css</code>
* Selectors used:
* <code>.some-selector { display: none; }</code>

== 3. Configuration Summary ==
Bullet list of the important settings.

Example:
* Field <code>field_assets</code> is NOT translatable.
* View uses contextual filter <code>Content: Nid</code>.
* Display mode “Publisher view” hides metadata fields.

== 4. Dependencies ==
List modules, fields, or other subsystems this depends on.

Example:
* Depends on: Views, Media, Asset-chain View.
* Requires field <code>field_assets</code> to exist.

== 5. Interaction With Other Subsystems ==
Explain how this subsystem connects to others.

Example:
* The asset table is embedded using the Asset-chain View.
* The admin listing links to this view via a custom URL.

== 6. Known Quirks ==
Document anything Drupal does that is “special”.

Example:
* Contextual filter fails if node is unpublished.
* Translation tab appears even though no fields are translatable.

== 7. How to Modify It Safely ==
Step-by-step instructions for future changes.

Example:
# Edit the View “Record View – Places”.
# Do NOT change the contextual filter.
# Add new fields only at the bottom of the field list.

== 8. How to Debug ==
Where to look when something goes wrong.

Example:
* If assets do not appear → check relationship in the View.
* If the page is empty → check contextual filter.
* If translation behaves oddly → check field translatability.

ICT:D - Maintenance TEMPLATE - Revision history