Here is my thougths:

{{all.p propertyName}}

This is totally achievable with an respect to uniqueness of properties names in the page.

But uniqueness is not a restriction. We can use layers to prioritize blocks to search properties in: current block, page's first block, pages other 1-level blocks top to bottom, page's 2-level blocks top to bottom. It solves your example case with «I want to access this!». If we cannot find property in one layer, it starts to find in the next one.

{{blockName.p propertyName}}

This is achievable too, but such approach has disadvantage: if you change block name (title), then all these blockName.p calls become wrong. They won't be auto-corrected.

How to overcome this?

via block UUID

Instead we can use something like {{block.p ((...uuid...)) propertyName}} to be protected from changing block title. But this way it is not such an easy-to-type approach.

via sub-pages

It requires you to change page structure.
Instead of:

Use:

Sub-pages will be renamed automatically. But you need to keep pages structure.

UPDATE: I was pretty sure that macro call with page reference in the form [[...]] will be renamed automatically:
{{renderer :view, "c.page.props.primary", :page [[CHARACTER TEMPLATE/Character DNA]]}}
but It doesn't work =( so sad. Just left the comment in corresponding bug.

Well, sub-pages is not an option. The rest is reasonable. What do you think?

Awesome response, thank you for so much consideration!

I agree about your sentiments on searching by block title; it'd likely need too much maintenance.

One of my main constraints with the block UUID and the sub-page solution is that there will be a handful of character pages that use this template, and each character will have unique information.

• Am I right to assume the UUID will need to be set each time I use this template to create a new page for a character?
• Similar issue for sub-pages right? I would need to create sub-pages for each section for each character?

If the answers to the above questions are "yes," it seems in my case it would make sense to just search all the properties in all blocks on the page, as in that first example {{all.p propertyName}}. I still have no idea how to do this one 😅

If the answers to the above questions are "yes"

Yes, it is. So the chosen approach is {{all.p propertyName}}

I still have no idea how to do this one 😅

Yep, I just want to clarify the details before any coding.
I need some time to dive into this.

Thank you! I really appreciate you spending time and effort on this. I'll take the help whenever you can get around to it! ❤️

Hello, @rowsof !
Just implemented this idea in new version of plugin (v3.4.0).
Setup instructions are here.