openfreeenergy / openfreeenergy.github.io Goto Github PK

Since the example notebook is available on binder, we should highlight it with a button link in the hero section of the landing page. (cf the "Get started free" link in the theme site: https://proud-alligator.cloudvent.net/)

https://osg-htc.org/acknowledging.html
perses
anything else?

Right now, our URLs for news items include the "categories" (which we're actually treating as unordered tags). Example, a URL with categories lomap and release gives:

https://openfree.energy/lomap/release/2022/03/15/lomap-conda-forge/

Since we don't have a defined ordering on these, this could just as easily have been release/lomap/2022/03/15/lomap-conda-forge/. I think we should change this. Two ways to change (both about equally easy):

1. Distinguish between actual categories and tags. Each post must have 1 category. Possible categories include:

   • releases
   • hirings
   • presentations
   • science
   • misc

   We aren't locked into any set; we can always add more categories later as needed. This could be nice from a URL standpoint because we could have openfree.energy/releases/ as an index with all releases, and then within it openfree.energy/releases/2022/03/15/lomap-conda-forge/ .

2. Completely remove these labels from the URL. In this case, I'd probably want to add news/ as a level, and the URL would be openfree.energy/news/2022/03/15/lomap-conda-forge/

Either solution should be easy to implement (probably took me longer to write this issue).

Note that changing the URLs will break any existing links to them... but I highly doubt we have many incoming links to our 2 little news items.

There are a few folks on there that are no longer on the board.

We should add a copy of the CoC & a DEI statement to the OpenFE pages.

see: OpenFreeEnergy/openfe#474 and: https://www.mdanalysis.org/pages/conduct/

pinging @jameseastwood

I'm using this issue to collect a few things that where we should eventually tweak the CSS to look better. This isn't high priority stuff, but if someone feels like taking a break from real coding to play with CSS for an hour or so, you can probably get some of these fixed.

Slightly important issues:

• Hover transition on Read More links (News page): Until hover, the buttons use our color scheme. On hover, the transition reverts it to the old base theme color (solved in #24)
• Links (in other-blue) are insufficiently distinct from the text. I tried increasing line weight; it seemed like overkill. Maybe a dashed underline would do it?

Very minor issues:

• index page, OMSF banner: link is an unofficial color (but we might have to select something from outside the official set)
• footer: links are unofficial color
• Team page: GitHub icons aren't styled to match the link color
• Team page: Names aren't styled according to our color scheme. Our names should be in badass-blue (obviously!)
• Team page: blurb should probably have some spacing before it starts
• News page Blog post h3 titles in li use the wrong font (this is a bug in the original theme)
• Tags for news items: not using official colors. At least background should be either sandy Sergio or Sergio's cousin
• Tags for news items: Forcing first-letter upper is wrong. These should be all-lower (this is a theme layout issue).

None of these should be considered blockers. They're just relatively low-hanging fruit that we can deal with whenever we have time.

• Image for "Open Source"
• Image for "Binding free energy"
• Image for "Drug design and discovery"

First thoughts are:

• Open source: that cheesy low-f image of a screen of code (maybe try to make it Python code, not HTML like everyone else does 😂)
• BFE: Maybe a thermodynamic cycle similar fig 2 in the livecoms best practices
• Drug design and discovery: Maybe one of our atom mapping visualizations for something interesting-looking?

At least, once it has a release on conda-forge.....

@hannahbaumann : As part of your onboarding, we also usually ask you to add yourself to the team page of the website!

There are instructions in the README of this repo, you can see the recent PR where James added himself in #59, and you can see all of our individual pages in the _team/ directory. The results, after merged, will show up at https://openfree.energy/team/

For a picture, you can either use an existing online image (several of us use our GitHub avatars), or you can upload a picture as part of your PR.

try.openfree.energy needs to point to a new url for the updated showcase notebook.

This is something that came up, during some discussions.

I think it would be really nice to have an Emeriti Section on the team page. (we could also add a Emeriti page, but I think that's to much Pages in the end. ;) )

For future consideration: We might get different pics (at least, some of us). They're a little blurry (especially noticeable on Mike), and Irfan looks... very different in real life.

This isn't necessary for first launch, but keep in mind that we can backdate "news" ("blog") posts -- so we can write them for things like hire dates or previous releases. This can help us fill out some content in the short term.

Couple of things post-publication:

1. Is there a missing picture?
2. Bullet points are missing

i.e. "Relative Binding/Hydration Free Energy Calculations using the Hybrid Topology approach, including the capability of charge changing transformations Absolute Hydration Free Energy Calculations “Vanilla” Molecular Dynamics (MD) simulations Automated setup approaches for the calculations Automated analysis of results" should have bullet points.

Would you be able to update this accordingly @jameseastwood ?

The target audience for this should be people who might fund OpenFE, and want to know more about what we're doing.

I am not sure how GA is showing up.
This bit seems to indicate that we have to have a site key set for it to add the script: https://github.com/OpenFreeEnergy/openfreeenergy.github.io/blob/main/_layouts/default.html#L14-L21

But it seems to be putting the script in anyway (viewing page source)

<script>
	window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)};ga.l=+new Date;
	ga('create', '', 'auto');
	ga('send', 'pageview');
</script>
<script async src='[https://www.google-analytics.com/analytics.js](view-source:https://www.google-analytics.com/analytics.js)'></script>

I wonder if instead of having our key set like this

google_analytics_key:

If it needs to be

google_analytics_key:''

or something

See example in the /_team/ directory in #1.

If you want to use the scholar field, just paste in everything after https://scholar.google.com/. The website will add the words "Google Scholar" (with the appropriate link) under your GitHub username link. If you leave it blank, nothing will be there.

Eventually I guess we should put pictures up as well (I hate that part).

• @IAlibay
• @dwhswenson
• @richardjgowers
• @mikemhenry
• Diego

See https://github.com/OpenFreeEnergy/openfreeenergy.github.io/tree/main/_team for examples, e.g. https://raw.githubusercontent.com/OpenFreeEnergy/openfreeenergy.github.io/main/_team/ialibay.md

These are rendered at https://openfree.energy/team/

EDIT: Instructions added to README in #30.