Wolfspyre
Chevereto Member
I've got several context albums, with sub-albums ...
Maybe I'm doing this incorrectly; but my understanding was to create contextual pools via albums, and more specific sub-contextual albums within those.
However, my implementation of this strategy seems to be a little flawed....
Thealbums which contain sub-albums don't seem to show any content or information when viewing them in the UI; for example:
I would expect the default behavior of an album like this to default to: https://img.hoof-paw.art/pool/Synthetic-Creativity.zG/sub
is this a different style of album? or is there a way to assert that albums which have no direct content, but have sub-albums, to have the 'sub' route be their default page?
I looked in the documentation for such a behavior, but didn't see anything that stuck out as a likely path of exploration
Maybe I'm doing this incorrectly; but my understanding was to create contextual pools via albums, and more specific sub-contextual albums within those.
However, my implementation of this strategy seems to be a little flawed....
Thealbums which contain sub-albums don't seem to show any content or information when viewing them in the UI; for example:
I would expect the default behavior of an album like this to default to: https://img.hoof-paw.art/pool/Synthetic-Creativity.zG/sub
is this a different style of album? or is there a way to assert that albums which have no direct content, but have sub-albums, to have the 'sub' route be their default page?
I looked in the documentation for such a behavior, but didn't see anything that stuck out as a likely path of exploration