Possible agenda item: For docs.borg, maybe the non-code syntax related documentation and policies should go under a new "Organization Policies" section? Not the most pressing or exciting idea...
For reference on #2, I did open an all-encompassing issue for the technical side (I haven't had time to work on it yet): https://github.com/backdrop-ops/backdropcms.org/issues/1107
As for...
For today's dev meeting:
There are a lot of topics for today, but these two would be important:
1. AI policy
The draft ist mostly the same as back in May. Any chance, it will...
Comments
This issue may be related (and it looks like it has a PR that can be tested):
https://github.com/backdrop/backdrop-issues/issues/2134
That PR wont be in production any time soon. But you could make a quick access condition module, its quite simple. Use as a guide: https://github.com/backdrop/backdrop/blob/1.x/core/modules/layout/plugins/access/path_layout_access.inc or https://github.com/backdrop-contrib/block_scheduler
Your form function would probably be something like:
$form['nid'] = array( '#type' => 'textfield', '#title' => t('Node NID'), '#default_value' => isset($this->settings['nid']) ? $this->settings['nid'] : '', ); $form['term'] = array( '#type' => 'textfield', '#title' => t('Term'), '#default_value' => isset($this->settings['term']) ? $this->settings['term'] : '', );And your access function:
function checkAccess() { $entity = $this->contexts[$this->entity_type]->data; return isset($entity->{$this->settings['term']}); }Some adjustment may be necessary.
As an easy workaround without any coding Views could be your friend.
We'd need some more info about your use-case though. Could you describe a bit more, please?