July 20, 2023 / Experimental 🥹 new Grid View and 🏛️ Columns Layout in Docs

Leveraging Field Combination in Fibery: Insights from Drupal’s Approach

1. Potential Issue in Fibery: Fragmented Data Display

  • Fibery’s default setup I see often results in fragmented information across a single page.
  • My temporary solution involves activating a unified field that merges all databases, restricting the display to entities that have a direct relation.
  • However, this method falls short when trying to amalgamate fields from diverse entities into a single cell or card.

2. Drupal’s Approach: Utilizing ‘Global: Custom Text’ and Field Tokens

  • Drupal’s Views module enables the creation of a ‘Global: Custom Text’ field in the views table, which can incorporate field tokens. See also https://www.drupal.org/project/token
  • This allows a single table cell to present a combination of token outputs. For instance, a cell could display a user’s name, email, and last login date all together.

3. Advantages of Field Tokens

  • Field tokens provide a user-friendly, code-free method for users to customize the output of a field.
  • They can be used to display a field in a variety of formats. For example, a date field could be displayed as “July 7, 2023”, “07/07/2023”, or “2023-07-07” depending on the token used.

4. Suggestion: Enhanced Integration of Field Tokens in Fibery

  • Fibery currently employs tokens within its automation features.
  • An improvement could be the introduction of ‘lookup tokens’ in Fibery views, enhancing the adaptability and compactness of the output. For instance, a lookup token could be used to display the name of a related entity directly in a view, without needing to navigate to the entity itself.

Conclusion

  • Enhancing token integration in Fibery could offer users greater control over entity field displays, addressing a frequent request within the community.
  • I am available to provide additional examples or engage in further discussion if needed.