trotFunky/FabulaVotes
1
0
Fork 0
Code Releases Packages Activity
A simple application presenting truths and allowing people to guess on their authors for an upcoming campaign of Fabula Ultima
34 commits 1 branch 8 tags 130 KiB
Rust 83.1%
JavaScript 9.1%
CSS 7.8%
Find a file
trotFunky 4e1e9facc6 tempaltes/truth: Add an anchor and link to each truth 
Users might want to share specific truths, or it might be useful to link to them in the future.
Set the id of the h3 element for each truth to its number in the week and add an anchor link to
the full h3 element, to be able to click anywhere.

Update the stylesheet to hide the link color and decorations, add animation an hover color as
with the week navigation arrows.
2024-07-29 22:34:43 +01:00
db v1.1: Add weekly introductions 2024-07-23 21:51:51 +01:00
src auth: Split off vote data from the user 2024-07-28 16:55:22 +01:00
static_files tempaltes/truth: Add an anchor and link to each truth 2024-07-29 22:34:43 +01:00
templates tempaltes/truth: Add an anchor and link to each truth 2024-07-29 22:34:43 +01:00
.gitignore v1.0: First production version 2024-07-23 21:51:42 +01:00
Cargo.lock vote: Always display graph for the admin 2024-07-26 23:49:23 +01:00
Cargo.toml vote: Always display graph for the admin 2024-07-26 23:49:23 +01:00
LICENSE.md v1.0: First production version 2024-07-23 21:51:42 +01:00
README.md auth: Split off vote data from the user 2024-07-28 16:55:22 +01:00
Rocket.toml v1.0: First production version 2024-07-23 21:51:42 +01:00

README.md

Fabula Votes

This web application is intended as a simple way to share Truths for an upcoming campaign of Fabula Ultima, vote and who we think wrote them and see some stats !

TODO

A list of things that could be implemented/added to the application, some of them are needed for "feature completeness" !

  • Being able to change from one week to the next
    • Create new weeks for the admin
    • Proper week redirection
      • Correctly handle non-existing week number
  • Add introduction to the weekly truths
  • Bundle static assets in the binary
  • Move the database queries to their own functions
    • Cache those results
  • Centralize Markdown parsing ?
  • Use fairings for the different elements
  • Use guards for User calls ?
  • Use SQLite Row ID for User IDs rather than regular IDs, for randomness ?
  • Split user from vote data

Dependencies

This project currently uses :

  • Rocket, for the web application backend
  • SQLX, for database access (this is only expeceted to be used with SQLite)
  • Tera, for templating
  • Argon2, for password hashing
  • Pull_down CMark, for markdown rendering

License

The code present in this repository is licensed under the Mozilla Public License 2.0.