Make an explicit "community" section

Open
#52 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
content, web-dev

Research direction

The issue does not name any files, tests, or entry points. Start by locating how existing site sections are defined and how projects are identified as Google-owned; clarify the intended community content and presentation before making a change. Done means the site has an explicit section that showcases non-Google-owned projects.

Written by the indexing model from the issue text.

Description

A section to show off things that are not Google-owned.

Dominant language
TypeScript
Stars
127
Forks
49
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebaseopensource.com

All issues in firebase/firebaseopensource.com

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.