Skip to content
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

Fy23 redesign #616

Closed
wants to merge 13 commits into from
Closed

Conversation

cyndy-llnl
Copy link

Individual comments by file. In general, changes include:

-Addition of a metadescription
-Addition of framing copy (/visualization pages only)
-Reorganization of header hierarchy
-Copy updates for fy23-redesign

Added metadata, fixed header hierarchy, made header capitalization consistent, updated copy in anticipation of fy23-redesign.
Added metadata, updated header hierarchy, updated copy for fy23-redesign
Added metadescription, updated header hierarchy, updated copy for fy23-redesign
Added metadescription, updated header hierarchy, updated copy for fy23-redesign
Added metadescription, framing copy
Added metadescription, framing copy
Added metadescription, framing copy
Added metadescription, updated copy for fy23-redesign
@cyndy-llnl cyndy-llnl requested a review from a team as a code owner July 12, 2023 17:02
Copy link
Member

@IanLee1521 IanLee1521 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cyndy-llnl - this looks great overall! Really thankful for your work here!

The biggest thing I want to hash out is the presence of the {% raw %}{% endraw %} blocks that you've added, why are those being added after all the links?


If youre new to GitHub and open source in general, figuring out how to get set up can be a challenge. You may want to read through the GitHub Help pages on [setting up and managing your GitHub profile](https://help.github.com/categories/setting-up-and-managing-your-github-profile/).
If you're new to GitHub and open source in general, figuring out how to get set up can be a challenge. You may want to read through the GitHub Help pages on [setting up and managing your GitHub profile](https://help.github.com/categories/setting-up-and-managing-your-github-profile/){% raw %}{% endraw %}.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's the rationale for {% raw %}{% endraw %}. ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that I see this in many places (every link?), and don't understand why it's there.

permalink: /about/faq/
---

## {{ page.title }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll need to fire this up locally and check it out, I seem to recall there being a reason for starting at H2 here in these files, but I can't quite remember.

pages/about/faq.md Outdated Show resolved Hide resolved
pages/about/index.md Outdated Show resolved Hide resolved
@cyndy-llnl
Copy link
Author

@cyndy-llnl - this looks great overall! Really thankful for your work here!

The biggest thing I want to hash out is the presence of the {% raw %}{% endraw %} blocks that you've added, why are those being added after all the links?

Hi Ian! That's based on guidance from digital.gov around the handling of external links. The {% raw %}{% endraw %} adds an external link icon on dev.llnl.gov, but perhaps that isn't true for the Software site?

I should also note: Some of these updates "won't make sense" until our dev has had the chance to get in and implement the design (coming soon!) stuff. We know what components we're building so I went ahead and prepped the copy accordingly, but the full thing won't be complete for a hot minute.

cyndy-llnl and others added 2 commits July 12, 2023 10:57
Sounds good! Wasn't sure if you'd be up for having your email so readily accessible

Co-authored-by: Ian Lee <[email protected]>
@hauten
Copy link
Contributor

hauten commented Jul 12, 2023

I will set aside some time very soon to review in detail locally

* [Visualization Software Stands the Test of Time](https://str.llnl.gov/2021-05/brugger)
<!-- END: Quicklinks boxes -->

### 2020 LLNL Computing Virtual Expo Materials
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cyndy-llnl What do you think about removing "2020" from this heading so it doesn't seem so outdated? The assets from the Expo are fairly evergreen.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hauten That works! I'm a fan of including the date if something is "of a moment," but when it's evergreen, you'll entice more folks to use it when an older date is omitted.

One thing: Is that a change you're making or that you'd like me to make? Happy to participate however you prefer!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cyndy-llnl I made the change just now, thx

Copy link
Contributor

@hauten hauten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cyndy-llnl If by chance the changes go live before the end of August, I'd like to retain the temporary banner from the currently live home page. It advertises tutorials that end on Aug 31. After that date, we don't need it anymore. Markup for the banner is in 47f696a.

@hauten
Copy link
Contributor

hauten commented Jul 19, 2023

@cyndy-llnl and @IanLee1521 I'm finished reviewing. I have one question for Cyndy above, plus one note about the temporary tutorials advertisement on the currently live home page. I made two commits that Cyndy may want to review. No other changes from me.

@cyndy-llnl
Copy link
Author

@hauten We made a note about the tutorial banner and will retain it if we're able to launch before 8/31. I think the commits look good (and they'll make even better sense once Doug gets ahold of the site). Thanks!

@hauten
Copy link
Contributor

hauten commented Oct 2, 2023

Incorporated and confirmed as part of #647

@hauten hauten closed this Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants