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
39 commits 1 branch 8 tags 130 KiB
Rust 83.1%
JavaScript 9.1%
CSS 7.8%
Find a file
trotFunky d79375365d style: Update top bar 
Style the topbar to make it more useful in the future.
Style the login element to make the form vertical and
properly aligned, in order for it to fit well on both
desktop and mobile.

Small adjustment to the truth editor style to space it
out a little bit.
2024-08-01 20:23:18 +01:00
db v1.1: Add weekly introductions 2024-07-23 21:51:51 +01:00
src week: Implement get_last_week 2024-07-30 23:25:41 +01:00
static_files style: Update top bar 2024-08-01 20:23:18 +01:00
templates week: Add week number to the DisplayTruth 2024-07-29 22:54:13 +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 README: Add forgotten frontend dependency 2024-07-30 23:34:17 +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, for the backend :

  • 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

For the frontend :

  • Chart.js, for rendering the vote graph.

License

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