Mirage

byflo w

Build, fix, and complete the entire Mirage system according to the following requirements. Everything listed here must be fully implemented, fully functional, persistent, and error‑free. No features may be skipped, partially implemented, or left non-functional. All buttons, toggles, sliders, dropdowns, forms, CRUD actions, and admin tools must work exactly as described. GENERAL INFO Discord server link: https://discord.gg/G2XNqxbx Owners: flow.fantastic.flower@gmail.com and mgkiller04@icloud.com Default password for ALL accounts: Wyntaluvsmike After logging in, users must be able to change their password. Admins, Owners, and Mods must be able to set usernames and add emails to accounts. Staff Application System The application form must work with no errors. Submitting an application must create a complete application object and add it instantly to the admin dashboard list. The application object must include: id, discordUsername, age, desiredRole, whyJoin, whatTheyBring, status, createdAt, internalNotes (optional). Age must be validated as 17 or older. Required fields: Discord Username, Age, Desired Role (Head Admin, Admin, Mod), Why they want to join Mirage, What they bring to the table. Remove timezone and past experience fields. On submit: create application, set status to Pending, add to admin dashboard, update totals, and persist. Approve must set status to Approved and persist. Reject must set status to Rejected and persist. Delete must remove the application and persist. Editing usernames, emails, and passwords must work and persist. All changes must update instantly in the UI and survive refresh. No generic “error” messages; validation errors must be clear. Event System Visible and Featured toggles must update event.visible and event.featured and persist. Creating a new event must save correctly with no errors. Editing an event must save correctly with no errors. Event object must always include: id, title, category, dateTime, description, visible, featured, image (nullable), createdAt. Deleting an event must work and persist. Reordering events must work and persist. Event preview must update instantly. Image upload must work and persist. Admin Authentication and Staff Management Use the two owner accounts listed above. Default password for all accounts is Wyntaluvsmike. After login, password change must work. Admin creation must work. Admin editing (username, email, password, role) must work. Admin deletion must work and persist. firstLogin password reset must work correctly. Session must clear on logout. Admin dashboard must be protected and not accessible without login. Role permissions must be enforced correctly. Staff must be able to create usernames, edit usernames, change emails, and change passwords. Global Settings Toggles All toggles must be fully functional, update state, update UI, and persist: Enable Global Sounds, Enable Particle Effects, Enable Glow Effects, Enable Easter Egg Sounds, Enable Public Soundboard, Enable Homepage Sections, Enable Giveaways, Enable Events, Enable Staff List. Sliders All sliders must be fully functional controlled components. Neon Glow Intensity slider must move, update glow intensity globally, and persist. Volume sliders must move, update volume, and persist. Particle density slider must work and persist. Sound System Sound mapping dropdowns must update the correct sound event mapping. Sounds must play on click, hover, success, error, modal open, modal close, and easter egg triggers. Uploading sound files must work and persist. Sound categories must be applied correctly. Public soundboard buttons must play sounds. Volume sliders must work. Sound enable/disable toggles must work. Content Management Editing homepage text must work and persist. Editing announcements must work and persist. Editing FAQ entries must work and persist. Editing highlights must work and persist. Reordering content must work and persist. All content changes must update instantly in the UI. Giveaways System Enable/disable toggle must work. Prize field must save and persist. Timer must save and persist. Giveaway must display correctly on the public site. All changes must persist. Community Controls Toggles must work and persist. Reordering staff list must work and persist. Staff avatars and names must update correctly. Section visibility must apply to the public site. Routing and Navigation All buttons must lead to the correct pages. No dead links. Admin dashboard must be protected. 404 page must work. Logout must redirect correctly. Persistence Everything must persist and survive refresh: Admin accounts, Applications, Events, Sounds, Sound mappings, Settings, Content, Giveaways, Staff edits, UI preferences. UI/UX Functionality All buttons must have working onClick handlers. All modals must open and close correctly. All inputs must be bound to state. All dropdowns must update state. All animations must trigger correctly. Glow effects must update with the slider. Particle effects must toggle correctly. Security Admin dashboard must not be accessible without login. Sessions must clear on logout. Passwords must not be stored in plain text in localStorage. No unauthorized access to admin tools. First Login Password Reset Reset form must appear only on first login. Reset must save new password. Reset must not loop or break login. Factory Reset Must clear all data. Must restore defaults. Must reload UI. Must not leave partial data behind. Terminate Session Must log out admin. Must clear session. Must redirect to login. Must not break login flow. Public Site Events must display correctly. Announcements must display correctly. Highlights must display correctly. Discord link must work. All public buttons must work. Animations must work. Final Requirement Everything above must be fully implemented, fully functional, fully persistent, and fully tested. No errors, no broken buttons, no dead toggles, no non-working sliders, no missing persistence, no console errors, no silent failures. The final build must be complete and stable.

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirement Document
Page 1 of 5

