CONTRIBUTING GUIDELINES.
Every contribution matters. Whether you're submitting bug fixes, adding new repo scrapers, or refining neo-brutalist UI components.
1. The OpenSourceHub Git Flow
Fork & Clone
Fork the repository on GitHub and clone your fork locally. Run npm install.
Create a Feature Branch
Create a branch named after the issue: git checkout -b fix/issue-number.
Implement & Test
Write clean TypeScript code, follow existing UI patterns, and run npm run build to ensure zero type errors.
2. Neo-Brutalist Design Standards
OpenSourceHub follows a distinctive Neo-Brutalist visual language inspired by Google DevFest and developer culture. All UI PRs must respect these rules:
2px solid black borders (border-2 border-black) and hard drop shadows (shadow-[4px_4px_0_0_#000]).
Warm off-white surface (#fffbf0), Yellow CTA (#fbbc05), and Blue accent (#4285f4).
Plus Jakarta Sans for bold display headings, Space Mono for badges, metrics, and code snippets.
Avoid subtle blur, transparent glassy cards, and purple/neon SaaS gradients. Keep surfaces crisp and tactile.
3. Pull Request Checklist
feat:, fix:, docs:.Join our Builder Community
Submit your first PR on GitHub and get listed on our Meet the Builders leaderboard.