Skip to content
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

Fleshing Out ucla-opensource Page #124

Open
matthewcn56 opened this issue Jul 17, 2022 · 1 comment · May be fixed by #125
Open

Fleshing Out ucla-opensource Page #124

matthewcn56 opened this issue Jul 17, 2022 · 1 comment · May be fixed by #125
Assignees
Labels
enhancement New feature or request

Comments

@matthewcn56
Copy link
Member

Our main infrastructure is almost set up, the next page we should work on is making the ucla-opensource page to highlight UCLA's opensource projects! Similarly to how in the work in progress good first issues section of the contribute page as made in #97 , we should use the Octokit repository search feature to search all repositories which have the ucla-opensource topic.

We can simply display the projects similarly to how we display them on the projects page, but we'll just have to change the image associated with each project.

Similar to the mapReposToProjects function currently being used in the projectRequest.ts page.

Using getStaticProps as outlined in the Next.js Incremental Site Regeneration docs, we can grab these projects in designated intervals (once per hour?) to ensure our info is up to date!

@matthewcn56 matthewcn56 added the enhancement New feature or request label Jul 17, 2022
@Amyh11325 Amyh11325 linked a pull request Jul 21, 2022 that will close this issue
@matthewcn56
Copy link
Member Author

Linked to #7 and @BryanPan342 , we'll def push this during ACM's GM in fall and try to get research profs on board as well to try and encompass all of UCLA's open-source projects!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants