backstage / backstage/backstage
🚀 Feature: Create a logo wall
- Dominant language
- TypeScript
- Stars
- 34.4k
- Forks
- 7.6k
- Avg merge
- 8h 57m
- Merged PRs (30d)
- 50
Description
### 🔖 Feature description
Website: Create a logo wall
Create a logo wall containing a recognizable selection of organizations that use the product. Link each logo to the organization's website.
Audience: Evaluator
Type: Marketing
The existing documentation might contain helpful source material that you can pull into this doc change. See this catalog of the existing (at the time of the CNCF tech doc analysis) Backstage technical documentation pages:
https://github.com/cncf/techdocs/blob/main/assessments/0008-backstage/backstage-doc-survey.csv
### 🎤 Context
This issue is a recommended change resulting from an analysis of the Backstage documentation commissioned by CNCF. The analysis and supporting documents are here:
https://github.com/cncf/techdocs/tree/main/assessments/0008-backstage
### ✌️ Possible Implementation
Display an array of organizations that have successfully deployed and are using Backstage on the website landing page. Ideally each logo links to a case study, but it's sufficient to link to the organizations' websites.
For a good example of both a logo wall and case studies, see:
https://kubernetes.io/case-studies/
### 👀 Have you spent some time to check if this feature request has been raised before?
- [X] I checked and didn't find similar issue
### 🏢 Have you read the Code of Conduct?
- [X] I have read the [Code of Conduct](https://github.com/backstage/backstage/blob/master/CODE_OF_CONDUCT.md)
### Are you willing to submit PR?
None
Contributor guide
Research direction
No repository file or test is named. Start with the linked CNCF Backstage documentation assessment and existing Backstage documentation, then locate the website landing page and its current content structure. Done means the landing page displays a recognizable selection of user organizations and each logo links to an organization website or case study.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- content, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100