OpenLake / OpenLake/OpenLake--Website

Add a resources section

Open
#13 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
TypeScript
Stars
3
Forks
16
Avg merge
8h 54m
Merged PRs (30d)
7

Description

Resources Section

🎯 Objective

To provide a centralized knowledge hub that equips students with the tools, tutorials, and context they need to get started with and grow in open-source development.


📚 Section Structure
1. Getting Started
  • What is Open Source?
    • Basics of FOSS, licensing, why contribute?
  • Git & GitHub Essentials
    • Introductory guide with commands, GUI alternatives
    • Creating your first PR walkthrough (with GIFs or videos)
  • Common Tools
    • VS Code, Git CLI, GitHub Desktop, Docker (for advanced workflows)

2. Contributor Pathways
  • Frontend Development
    • React, Next.js, TailwindCSS guides
    • Starter templates
  • Backend Development
    • Node.js, Express, NestJS guides
    • API design resources, database basics (MongoDB, PostgreSQL)
  • DevOps & Infra
    • GitHub Actions basics
    • Deployment tutorials (Vercel, Netlify, Render, etc.)
  • Open Source Program Guides
    • GSoC, LFX, Hacktoberfest, C4GT
    • How to apply, write proposals, past OpenLake selections

3. Issue-Hunting & Contribution Guide
  • How to find good first issues
  • How to communicate with maintainers
  • How to write clean, review-friendly code
  • Writing good commit messages

4. Curated External Resources
  • 🧠 Blogs, YouTube channels, and MOOCs
  • 📘 GitHub repos (e.g. awesome-open-source)
  • 🧰 Tooling (Linters, formatters, boilerplates)

5. Glossary
  • Open source terms and acronyms explained (e.g. PR, CI/CD, LTS, CLA)

📐 Design Notes
  • Responsive card layout (tag-based filtering: “Beginner”, “Frontend”, “Docs”, etc.)
  • Icons or illustrations per category
  • Search bar at the top for quick lookup
  • Markdown-based content (optional) – to allow easy PR-based contributions

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue does not identify any files, tests, or entry points. Start by locating the website's existing page and content structure, then define the resource categories, filtering, search, and responsive layout; done means the resources section is populated and matches the listed structure and design notes.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
content, documentation, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.