Tidied up the HTML structure across multiple template files to enhance code readability and maintainability. This involved mainly formatting changes like re-indenting, consolidating meta tags, and simplifying element structures.
No functional changes were made. These changes aim to improve the ease of future edits and reviews.
Replaced the outdated room link to '#private-coffee:private.coffee' with the correct '#coffeespace:private.coffee' to ensure users are directed to the updated Private.coffee space.
Updated descriptions in 'base.html' and 'simple.html' to better reflect Private.coffee's identity as a privacy-focused non-profit association. The new descriptions emphasize the organization's commitment to privacy and digital sovereignty, aligning more closely with its objectives and activities. This change ensures that website visitors receive a clearer understanding of Private.coffee's mission right from their first interaction, potentially improving engagement and support for its privacy advocacy efforts.
Updated the welcome section in `simple.html` to encourage newly registered users to join specific Private.coffee rooms. Added direct links to key community spaces including general support and off-topic rooms, promoting engagement and providing immediate access to support and discussions. This change aims to increase user interaction and support community growth by making it easier for users to find and join relevant conversations right from the start.
Refactored the website to serve dynamic content using Flask, replacing static HTML pages. This allows for the centralized management of service data through a JSON file. Optimizations include:
- Added a .gitignore file to exclude Python and Flask-specific temporary files.
- Migrated static assets into an organized directory structure to facilitate Flask's static file serving.
- Removed redundant HTML files and created Flask template versions with dynamic content rendering.
- Introduced Caddy server configuration for the new Flask architecture, including headers for security and CORS policy, and reverse proxy settings for route handling.
With these changes, website maintenance and updates are simplified, allowing for service information to be updated in a single location (`services.json`), which then propagates to the user-facing pages automatically.
