-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temporary Hacktoberfest page #190
Comments
Hey @TuanaCelik, sure we can definitely add this page! All we need is a github api key for fetching the issues (I think there is one in env already) |
Thank you for the design @TuanaCelik, it represents nicely what I imagined. I updated some parts:
|
@bilgeyucel maybe we should have both register and join discord? The register was for registering to hacktoberfest. I thought we wanted that? |
Registration for the event will happen on the main 'Hacktoberfest 2023' website. I have asked to double-check and see whether it's okay for us to have a 'Register' button as well |
I mean a button that takes people to that page. |
Ok I think we are set @carlosgauci You're a maintainer so you should be able to get the API keys you need. But let me know if you need that from me. |
Hey @carlosgauci
Haystack will be participating in Hacktoberfest this year. Meaning on October 1st we would tag some issues with 'hacktoberfest' on the haystack and haystack-tutorials repo.
The idea is, for that month, we have a page displaying these issues, how they are tagged, and whether they are closed or not.
We would also change the 'get started' button temporarily to 'Hacktoberfest' that takes you to that page. The page could be '/hacktoberfest-2023'
To help with developing this, I've created a repo with mock issues tagged with 'h'. When the time comes, I would change the repo that we pull from, and make the tag we look for 'hacktoberfest'
This requires working with the GitHub API, and fetching the issues tagged with 'h' (eventually hacktoberfest) from the haystack and haystack-tutorials repos.
Is this something you could work on? And if yes, what would you need from us? Anything on vercel or GitHub?
I've also created a mockup for you to review and approve @bilgeyucel
The text was updated successfully, but these errors were encountered: