Create mockups for Usecases and Case studies landing pages

[sm1990]

Description

$subject

Related website/documentation area

Add/Uncomment the relevant area label out of the following.

Describe the problem(s)

A detailed description of the purpose of this new feature.

Describe your solution(s)

A detailed description of how this new feature will solve the problem described above.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

[sm1990]

@anupama-pathirage & @keizer619 please share your feedback on the following designs

[anupama-pathirage]

LGTM.

@sm1990 Can you share how the top nav Explore menu will look like with this change?

[sm1990]

@anupama-pathirage please review the explore menu.

[sm1990]

@anupama-pathirage please review the explore menu.

@anupama-pathirage any thoughts on the top nav design?

[anupama-pathirage]

@sm1990 I am not that convinced about showing only a few things.

How about having all pages as links? Something like below? So the categories are UseCases, Case studies, Comparisons, and Saas (Salesforce, netsuite etc which will add soon)

[sm1990]

@anupama-pathirage are you suggesting that, instead of showing links to the few individual pages under each category, we should show the category name (e.g. Use case, Case studies & Comparisons) and link them to their respective landing pages?

The problem with that approach is that there are only 2 pages under Comparisons, which is not enough to create a landing page.
We can go with that once we have more more content for comparisons. WDYT?

[sm1990]

@anupama-pathirage are you suggesting that, instead of showing links to the few individual pages under each category, we should show the category name (e.g. Use case, Case studies & Comparisons) and link them to their respective landing pages?

The problem with that approach is that there are only 2 pages under Comparisons, which is not enough to create a landing page. We can go with that once we have more more content for comparisons. WDYT?

@anupama-pathirage any thoughts on the above?

[anupama-pathirage]

@sm1990 This is what I have in mind. Open for discussion. @sameerajayasoma Any thoughts?

Somewhat similar to following wso2 menu.

[sameerajayasoma]

Since we have a few case stuides and use cases, I can see the point of displaying 3-4 key ones in the navigation menu it self with a see more link.

[sm1990]

@sameerajayasoma, @anupama-pathirage @keizer619 please review the changes below.

Top nav:-

Case studies:-

Use cases:-

[anupama-pathirage]

+1 to proceed.

[sm1990]

This is live now.
https://ballerina.io/use-cases/
https://ballerina.io/case-studies/