The time has come and we have the perfect skillful candidate to work on this (π @pcambra !) Tokens. There is SBF and Archipelago Specific data that can be exposed as Drupal [tokens] to the Drupal Ecosystem. This issue will just open the door to those and mention the most basic ones:
IIIF servers
A particular JSON key/value of a SBF field (requires flattening special characters because tokens use : as separators and JSON keys can contain those
Direct access to as:images, as:documents Drupal IDs, URLS, etc and also via drop_field as a generic list.
Active View Mode for an ADO
Parent ADOs (via our computed field or via a particular key like ismemberof)
Strawberry flavor document count for a given ADO, and for a given ADO/File Match
These are the ones I can see right now may be useful and I would focus on a first pass only on the ones marked in bold because the second one can really give us already a lot of flexibility
I like how webforms uses Tokens so a good way of integrating this also in our Twig Templates.
What?
The time has come and we have the perfect skillful candidate to work on this (π @pcambra !) Tokens. There is SBF and Archipelago Specific data that can be exposed as Drupal
[tokens]
to the Drupal Ecosystem. This issue will just open the door to those and mention the most basic ones::
as separators and JSON keys can contain thoseThese are the ones I can see right now may be useful and I would focus on a first pass only on the ones marked in bold because the second one can really give us already a lot of flexibility
I like how webforms uses Tokens so a good way of integrating this also in our Twig Templates.
@pcambra more ideas? What do you think?