venhance / mosp-web

General MOSP website

👋 Hi there!

I am Evan Chen, an MIT grad student and math olympiad coach. You can find me in the following places:

I'm also an amateur programmer, I guess.

🖼️ Pictures of Evan coding

mosp-web's Issues

Modal for completed hunts

On a page like https://mosp.evanchen.cc/volume/I if the hunt has completed (and hence spoilers are enabled) it would be nice if there was some more obvious notification after the list of chapters that the bottom right has the option to enable spoilers. You can probably write a

after the list of chapters and apply some Tailwind classes to it. https://nerdcave.com/tailwind-cheat-sheet is useful as a reference for Tailwind.

Right now, the Enable Spoilers and similar are pretty faint, easy to miss. You may like to tweak the color too.

Hint model

Write a model named Hint in core/models.py for the hint system, and integrate it into the admin interface in core/admin.py. You can mostly follow the existing code for examples of how to structure this.

Each Hint object needs to point to particular puzzle, have a question, content, and cost in patience (integer).

Try out projects -> issues system

This might require a code commit lol

Not solved should allow linking to solution page

Consider the page
https://mosp.evanchen.cc/chapter/1/spoil
and look at a situation in which the solver has some unlocked/found puzzles that aren't solved yet.

The "Not Solved" links should ideally be "Not Solved (link to solution)".. Search for the "Bypass puzzle" link in order to figure out how to set the URL.

Note that the link to solution should only show up in spoiler mode, so https://mosp.evanchen.cc/chapter/1 should not show such links.

pass djlint

aaaaaaaaa

Show hints

https://mosp.evanchen.cc/I/puzzle/kindergarten

Modify the view and template so that, if the hunt has finished, a clickable 🎁 shows up. Clicking the gift box should yield a modal with all hints associated to that puzzle in a dropdown, and picking one should reveal the hint content.

Logic for spending patience or delay is not needed now; these will be implemented for "active" hunts later on. Consequently it's not necessary to display the patience costs for now.

This should probably be done via SweetAlert. Check checkname.ts for an example of how SweetAlert is used.

Isolate courage by chapter, not additive

This is probably better to do after #18 is done.

Move token logic into middleware

Pick a text editor

Both of you should pick a code editor. Some names I hear:

Windows

• Notepad++ is simple and pretty clean
• Visual Studio Code is more bulky, but I hear lots of good things about it
• Atom is also simple and clean.

Mac

• Sublime and Atom are simple / clean.
• You can try the built-in Vim if you really want, but be warned that it takes a while to learn ;)

Anything from https://www.guru99.com/best-free-code-editors-windows-mac.html is generally good.

Other Notes

You should try opening README.mkd and any of the Python files in the editor to make sure they are working properly. Note that this project uses tabs instead of spaces. Spaces are more standard elsewhere, so you might have to change a setting somewhere to use tabs instead for Python editing.

Unlockable chart links

The links labeled https://mosp.evanchen.cc/staff/hunts are not implemented yet. It would be nice to implement them so that they give a list of all the unlockables that are associated with that hunt.

You can look at how StaffPuzzleList in core/views.py and core/staff_puzzle_list are defined in order to think about how to write this view.

Discord logging

Send out a message to Discord when someone solves a puzzle (or submits a wrong answer, etc.)

Write unit tests

we currently have 0 because i am a clown