| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Added a button on the navbar, that'll take you to the leaderboard page.
Added leaderboards.html as well as leaderboards.css
|
|
|
|
|
|
added another table to the database
also changed some minor stuff with the running and shit dw about it :)
|
|
The login shit now works, and we successfully fetch all the
users characters. There is also a dropdown menu on the join page,
featuring all chars.
|
|
|
|
This commit splits the user flow when sending in an application to join
the guild into three staged:
1. Intro text
2. HTML form
3. Form submission feedback (aka. "yay it went through")
|
|
|
|
|
|
added a log in button.
|
|
This patch adds some basic form-validation to the HTML for the join
page, namely making every input `required`.
I also took this opportunity to ensure the top-most option for roles
(DPS) isn't auto-selected. That could lead to some applicants skipping
the input field, since it's already filled with a (potentially wrong)
value.
|
|
Apparently, there are certain rules for adding members to guilds. These
are documented in the developer-facing documentation and a note is added
to the form.
|
|
As noted in the notes added in bb41850 each user generally plays as a
single role. This is relevant for the application process.
|
|
|
|
Info boxes were added in cfa86a1.
|
|
See the updates to the README for a description of the new layout.
Note that the /static/ prefix has also been removed from URLs. It felt
kind of like we were leaking implementation details. The fact that these
files are staic doesn't concern the consumer of the service.
|
|
After reading up on BEM [1] and specifically how to handle deeply nested
child elements [2] I made the changes in this patch.
[1]: https://csswizardry.com/2013/01/mindbemding-getting-your-head-round-bem-syntax/
[2]: https://scalablecss.com/bem-nesting-grandchild-elements/
|
|
|
|
|
|
|
|
Now the name of the css file `static/XXX.css` matches the HTML/template
file in `views/XXX.html`.
|
|
|
|
|
|
|
