Integrate resources pages into a single OHW22 menu

[emiliom]

I've overhauled @abkfenris's initial exposure (PR #167) of the "resources" pages. Here, all those pages are integrated into a single OHW22 menu column (toctree). The bulk of those pages are now under directory ohw22/ev (ev = event; I wanted to keep it very short and not fully intelligible).

I've also exposed the schedule page (still a stub) more prominently.

Some things are still not updated from OHW21 (I wasn't trying to do that), a couple of pages are stubs, and the initial OHW22 page should probably be modified so it presents the "event" pages more prominently and not just via the menu. This is meant for discussion of the structure I'm proposing; this is an alternative to PR #167.

Includes the tweaks I proposed in https://github.com/abkfenris/oceanhackweek.github.io/pull/2

[netlify[bot]]

✅ Deploy Preview for oceanhackweek-preview ready!

Name	Link
🔨 Latest commit	6656088d38269bcd23ba25c162079126830391e0
🔍 Latest deploy log	https://app.netlify.com/sites/oceanhackweek-preview/deploys/62e38fd0f9e0b500092fd101
😎 Deploy Preview	https://deploy-preview-170--oceanhackweek-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[abkfenris]

The menu structure looks good, but I still think the resources should be their own directory (outside of an events) so that we don't end up duplicating them for every event.

Then we can use the version switcher going forwards.

For some reason I never got a notification for your PR against my branch....

[emiliom]

The menu structure looks good, but I still think the resources should be their own directory (outside of an events) so that we don't end up duplicating them for every event.

Then we can use the version switcher going forwards. image

I think we do end up needing to duplicate and tweak the resources pages (or at least some of them) every year, because some details change or need to be updated. But, we can decide next week whether resources (or whatever we call it) is its own directory or is under the event directory. As long as we present a clear event view to users, the internal folder structure shouldn't make a difference.

For some reason I never got a notification for your PR against my branch....

How odd

[emiliom]

@leewujung can you take a look at this proposed organization and layout and let us know what you think? Thanks.

[emiliom]

@abkfenris what path should we take? Let's try to make a decision soon, so we can turn our attention to content.

How about a quick call on Tuesday?

[abkfenris]

Ok, I incorporated the single menu structure into #172 but keeping the resources on their own path.

I split moved the schedule page into the event, as that is something that is truly distinct year to year, but many of the resources shouldn't have huge changes (they tend to become better year over year, but not get outdated).

If we manually version them by event, we will end up with a ton of duplicate pages down the road to wade through, where as we can expose the git versioning of the resources with the theme drop down.

[emiliom]

172 supersedes this PR. I'll close this one.