Hub unification: Initial launch checklist

[NickSto]

The initial launch of the unified Hub will consist of:

• Making the NavBar subsite dropdown visible
• No more posting new news/events on .eu

Todo list

What do we need to finish before we do that?

• Implement dynamic middle panes: Implement dynamic middle panes for EU Galaxy servers #1523
• Implement bare news/events widgets and pages: Bare pages to implement #1479
• Finish subsite homepages: Add content to EU subsite homepages and middle panes #1573
• Let subsites customize their NavBars: Customizable navbars #1576
  • And then customize them: First draft of custom navbar for each subsite #1582
• Let subsites use a custom (sub)site-wide footer: Display each subsite's custom footer instead of the global one #1586
• Implement or drop the galaxyproject.eu/{site}/galaxy/gx{news,events} pages (see comment below): Remove subsite middle panes #1608
• Port more of the old .eu posts (at least to fill up the recent news/events cards?)
• Put redirect/deprecation notices on .eu pages: Add deprecation notice to news and events feeds usegalaxy-eu/website#1056, Start redirecting away from galaxyproject.eu usegalaxy-eu/infrastructure-playbook#421

[NickSto]

On the topic of redirect/deprecation notices, this is a list of existing pages on .eu which list news and events. I'm using this to plan what to do with each one. For some we'll do an automatic redirect (301 or meta refresh), and for others I think we'll want to just put a notice at the top.

That's because initially we we'll only have the most recent content on .org, so if visitors want to reference historical content, they'll need to browse the old site. And serving an automatic redirect will prevent them from accessing it. But some pages, like homepages and widgets, only show the most recent posts, which will all be available on .org. So those are fine to auto-redirect.

.eu path	.org path	source file	action
/	/	index.md	301
/galaxy/news.html	/bare/eu/news/	_includes/filterable_news_list.html	301
/galaxy/events.html	/bare/eu/events/	_layouts/event_list-galaxy.html	301
/widgets/news.html	/bare/eu/latest/news/	_includes/widget_news.html	301
/widgets/events.html	/bare/eu/latest/events/	_includes/widget_events.html	301
/news	/eu/news/	_includes/filterable_news_list.html	notice
/news.html	/eu/news/	_includes/filterable_news_list.html	notice
/events	/eu/events/	_layouts/event_list.html	notice
/events.html	/eu/events/	_layouts/event_list.html	notice
/galaxy/	/bare/eu/usegalaxy/main/	galaxy/index.md	301
/index-metabolomics.html	/bare/eu/usegalaxy/metabolomics/	index-metabolomics.md	301
/index-proteomics.html	/bare/eu/usegalaxy/proteomics/	index-proteomics.md	301
/{site}/	/{site}/		301
/{site}/news	/{site}/news/	_includes/filterable_news_list.html	notice
/{site}/news.html	/{site}/news/	_includes/filterable_news_list.html	notice
/{site}/events	/{site}/events/	_layouts/event_list.html	notice
/{site}/events.html	/{site}/events/	_layouts/event_list.html	notice
/{site}/galaxy/	N/A	_includes/home_news_events-galaxy.html	drop
/{site}/galaxy/gxnews.html	N/A	_includes/filterable_news_list.html	drop
/{site}/galaxy/gxevents.html	N/A	_layouts/event_list-galaxy.html	drop

The ones marked "drop" aren't going to be implemented on .org because although they're present on .eu, they're unused (see analytics linked from #1607).

The /galaxy/{news,events}.html pages technically list all events, not just the most recent, but I think it's still better to 301 redirect them. That's because these are viewed from inside Galaxy and in that situation it's probably better not to bother the user with having to click through to get the most recent posts. We can still have a notice at the top of the .org page letting them know how to access old content if they wish.

Note: I may still be missing some pages under individual member sites.

I started a draft of the deprecation notices here: https://github.com/NickSto/eu-hub/tree/news-events-deprecation