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

The main landing text needs to be improved #9

Open
blokhin opened this issue Feb 18, 2020 · 6 comments
Open

The main landing text needs to be improved #9

blokhin opened this issue Feb 18, 2020 · 6 comments

Comments

@blokhin
Copy link
Member

blokhin commented Feb 18, 2020

In a private communication with an industrial provider, exploring the possibilities to support Optimade, I've received rather strong criticism:

  • the current description text is unclear and difficult to understand
  • the value of supporting the Optimade is not immediately seen
  • from a consumer point of view: a centralized access interface (or at least a library implementing it) is missing

As an example of good landing, the Facebook API was given.

I think, it's very healthy criticism, let's have it in mind.

@blokhin blokhin self-assigned this Feb 18, 2020
@ltalirz
Copy link
Member

ltalirz commented Feb 18, 2020

So far, the optimade.org web site has been mainly developer-centric.
With the paper being published, we should slowly transform it into a user-focussing web site;
PR #5 adds an interactive documentation of the API and so already takes a big step in this direction.

@rartino
Copy link
Contributor

rartino commented Jun 15, 2020

How is this for a brainstorming idea for the front page?:

The text could start with, rather then end with, defining what OPTIMADE is, i.e.,


The Open Databases Integration for Materials Design (OPTIMADE) is a consortium of materials database providers with the aim of making materials databases interoperational.

The OPTIMADE API is an industry standard API that unifies searching and retrieving information from materials databases. → More about the motivations behind OPTIMADE API


And then the rest of the front page could be just two dropdowns + a serch box with the text: *Try out searching materials databases using the OPTIMADE API". One dropdown with a list of "Aggreate (default)" + a choice of databases presently implementing OPTIMADE. A second dropdown with "Search for", Structures, Calculations. A request to a specific database can be submitted to that database endpoint; whereas the 'Aggregate' request can go to @blokhin's skyscanner (although, if we are "standardizing" on it to this degree, I would feel more comfortable if the development was made collaboratively under the Materials-Consortia organization.) There is also obviously a need for a linked (or fold-outable) help text about the filter.

Just a very open suggestion. What do you think?

@gmrigna
Copy link
Contributor

gmrigna commented Jun 15, 2020

Indeed, this page is meant for publicizing OPTIMADE. So far, it was indeed focused on the specifications (which was and is still important) but it would indeed be nice to illustrate what can be done with it. I thus very much like @rartino ideas...

@rartino rartino mentioned this issue Jun 19, 2020
@rartino
Copy link
Contributor

rartino commented Nov 9, 2020

I'll add another issue here: someone really should take a look at the meta tags we have for the front page, because Google is still showing the old OPTIMADE capitalization in the search results (and I cannot figure out why, but setting correct meta tags may solve it.)

@gmrigna
Copy link
Contributor

gmrigna commented Nov 10, 2020

The problem seems to be on Google side (with their cache)... I tried Bing, Yahoo, and DuckDuckGo. They all have the correct capitalization...

@ml-evs
Copy link
Member

ml-evs commented Mar 31, 2021

Is anyone interested in doing this? I see @blokhin self-assigned at the time (I will now remove the assignment to free it up).

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

No branches or pull requests

5 participants