Open lmcnulty opened 2 months ago
I think this is historical in some respect and don't have an objection off the top of my head.
I would like to add the additional constraint: if we move any of these paths, we add and maintain a permanent re-direct.
Summaries were meant to be largely non-dynamic reports/visualizations/pipeline outputs, while apps were meant to be dynamic applications interfacing with the DB. It didn't really work out that way. We don't have random people/orgs contributing these types at present.
I think maybe summaries as a concept is worth keeping around, and killing Apps? Having a collection of windows into an increasingly complex data schema/data types could be useful.
Currently many of our pages have either /apps/ or /summaries/ in the path: e.g. /apps/discover/, /summaries/spatial, /apps/checklists, /summaries/wordcounts. I suspect that the distinction between these two categories is not particularly clear or important to end-users. I think it may make sense to promote these pages to top-level paths. E.g.
This may require some care for SEO concerns.