Improve the GitLab Serverless product page
Problem to solve
As a developer, in order to make a wise technology choice, I want to make sure that GitLab fits me well, and I can get started using it quickly.
As a manager, in order to make a wise technology choice, I want to gather all the information if my serverless use cases are supported.
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
We can think of many features to add. This is a brainstorming of features, that we would like to shortlist for MVCs:
- call to action: get started. Following it the user can choose between the serverless project templates.
- blog posts on using GitLab with AWS and Knative, in different use cases (frontend heavy, api heavy, etc...)
- presentation of main features
- CI/CD
- Monitoring
- Easy getting started
- hosting / api endpoints with a domain
- separate section for K8s+Knative and AWS Lambda
Proposal
We want to improve:
- https://about.gitlab.com/product/serverless/ <-- focus on this primarily
- https://about.gitlab.com/topics/serverless/ (this will be a separate issue)
Content
Over the fold contents:
- present our Knative and AWS Lambda integrations with separate getting started call to actions
- Knative should speak to people already using K8s, it's NOT a K8s getting started CTA
Remaining contents:
- features descriptions
- selected blog articles
- link to strategy and documentation
Call to actions
- for AWS: start a new project with a template, the README should describe how to retrieve AWS credentials and add them to GitLab
- for Knative: start a new project with a template, the README should describe how to install Knative after adding an existing cluster
Documentation
PMM should review the contents
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by 🤖 GitLab Bot 🤖