Would be possible to move the Nodes section to the bottom of the page, being the last section?
To be able to operate with the collection, such as sharing it or checking the properties, we need to navigate to the bottom of the page, as all nodes will appear at the top.
The ideal solution would be to have some sort of pagination, to avoid loading and showing all the nodes in a single page. But this quick solution, at least, could facilitate navigating that page.
On the other side, maybe adding the number of nodes would be useful (e.g., Nodes (12)).
Also, even ordering by getlastmodified, not displayPath. Not sure what is displayPath here, as filenames (UUIDs + ics) are not in order:
Finally, a bug, I think the </section> shouldn't be outside the conditional (check the above "Nodes section" link).
What do you think? I can create the PR, but wanted to know first if it is acceptable.
Would be possible to move the Nodes section to the bottom of the page, being the last section?
To be able to operate with the collection, such as sharing it or checking the properties, we need to navigate to the bottom of the page, as all nodes will appear at the top.
The ideal solution would be to have some sort of pagination, to avoid loading and showing all the nodes in a single page. But this quick solution, at least, could facilitate navigating that page.
On the other side, maybe adding the number of nodes would be useful (e.g.,
Nodes (12)). Also, even ordering bygetlastmodified, notdisplayPath. Not sure what isdisplayPathhere, as filenames (UUIDs + ics) are not in order:Finally, a bug, I think the
</section>shouldn't be outside the conditional (check the above "Nodes section" link).What do you think? I can create the PR, but wanted to know first if it is acceptable.