9. 19th Jul. 2023 (Wednesday)

19th Jul. 2023 (Wednesday)

Meeting notes

Date: 19th July 2023, Friday

Target audience: ACCESS-Hive dev team

Goals/Agenda

Improve the UI of the “Run a model“ landing page with GIFs or code animations.
Ensuring natural logical layout of the “models“ landing page. Perhaps, having the components first followed by configurations for a natural flow...
Condensing/shortening “models“ tab sub-headings, might be too long (change ”Supported ACCESS model configurations” to just ”Supported model configurations“ etc )...
Shortening model configurations text on the rectangular cards, having just one-two liners.
“Community resources” renaming to “resources“ and discussing subsections structure.
Decide upon the content of “User support page“ and how that’s gonna be linked to the user support model on github (Aiden, Claire, Roger...)
Linking ACCESS-NRI and ACCESS-Hive by using tagline “hosted by ACCESS-NRI”, perhaps below the top-left heading (to be visible at all times).
Have discussion about what is the contribution/development scheme of ACCESS-Hive, and what’s the difference in function between the Hive and the Forum (might need to be extended to other people like Aidan, Claire, Andy..)

Discussion Notes

UI OF "RUN A MODEL" SECTION

Davide could be working on improving the run a model page. And put the gifs in there.

ORDER OF "COMPONENTS" and "CONFIGURATIONS"

Smaller text for different configurations.
Also, might need to think about from the beginner point of view as it could be possibly more logical to have the components up or may be just stay as it is.
The text in the rectangular cards is quite long and that could be possibly reduced.
Have clear definitions of what components, and configurations are, and their differences on the supported access-models page.
For making it a bit more visual and we could add some more diagrams. We could possibly remove this image too or have it at the bottom, to avoid taking too much space at the top.
We might also consider changing the text at the model configurations top section, having simple definitions of what models are, model components, and experiments are.
Overall team agreement - Keeping the order as it for having the configurations first and followed by components, for users who just want to quickly get started with some of the configurations offered. Could have the GIF.
We could reduce the text in the model configurations tab by one-liners.

MODEL CONFIGURATIONS TAB

The CM and AM are related and we could have them together or possibly just have an unbiased order in left hand side contents.
The choice of text possibly depends who are using the Hive, so we might need to use simple language for considering everyone.
We could have another discussion about the text of what we need to include.

DEVELOPMENT WORKFLOW

We can create the issues and even if they are not deployed on the development branch, they could still be worked upon.

SKILLSHARE

How to use the hive and what the hive is about and what the models part is all about.
What the community resources is all about.
For the SkillShare, how people can add suggestions to the hive.
Romain suggested that there a range users to the ACCESS-Hive, and we could utilise the fresh eyes and could use some of our time for someone to provide suggestions about the hive.
Discuss about the images to include on the hive page.
Davide would be giving an introduction of what has been completed and introducing the new hive. Explaining the changed to be made in the home page.
Heidi would possibly be doing the models tab.
Sven would be talking about the community resources, model evaluation and the about tab.
Where should we allow people to give comments to for the hive page. Could possibly have another channel in slack and have suggestions about the hive page.
Asking people in the SkillShare if they would like to review particular things on the hive page, or just have any suggestions they have for the hive page.
By the end of July, we do need to have the external people to look at that, and for the soft release. We might to have it looking in the polished state before the external review.

HOME PAGE

Action Items

Have clear definitions of what components, and configurations are, and their differences. Should we it as footnote or display it diagrammatically - https://github.com/ACCESS-Hive/access-hive.github.io/issues/463.
The text in the rectangular cards is quite long and that could be possibly reduced.
Could have a GIF explaining the coming together of models to make the model configurations - https://github.com/ACCESS-Hive/access-hive.github.io/issues/463.
We need to remove the title of the pictures for the configurations, and could just have it in the title - https://github.com/ACCESS-Hive/access-hive.github.io/issues/435.
Add all of the above action items as issues on zenhub (if they are not already) :)

Add or link all the above items to zenhub.

Participants