- Issue created by @lrwebks
- Assigned to thomas.frobieter
- Status changed to Postponed
about 1 year ago 9:17am 31 August 2023 - 🇩🇪Germany Anybody Porta Westfalica
I'm not sure we should really do this as I can't see a clear benefit yet and I think it's leading away from the original plan.
Typically this would of course be the right way to go, but we need to keep in mind, that some things are different here:- We don't talk about regular Drupal entities, but support all kind of sources for our list of wiki entries
- We can't use Views for that reason
- We need to allow searching all contents, but can't use Core or Views Search and need to solve it light-weight as nobody pays us for this
- ...
But there are still many options, which we simply don't use regularly, so may sound strange first:
- JS Search
- Accordion and/or Tree View
- Anchors to open / jump to a specific result
- ...
This still makes it possible to have the expected functionality and features without bloating the tasks and needing to invest months of work here.
Let's solve this smart with usability in mind.TL;DR:
With that concept, I think an additional view mode will not help here! So should we use this task for the points listed above or better create a separate one to improve the list page? (I'd tend to create a new one and close this won't fix). - Status changed to Closed: works as designed
about 1 year ago 9:34am 31 August 2023 - 🇩🇪Germany Anybody Porta Westfalica
Closing this task in favor of 📌 [META] Implement wiki overview as single-page Active