hacksc / odyssey Goto Github PK

We should have an API route that any admin can hit. Something like GET /api/admin/profiles that will support a variety of query params

Ex: GET /api/admin/profiles?status=verified|submitted will return all of the user profiles that are verified and submitted

Specs

• Write GET /api/admin/profiles which will return a gigantic JSON object of all the profiles
• Extend this route and allow it to support 1 basic query (for now)
  • ?status=XYZ - filter profiles by status

Let's get the reposting going, want to add affiliate codes so people can help spread the word. Making a full proposal in Quip

i must've messed up my logic for displaying things...

this is what the profile object is

a super useful trait for evaluating completing projects is how many hackathons they have been too before.

Sentry Link: https://sentry.io/share/issue/44f93b85a6f0428ba7ca7031d2707653/

GET https://odyssey-staging-hacksc.herokuapp.com/_next/static/
JokgKPq1NLFhcXCKtMpzo/pages/auth/logout.js net::ERR_ABORTED 404 (Not Found)

Logging out seems to hang, but does successfully logout. If we hit another request or do anything with the page, it does seem to have successfully logged out tho.

We need a way to generate referral links from some kind of admin screen for marketing.

I want to add a button to the dashboard the copies the questions to clipboard, it's my standard workflow for completing apps.

Configure Heroku to:

[x] Auto-deploy on merges to main branch (develop)
[-] Auto-run migrations on new deployments
[x] Configure repo to protect develop branch (require approvals before merges)

Facebook is desperate in need of users & data. Let's figure out someone's way to get them all of our information and help keep @saresend employed!

Plus the re-targeting is useful af.

Add some sort of mechanism in Odyssey that enables users to specify who their teammates are

I'm thinking there could be a "Teams" tab on Odyssey that lets you create a team w/ a unique ID that you share w/ your potential teammates

Ex:

• go to "Teams" tab, you "create a team", you get the team ID: "H4U8", you send code to your friends
• your friends add themselves to team "H4U8"

willing to iterate on this, i think this is the best and most formalized way to do teams since just asking for names requires so much work on our part during application review

• hover state for "save" and "submit"
• DONE: "tell us about a project you have finished in the past?" (make into a statement, not a question)
• DONE: change results text from "HackSC Application Results" to "HackSC Application Complete"
• DONE: have active tab in a different color
• view results should be disabled or have a disclaimer that decisions haven't been released yet
• DONE: update question one in the application to say that a user isn't locked into the vertical they choose

sentry gets filled w/ errors from development. we should add a tag to sentry errors so we know if it's from production or dev

What this is

I'd like a CLI that we can call as follows:

odsc-admin add [email protected]
odsc-admin remove [email protected]
... # Other functionality here

So we can quickly manage reviewers without having to drop into working on the production database directly. Also, hopefully we could integrate all of our scripts into this helper CLI so that we can improve ergonomics of working on this project

Steps to reproduce:

• Fill out the application to completion and select a resume file
• Click "Save for Later"
• Refresh application
• Click "Submit" -- will say resume hasn't been provided even tho it technically has

• A lot of FE code could be broken down into cleaner, more re-usable components...
• Clean up a lot of our methods, split code into methods that are easier to test

Reported by Diya in #2020-hacker-questions

We need a way to be able to send emails to people, with segmenetation on properties such as schools or status.

There are 2 ways I can see to do this, we can either use the sendgrid api to import the contacts and send from there. Or add a dashboard to send it from an admin page.

@WilhelmWillie @saresend Thoughts?

Push notifications (transactional & marketing) are useful for helping to drive conversions and certain user actions e.g. submit app or send affiliate links.

Thinking about setting up firebase for it

On dashboard show days to application close

The minor dropdown apparently lacks autocompletion

how we can do this:

• add an additional status inProgress to hackerProfile model
• set it to true when the user saves a profile for the first time
• add additional logic checks in the status step

• dashboard should be accessible at odyssey.hacksc.com/admin
• only profiles w/ the role organizer should be able to access
• need to write additional middleware to check if a user is authenticated AND if they are an organizer
  • odyssey.hacksc.com/api/admin/*should use this middleware

Why?

We need an admin dashboard to do application judging

We'll also likely add more features to this dashboard, those of which are TBD

Right now, our express server handles sessions in memory. This has been fine for now, but creates issues when the server reboots due to new deploys. New deploys will reboot the server causing current sessions to be lost. This means users will have to constantly log in and out. Because we plan on making frequent updates to Odyssey over the next few weeks, I believe it's high priority for us to fix this and figure out a way to get sessions to persist.

No way to check what file you've uploaded when submitting resume

Just a nice touch to prevent lost application data

IMPORTANT: Time zones!!!!!!!!

• backend: Lock down /api/profile
• frontend: Disable submit button

Relevant docs: https://auth0.com/docs/email/templates

This might be tied with #56, but Google auth provider causes redirection to a 404 Page, rather than the dashboard. The dashboard does however work if you go to it manually.

Repro Instructions:

Go to the sign up page in auth0, and sign up with a google account that does not have a preexisting email associated with a HackSC identity. This should get you to the 404