Create structure for 'Resources' Page

[harisood]

I’m struggling to think of a good way to structure the resources page - i.e. effectively signpost to resources so users can easily find and discover what they’re after. Current thoughts:

• Categorise by TYPE of resource (e.g. ‘code’, ‘paper’, ‘video’, ‘template’, ‘article’ etc)
  • Pros: Easy to categorise and a good first version
  • Cons: Not very discoverable, as e.g. papers could vary wildly in content (infrastructure design, approaches to sensitivity tiering, user experience…)
• Categorise by TOPIC of resource (e.g. ‘infastructure code’, ‘Toolkits and packages’, ‘information governance’, ‘accreditation’ etc)
  • Pros: Makes content more discoverable
  • Cons: Hard to know what the right categories will be. Also makes it more complicated from a data storage point of view for the website (e.g. multiple tags, more metadata, confusing hierarchies etc)

Any thoughts?

[manics]

We don't have that on the existing website so we can leave it for later?

Ideally I think we should store the resources in a structured file (e.g. YAML), and generate templated HTML pages from that. That also means we can easily generate multiple pages with different views from the same data source. I know how to do it with Jekyll, https://jekyllrb.com/docs/datafiles/ I'm happy to have a go with Hugo at some point if you want.

[harisood]

store the resources in a structured file (e.g. YAML)

I have a simple version of that atm but have also left room for MarkDown, e.g. https://github.com/uk-tre/hugo-website/blob/main/content/community_resources/code/turing_tre/index.md?plain=1

Would be up for going to purely YAML content and rendering templates, though it does make it possible sliiiightly more inaccessible (YAML configuration vs Markdown writing) for contributions

Either way the cataloguing issue still remains. Atm I am just using two different classes of tags but sure there's a better way!

@manics I also wonder if at some point it's worth us sitting down and going through the hugo architecture? Looks p much the same as Jekyll so shouldn't take too long?

[Davsarper]

Agreement on getting it done, and if there are issues in the future address them.

[KirstieJane]

I think these look great - and I feel quite strongly that trying to optomise this further is not the highest priority for a very young community.

My proposal is that if the community are using the resources page and there are so many that they're getting confused then that's a HUGE WIN for the UK TRE community and we can open a new issue when that moment arises 🚀

So I'm a vote for approve and close the issue 💪 Great thought already put in and sufficient in my opinion!

[harisood]

Happy with this as initial structure