Make the Elm pages "live" #78
Merged
Conversation
This file contains hidden or 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
Today, the Elm detail page is live, but it's not directly reachable from any of the pages on the site. This commit makes it live by adding an Elm entry in the Cloud main page, and also adding Elm to the Cloud ToC.
This reverts commit 03a8130. On the elm branch, we are not "under construction". So, remove the note!
Add a reference to the new User Policy Generator, which will make it a lot easier for users to set a properly locked-down user policy. Also, remove the reference to Globus's example IAM Policy. That won't work right now, because our MinIO does not include support for the `*` wildcard.
Since Elm is a new service that we (from the Globus side) are supporting, add a news post making the announcement. NOTE: This post has a date of July 15. If you are trying to build the site locally before July 15, the post will not display. In that case, add the `--future` flag to your build command. For example, if you normally run `bundle3.2 exec jekyll serve`, you should instead run `bundle3.2 exec jekyll serve --future`. NOTE: GitHub Pages only does not automatically rebuild the site every day. So, if you merge this into `main` before July 15, the post will not display. So, you have two options: * Wait until July 15 to merge this into `main`. * Merge early, and then on July 15, manually trigger the [Deploy Jekyll site to Pages](https://github.com/stanford-rc/globus.stanford.edu/actions/workflows/jekyll.yml) workflow.
|
Forgot to note: If you're building the site locally, remember to add the |
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 PR merges everything from the elm branch into main. Once the PR is merged, the elm branch should be deleted.
Although the Elm details page has been on the live site since its creation, it has only been accessible to those who knew where to look. It is not currently linked in the site itself, and it has an "Under Construction" header on it.
The elm branch changes that:
By merging the elm branch into main, this PR effectively makes the Elm pages "live".
@saracook, could you please take care of shepherding the merge, including any other changes that folks might need?
NOTE: The news post (added in eac45fb) has a date on it. That means weird things can happen if you merge the branch before July 15. See commit eac45fb's message for details!