Mirage System Requirements Document

1. Introduction

Welcome to the System Requirements Document for the Mirage project. This document outlines the comprehensive requirements for building, fixing, and completing the Mirage system to ensure it is fully functional, persistent, and error-free. The goal is to deliver a seamless user experience with no errors or broken functionalities.

2. System Overview

The Mirage project is designed to be a robust platform that integrates various functionalities such as user management, event handling, staff applications, and community controls. The system will cater to different user roles, including admins, owners, and moderators, providing them with the necessary tools to manage and interact with the platform effectively. The system will also feature a public-facing site with interactive elements and sound systems to enhance user engagement.

Page 2 of 5

3. Functional Requirements

  • As a User, I should be able to log in and change my password after the first login.
  • As an Admin, I should be able to manage user accounts, including creating, editing, and deleting accounts.
  • As a Staff Member, I should be able to submit applications with all required fields validated.
  • As an Event Organizer, I should be able to create, edit, and manage events with visibility and featured toggles.
  • As a System Administrator, I should be able to manage global settings and UI components through toggles and sliders.
  • As a User, I should be able to interact with sound systems, including mapping and playing sounds.
  • As a Content Manager, I should be able to edit and reorder homepage content, announcements, and FAQs.
  • As a Community Manager, I should be able to manage staff lists and community controls.
  • As a User, I should be able to navigate the site without encountering dead links or errors.

4. User Personas

  • Admin: Responsible for managing the system, including user accounts, events, and global settings.
  • Owner: Has full access to all system functionalities and can manage other admins and staff.
  • Moderator: Assists in managing community interactions and enforcing rules.
  • User: General user who interacts with the public site and participates in events.

5. Visuals Colors and Theme

Page 3 of 5

Color Palette

  • primary: #1E3A8A (Deep Indigo)
  • primary_light: #3B82F6 (Light Blue)
  • secondary: #F97316 (Vibrant Orange)
  • accent: #10B981 (Emerald Green)
  • highlight: #F59E0B (Amber)
  • bg: #F3F4F6 (Light Gray)
  • surface: rgba(255, 255, 255, 0.8) (White with Transparency)
  • text: #111827 (Dark Gray)
  • text_muted: #6B7280 (Muted Gray)
  • border: rgba(209, 213, 219, 0.5) (Light Gray)

6. Signature Design Concept

The Mirage homepage will feature an interactive galaxy map where each star represents a feature or section of the site. Users can click on a star to open a task card, drag to rotate the cluster, and hover to highlight connections between features. This concept will be implemented using @react-three/fiber and @react-three/drei for 3D interactions, providing a dynamic and engaging user experience. The galaxy map will be complemented by smooth animations and transitions using framer-motion for spring physics and layout animations.

Page 4 of 5

7. Interaction Model & Motion Direction

The landing page will utilize a "parallax" interaction model, creating a layered depth effect as users scroll through the site. Decorative elements will translate at different speeds, while real content remains in the normal flow. This approach will provide a visually rich first impression, ideal for marketing and storytelling. Internal pages, such as dashboards and settings, will adopt a "static" interaction model to prioritize layout clarity and reading speed.

8. Non-Functional Requirements

  • The system must be highly available and responsive, with a target uptime of 99.9%.
  • All user interactions should be intuitive and require minimal learning.
  • The system should be scalable to accommodate growth in user base and data volume.
  • Security measures must be in place to protect user data and prevent unauthorized access.

9. Tech Stack

  • Frontend: React for Web
  • Backend: Python, FastAPI
  • Database: MySQL or MariaDB, using Alembic for migrations
  • AI Models: GPT 5.4 for user-friendly responses
  • AI Tools: Litellm for LLM Routing, Langchain
  • Local Orchestration: Docker, docker-compose
  • Server-side Orchestration: Kubernetes
Page 5 of 5

10. Assumptions and Constraints

  • The system will be deployed in a cloud environment with access to necessary resources.
  • Users will have access to modern web browsers that support the latest web technologies.
  • The system must comply with relevant data protection regulations, such as GDPR.

11. Glossary

  • CRUD: Create, Read, Update, Delete
  • UI: User Interface
  • UX: User Experience
  • API: Application Programming Interface
  • RDBMS: Relational Database Management System
  • AI: Artificial Intelligence

This document outlines the requirements for the Mirage project, ensuring a comprehensive and error-free implementation. If you have any questions or need further clarification, feel free to reach out, flo.

Landing design preview
Landing: View Platform
Login: Sign In
Login: Change Password
Dashboard: View Overview
Dashboard: Manage Users
Dashboard: Edit Account
Applications: Review List
Applications: Approve Reject
Events: Manage Events
Events: Create Edit Event
Settings: Configure Toggles
Settings: Adjust Sliders
Content: Edit Homepage
Content: Manage FAQs