Closed amandavisconti closed 2 months ago
Build preview research:
Tested if GH Pages updates site build successfully, without Action setup, for
Also looked in docs and verify GH Pages does this automatically for Jekyll. I.e. GH Pages handles building the site for us automatically without further work/Actions setup needed.
Moved work that needs to be held until after all site renewal priorities completed and published to web (search #1009; build preview action #1010).
(No longer making repo private at any point.)
7/13/2024 verified redirect plugin works!
~Struckthrough~ items below as I add the redirects on my local instance of the realignment branch; all now done, or moved into "not setting up redirects for these" section. Note that some pages ultimately use YAML permalinks instead of redirects (matching URL from current site, so no redirect needed).
The following are redirects on the current server I decided not to set up for the new site, as I believe they should no longer be needed, and if used are better served with a 404 than continuing to include them as redirects. Long defunct location pages: RedirectMatch permanent ^/locations/alderman-library-rm-317/ /hours-and-spaces/ RedirectMatch permanent ^/locations/alderman-library-room-421/ /hours-and-spaces/ RedirectMatch permanent ^/locations/alderman-library-room-421-2/ /hours-and-spaces/ RedirectMatch permanent ^/locations/alderman-library-room-423/ /hours-and-spaces/ RedirectMatch permanent ^/locations/alderman-library-room-423-2/ /hours-and-spaces/ RedirectMatch permanent ^/locations/alderman-library-room-423-3/ /hours-and-spaces/ RedirectMatch permanent ^/locations/auditorium-harrison-institutesmall-special-collections-library/ /hours-and-spaces/ RedirectMatch permanent ^/locations/brooks-hall-common-room/ /hours-and-spaces/ RedirectMatch permanent ^/locations/brooks-hall-commons/ /hours-and-spaces/ RedirectMatch permanent ^/locations/brown-library-rm-133-clark-hall/ /hours-and-spaces/ Other pages that didn't feel like they should/could have redirects: RedirectMatch permanent ^/about/colophon/ /about/#how-was-this-website-made RedirectMatch permanent ^/about/accessibility/ /accessibility/ Pages below are from old WP blog URL formatting. Unclear how to mimic with Jekyll redirect plugin RedirectMatch permanent ^/announcements/(.)$ /blog/$1 RedirectMatch permanent ^/job-announcements/(.)$ /blog/$1 RedirectMatch permanent ^/digital-humanities/(.)$ /blog/$1 RedirectMatch permanent ^/experimental-humanities/(.)$ /blog/$1 RedirectMatch permanent ^/geospatial-and-temporal/(.)$ /blog/$1 RedirectMatch permanent ^/grad-student-research/(.)$ /blog/$1 RedirectMatch permanent ^/podcasts/(.)$ /blog/$1 RedirectMatch permanent ^/technical-training/(.)$ /blog/$1 RedirectMatch permanent ^/uncategorized/(.)$ /blog/$1 RedirectMatch permanent ^/visualization-and-data-mining/(.)$ /blog/$1
For that last set of potential redirects (from old WP blog categories), we might be able to use the Jekyll redirect plugin, but I think this is not something we should spend time on until the renewed site is pushed to the web. My guess is that we'd use the plugin readme's "customizing the redirect template" section to create a layout that would use liquid templating to move through all the blog slugs from the WP-era publication date ranges. (This would redirect a bunch of URLs no one will ever enter as they did not exist, e.g. /podcasts + all the blog titles from that era since we don't know which were in that category.) Or actually, we do still have WP categories in most posts as YAML categories, don't we? So maybe this is easier. Still not doing it for now, and asking others to not either until site renewal priorities done and published.
~To ask about:~
Shane: "We run the scholarslab.org DNS but not any virginia.edu domain. For scholarslab.org, we have separate records for the base domain and for each subdomain (www works just like, say, takeback)". Jeremy: says to ask shane, but "I"m pretty sure we automatically redirect any scholarslab.org/* traffic to scholarslab.lib using CodeFlare's DNS stuff; Then the rewrites and redirects for scholarslab.lib take effect."
Latest list of to-dos:
Completed research and decision, moved remaining tasks to new ticket; closing this as #1013 handles the latter actual move to all-GH
Noting /realignment branch commit https://github.com/scholarslab/scholarslab.org/commit/06f98249cf42ab942fa0365b4516291a4fe08fae addresses items in this message https://github.com/scholarslab/scholarslab.org/issues/992#issuecomment-2218265235 under "redirects I did not create", making old posts point to where these posts currently reside instead of using old broken links
~Plan~ (instead, see messages below for latest version of to do list): ~1. Test out GH Pages + Actions for site build/deployment (to replace current UVA server and deployment code) *~ ~2. Test if redirects (may need Jekyll redirect plugin) satisfy our redirect needs AND work with GH Pages plugin limits, GH actions~ ~3. If simple, test if GH Actions can implement site search (and update/create ticket re:search either way, so Jeremy knows re:design and open fall work)~ ~4. Talk to Shane~ ~5. Temporarily remove search from site, if GH Actions don't have easy solve now (to explore/readd in fall after other retheming work done)~ ~6. Point domain at GH Pages-hosted site~ ~7. Make repo private (unless decide otherwise; Jeremy is interested in open, and Shane may be; both did not respond until a while after the deadline request, so fine with proceeding as planned for now but at least consider in fall once have time to adjust licensing, credit info)~ ~8. Explore regaining Netlify-like build preview via free action: https://github.com/rossjrw/pr-preview-action Amanda started testing out actions deployment on new repo 7/2 (https://github.com/scholarslab/deploydog); see also my research here below~
Background work (completed!):
Pros:
Cons:
Options for SLab website hosting and deployment:
My (Amanda) preference is currently #2 (all GH); reasons below. Talking with Shane 7/10/2024 about his preference for (#1 or #3?).
My (AWV) reasons for moving to all-GH:
This is a change I can implement myself, and prefer to perform myself (since I document things quickly for others to also learn; and to confirm my understanding of all pieces involved).
Research on impacts of moving to all-GH: