Ref #122 -- the design of this page is still very much in progress. However, we can still analyze and agree on the best technical solution and stand up a minimal page in the right place.
There will need to be a page that sits in front of the NTA Arclight homepage (right now catalog#index). This VT landing page will at minimum contain 2 links and live at virtualtribunals.stanford.edu
Into the main page for NTA Arclight (catalog#index) (virtualtribunals.stanford.edu/nuremberg)
To the Spotlight exhibit for Virtual Tribunals
The most obvious approach to handling this requirement is:
Simply create a new route/page in this repo for the landing page. Pros: Contained within this application, simpler. Cons: potential routing weirdness. Future of VT is unclear, not sure this will make sense long term or if most other VT content will be added to this Arclight instance.
We should discuss as a team and decide on an approach.
Strategy: virtualtribunals.stanford.edu hosted in our instance, root static page
/nuremberg is a static page that has NTA specific landing page and can take you into catalog with a filter applied to only see NTA stuff
Design question: how should we navigate from the Arclight/item/catalog pages back up to the root/VT page and/or /nuremberg page -- does this impact the headers design
Taube Archive of the International Military Tribunal (IMT) at Nuremberg (1945-1946) is currently the application title. This now changes to Virtual Tribunals.
Ref #122 -- the design of this page is still very much in progress. However, we can still analyze and agree on the best technical solution and stand up a minimal page in the right place.
There will need to be a page that sits in front of the NTA Arclight homepage (right now
catalog#index
). This VT landing page will at minimum contain 2 links and live atvirtualtribunals.stanford.edu
catalog#index
) (virtualtribunals.stanford.edu/nuremberg
)The most obvious approach to handling this requirement is:
We should discuss as a team and decide on an approach.