Addresses #222 - Highlighting all of the Pythia resources from the landing page #227
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
for more information, see https://pre-commit.ci
|
This pull request is being automatically built with GitHub Actions and Netlify. To see the status of your deployment, click below. 🔍 Git commit SHA: 705e9e2 |
brian-rose
reviewed
Mar 25, 2022
Co-authored-by: Brian Rose <brose@albany.edu>
Co-authored-by: Brian Rose <brose@albany.edu>
jukent
approved these changes
Mar 25, 2022
There was a problem hiding this comment.
Looks great @clyne Thanks for adding this! I merged @brian-rose 's suggestion.
|
@brian-rose, comments addressed. Thanks! |
brian-rose
approved these changes
Mar 25, 2022
|
LGTM! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Fixed #222 - Highlighting all of the Pythia resources from the landing page
This PR addresses the content aspect of #222, adding descriptions and links for webinars, data sets, and cookbooks.
It does not address the aesthetics issues raised by @brian-rose, namely:
"Get rid of text and present a grid/panels of resources; more graphical and inviting"
I suggest we consider opening a second issue to address the aesthetics.