knative / knative/ux

[Improvement Proposal] Adding 1-liner to explain the use case on home page

Open
#125 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
13
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Might be helpful taking this into consideration when thinking about the website redesign v2 issue.

In the current design of our homepage, particularly under the "Case Studies" section, we present testimonials from users sharing their experiences with Knative. While these insights are valuable, they may not directly resonate with potential users or effectively highlight how Knative addresses specific challenges. Case studies are a really important in demonstrating the value of our platform and aiding individuals in determining whether Knative is the right solution for their needs!

To enhance the utility and relevance of our case studies, I think adding the concise, one-liner summaries that clearly articulate the use cases of Knative in addressing real-world problems will be helpful. These summaries will serve as direct links between potential users' challenges and the solutions provided by Knative, showcased through our existing case studies. And this will motivate people clicking into the case study to read more.

For example, something like
- "See how XX company use Knative Eventing to simplify their order dispatching system"
- "See how Knative Eventing help the medical researchers at Deepc deliver MRI image to the right AI service
- "See how ZZ company move from their traditional tech to cloud with Knative
- ...

![image](https://github.com/knative/ux/assets/36619969/021c96aa-2e6a-4b86-8c7f-42c294e9ce83)

@knative/ux-wg-leads @nainaz

Contributor guide

Open the contributing guide

Research direction

Start with the homepage's Case Studies section and review the existing case-study content, along with the referenced website redesign v2 issue. Add concise one-line summaries that explain each case study's Knative use case and encourage visitors to open the full story; verify the wording in the homepage preview.

Written by the indexing model from the issue text.

Assessment

Domain
content, web-dev
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.