Feat/53/website redesign notes #54
Conversation
|
|
||
| ```text | ||
| Learn | ||
| ├── What Is OpenAPI? (Relocate existing page). |
There was a problem hiding this comment.
| ├── What Is OpenAPI? (Relocate existing page). | |
| ├── What Is OpenAPI Initiative? (Relocate existing page). |
To avoid confusion with the specification itself. We can explain all 3 specs briefly on that page.
| Learn | ||
| ├── What Is OpenAPI? (Relocate existing page). | ||
| ├── [Learn About OAI](https://learn.openapis.org/) | ||
| ├── [OAI Courses](https://training.linuxfoundation.org/full-catalog/?_sf_s=openapi) |
There was a problem hiding this comment.
| ├── [OAI Courses](https://training.linuxfoundation.org/full-catalog/?_sf_s=openapi) | |
| ├── [Online Courses](https://training.linuxfoundation.org/full-catalog/?_sf_s=openapi) |
| The following are the drop downs we should aim for. | ||
|
|
||
| ```text | ||
| Learn |
There was a problem hiding this comment.
Shall we add Tooling under Learn? Or we can add something like Ecosystem, where we can have learn materials + tooling
There was a problem hiding this comment.
Ooh I like ecosystem! But will that draw the right attention?
| ├── [Overlay](https://spec.openapis.org/overlay) | ||
| ├── [Registries](https://spec.openapis.org/registry/) | ||
| Community | ||
| ├── [Collaborate on Slack](https://communityinviter.com/apps/open-api/openapi) |
There was a problem hiding this comment.
We're going to have Slack/GitHub icons. Do we need a dedicated menu item for Slack? Though, i think it might be important to have a page to describe how collaboration happens in OAI. E.g. the main communication channel is Slack, it's divided into sub-channels for each spec/SIG, etc. Also, how to join community meetings, not everyone knows where to find this information.
| > HERE LETS HAVE A CAROUSEL OF MEMBER LOGOS THAT AUTO TRANSITIONS RIGHT TO LEFT, SHOWING MEMBER LOGOS | ||
| > Button under the carousel - "All Current Members" - goes to https://www.openapis.org/members |
There was a problem hiding this comment.
Is this part of the member value proposition? Because otherwise, it is permanently ceding tremendously valuable screen real estate to a single purpose. Also, not all web pages need a carousel. It's usually used when you are trying to sell things and want to put different options in front of visitors immediately, in a way that can be updated quickly.
Our list of members does not change very often, and what benefit do we get from routing traffic to them? Again, if that's part of our member value proposition that's one thing, but eating up this part of the web site has a big cost.
It's more common to see a grid of members/contributors/sponsors further down. If we must have a carousel, it should be used to highlight timely events and announcements that we want users to take action on.
There was a problem hiding this comment.
Agree on the carousel for announcements... e.g. events, new spec versions, or maybe even new members... e.g. Jentic just signed up to support OAI, there was a post on LinkedIn, in addition we could have a banner in a carousel for a month on the main page or so as part of the package for new members.
There was a problem hiding this comment.
@pavelkornev yes, announcing a new member would be a good use, as it's a transient but important thing to highlight.
No description provided.