Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Item

Notes

Review and discuss

  • Follow up on action items from last meeting

Hmm… I don’t think we want to do an HTTP redirect or a DNS change, because we still have project-specific sites like https://samvera.github.io/serverless-iiif/. I’d say the most reasonable approach would be to have a landing page with a client-side redirect (JavaScript code) that changes window.location.href = NEW_URL and has a static “This knowledge base has moved to LINK TO NEW LOCATION” page for people who land on it with JavaScript disabled.

Next steps for pattern and practice guidance

Next steps for pattern and practice guidance

Related documents

https://docs.google.com/document/d/1XIMAUi7kQj7rmQIP3W5nFggFn5BfLh67TwYEPn5yKfw/edit#

https://docs.google.com/spreadsheets/d/1b6DDiikSwo_kOUbU_3htLVc_gsp3PPFvzMzu2QIdUJk/edit?usp=sharing

https://docs.google.com/spreadsheets/d/1OCD2PK2Q7Tkb0ciW6gOQIw0DBuSB0tpyWOXtzD6RPXo/edit?usp=sharing

https://docs.google.com/spreadsheets/d/1qssk3w6WwTLuDijjjC3rXQrUYhcHtWDlKa7RNYy7HI4/edit#gid=0

Samvera Development Knowledge Base

Other items

✅ Action items

⤴ Decisions