-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Complete Update/Overhaul of Hugo Backend #105
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Complete Refresh of TESLa Site Backend
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 16:54 — with
GitHub Actions
Failure
Add permissions to deploy token
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:01 — with
GitHub Actions
Failure
Don't actually need this
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:03 — with
GitHub Actions
Failure
Workflows are hard
Workflows are still hard
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:10 — with
GitHub Actions
Failure
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:17 — with
GitHub Actions
Failure
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:24 — with
GitHub Actions
Failure
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:27 — with
GitHub Actions
Failure
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:33 — with
GitHub Actions
Failure
kelseasouders
had a problem deploying
to
github-pages
March 27, 2024 17:35 — with
GitHub Actions
Failure
Apparently the GitHub checks might not allow deployment through PR's... might have to merge to see that it deploys. It builds fine, though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a test PR to ensure that the build-deploy process still behaves with the new
hugo
updates. The files appear to have changed, so I am unsure if it will be "plug and play".This PR contains much-needed updates to the
hugo
backend that we use for the TESLa website. The previous version was extremely outdated and featured a convoluted file structure that made things more difficult than necessary. According to thehugo blox
documentation, the best course of action when updating an "ancient" installation is to scrap everything and bring thecontent/
directory over, so I have done just that.I have also cleaned up the file structure and pruned a significant amount of the extra "bloat" files that we were keeping, for some reason. In the event that we want to add extra blocks in the future, you can find the guide to do so here.
As it stands, the content of the site should be as close to a 1:1 remake of the original form, save for certain functional aspects that weren't kept in the new version of the
theme-research-group
repo (for instance, the tabs in the navigation bar no longer highlight).I have made a few organizational changes that should make the site easier to maintain. The entire homepage is controlled by
/content/_index.md
, instead of dozens of separate files. Furthermore, I have organized the/content/authors/
directories so that a user's information is contained in a single directory, as described in the README.This is an initial commit of sorts, so I will need to verify that the build process still works, but everything renders correctly on my laptop running
hugo v0.124.1
.