Skip to content

feat: add meta-contribution page and homepage card#316

Closed
Yogendra-Bisht wants to merge 1 commit into
OpenSource-Communities:mainfrom
Yogendra-Bisht:feat/add-contribution-meta-page
Closed

feat: add meta-contribution page and homepage card#316
Yogendra-Bisht wants to merge 1 commit into
OpenSource-Communities:mainfrom
Yogendra-Bisht:feat/add-contribution-meta-page

Conversation

@Yogendra-Bisht

Copy link
Copy Markdown

Description

This PR adds a meta-contribution feature to help users understand that the course platform itself is an open source project. It creates awareness and provides a structured pathway for learners to contribute back to the project.

Problem Statement

Currently, the course teaches about open source contribution but doesn't make it obvious that the platform itself is open source and welcomes contributions. This is a missed opportunity for experiential learning.

Changes

  • New Page: /contribute route with comprehensive contribution guide

    • Quick start guide (4-step workflow)
    • 4 contribution categories with specific opportunities
    • Resource links to GitHub, issues, discussions
    • Call-to-action buttons for forking and reading guidelines
  • Homepage Update: Added new card highlighting contribution opportunities

    • Links directly to the contribute page
    • Matches existing card design and styling
    • Mobile-responsive

Testing

  • Built project locally - no errors
  • Design matches existing card styling
  • All links are functional
  • Mobile responsive (tested at 320px, 768px, 1200px)
  • Accessibility considered (semantic HTML, good color contrast)

Screenshots/Demo

Please see the visual breakdown of the changes below:

image image image image image

The new contribution page includes:

  • Eye-catching gradient header
  • Quick start guide with numbered steps
  • 4 contribution sections: Documentation , Code , Translations , Community
  • Resource links section
  • Strong CTA section with fork and guidelines buttons

Related Issues

No open issue. This is a spontaneous feature addition to enhance UX and encourage experiential learning.

Checklist

  • My changes follow the existing code style
  • I have performed a self-review of my own code
  • I have tested my changes locally
  • I have added/updated relevant documentation
  • My changes don't introduce new build errors
  • The PR title follows conventional commits format (feat:, fix:, etc.)

Additional Notes

This feature encourages the "meta-learning" aspect mentioned in the contribution guidelines - learning by doing on the actual platform.

…port

- Create new /contribute page with clean, minimal design
- Add 4 contribution categories with detailed descriptions
- Implement full dark mode support
- Remove emojis for professional appearance
- Add 4-step getting started guide
- Include resources section with GitHub links
- Update homepage with new contribution card
@netlify

netlify Bot commented Jun 23, 2026

Copy link
Copy Markdown

Deploy Preview for learn-open-source ready!

Name Link
🔨 Latest commit 551880b
🔍 Latest deploy log https://app.netlify.com/projects/learn-open-source/deploys/6a3abcb121d1c800080cf1b5
😎 Deploy Preview https://deploy-preview-316--learn-open-source.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this pull request is meant to address.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Congratulations on submitting your first Pull Request! 🎉

We appreciate your contribution. Feel free to join the conversation in our
Community and say hello!

@adiati98

Copy link
Copy Markdown
Collaborator

Hey @Yogendra-Bisht,

Thanks for the PR! We appreciate your contribution. ✨

However, we don't see any issue created for these changes and if we ever had any discussion about this. Please read our Contributing guidelines carefully before you're contributing.

As our courses are about open source, I think it makes a general idea that they're also open source. We also have link on the website to our repo, where folks are welcomed with README that consists "Contributing" section if they'd like to contribute to our repo.

I feel like our contributing guidelines are clearer — it's also include how to install this project, how to work with the contents, how to work with issues and PRs in the repo, etc. General instructions/guidelines to contribute to OSS projects across GitHub are also well written in the Intro to OSS course, if folks really follow the course from start to finish. So, I don't think we really need to have a brand new page and card.

I'd like to know @BekahHW thoughts about this so we might get back to this once she returns. In the meantime, I'm closing this PR as there's no issue accompanying this PR.

Can you please create an issue and elaborate the background of why you propose these changes to convince us otherwise? We might reopen it if we have second thoughts or if you can convince us. Thank you!

@adiati98 adiati98 closed this Jun 24, 2026
@Yogendra-Bisht

Copy link
Copy Markdown
Author

Thank you for the detailed feedback, @adiati98! This is actually my very first open-source Pull Request, so experiencing this workflow firsthand has taught me a lot more than just reading the documentation ever could.

I completely understand the importance of discussing features beforehand to prevent scope creep. To align with the proper process, I have opened an issue here: #317 to outline the "experiential learning" background behind this proposal.

I look forward to hearing your and @BekahHW's thoughts whenever she is back! Appreciate your patience and guidance with a first-time contributor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants