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

Members Portal: Create a way for members to reference past problems we have done #30

Open
philr35 opened this issue Feb 5, 2019 · 2 comments

Comments

@philr35
Copy link
Contributor

philr35 commented Feb 5, 2019

This would be beneficial considering we don't have a central place for people to look for the problems we have done. Additionally, Slack removes messages because we're on free edition, so we would end up losing previous messages with solutions.

@joncwong
Copy link
Contributor

joncwong commented Feb 8, 2019

Asking for everyone else's reference or incase I may want to pick it up, but how would this be executed? Manually integrated every week? Or a section of the site embedded with Medium/Google/Blog site (where we would update it from Google/Medium/etc and auto updates to our site)?

@philr35
Copy link
Contributor Author

philr35 commented Feb 8, 2019

So this issue requires both front end and back end.

This requires a system where the tech leads would select their problems, and they need to either paste in the leetcode problem into a google sheets, or submit them through a frontend gui. We've been using google sheets, just to keep the cost free, instead of a db, but also because the tech leads can visually go into the sheets to modify anything.

For the members portal, the frontend would make a request to our backend the makes a request to the google sheets

The format could be something like this:
Spring 2019 |
Week 1 | Stacks and Queues | leetcode url | leetcode url
Week 2 | Graphs | leetcode url | leetcode url

Just my thoughts on how this could be implemented

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

No branches or pull requests

2 participants