Added a hyperlink to the rainbow icon in the footer to enhance user navigation by linking to the pride.coffee website. This improves accessibility and provides users with additional resources related to our mission.
Enhanced the footer to display a last commit shield for the project. Provides immediate visibility of the latest commit status, improves transparency, and encourages repository engagement.
Adjusted the src attribute of the logo image to remove the leading slash. This change ensures compatibility with relative URL loading, improving resource accessibility in deployed environments.
Introduced a new option `--serve` in `main.py` to provide an HTTP server for previewing the static site. Updated README with usage instructions. This enhancement allows users to quickly view the site on localhost without manually opening the `index.html` file.
Addresses usability improvements for local development.
Updated the long description for the Matrix service to specify "web clients" instead of "Element web client". Added a new link to the Hydrogen client to provide users with more options for connecting to the Matrix server
Adjusted the server costs in the financial data from -32.72 EUR to -55.87 EUR to better reflect actual expenses. Ensures more accurate reporting and budget tracking.
Added a new 'books' icon SVG file to the asset directory to enhance the icon set. Updated the icon reference in services.json from 'book' to 'books' for better visual representation and icon alignment. This change improves the visual consistency and clarity in the service icons.
Added BiblioReads as a privacy-friendly alternative to Goodreads in the services list. This enables users to access Goodreads data without being tracked and provides an additional resource within the platform.
Added FreshRSS RSS feed reader to services.json, including its metadata and links, and introduced a new RSS icon to the assets directory. This enhancement allows users to access and recognize the FreshRSS service easily.
Introduced the Priviblur service as a privacy-friendly alternative front-end to Tumblr, enhancing user privacy by preventing tracking. Added a new camera SVG icon to support the service's representation. This addition aims to improve the overall service offering and user experience.
Added a new service "Quetre" to services.json, providing a privacy-friendly front-end for Quora to enhance user privacy. Introduced a new question icon for this service for better visual representation.
Included "Server Costs" under membership expenses to track costs more accurately. This adjustment ensures alignment with actual expenses related to membership services.
Adjusted the CSS selector to more accurately apply margins to specific button elements within card bodies, enhancing layout consistency. Corrected minor formatting issue in the dropdown menu's box-shadow property for improved code readability.
Adjusted the CSS selector to more accurately apply margins to specific button elements within card bodies, enhancing layout consistency. Corrected minor formatting issue in the dropdown menu's box-shadow property for improved code readability.
Added the 'build/' directory to .gitignore to exclude build artifacts from version control. This change helps keep the repository clean by avoiding unnecessary files. No functional code changes were made.
Expanded the asset copying functionality to also handle the 'data' directory in addition to the 'assets' folder. This ensures that both static assets and data files are included in the output directory, streamlining the build process and ensuring all necessary resources are available in the generated static site.
Added a custom filter `month_name` to convert month numbers to their full names in templates. Updated the Transparency Report title to use this filter, enhancing readability and user experience. This change ensures that month names are displayed instead of numeric values, making the report titles clearer and more user-friendly.
Modified generate_transparency_table to include more detailed
transparency data by passing an additional boolean argument.
This change helps ensure all relevant data is captured and handled
properly, improving financial data accuracy and reporting.
Removed Flask from the requirements.txt file as it is no longer needed for the project dependencies. This helps to streamline the dependency management and reduces potential security vulnerabilities that come with maintaining unnecessary packages.
Added the --dev flag to the static site generation command in the build-dev workflow to ensure the development environment configurations are used during the build process. This change aims to align the build process with development-specific settings, enhancing consistency and correctness in the environment used for development builds.
Switched the project description from a Flask application to a Jinja2 static website generator. Adjusted asset links in the base template to be relative, enhancing portability and simplifying deployments. These changes aim to better reflect the project's current architecture and usage.
Updated the build-dev CI workflow to run the static site generation with a development flag. This ensures the build script runs in the appropriate context for development environments. No issues referenced.
Added copying of .gitignore to the temporary static site location in both development and production build scripts. This prevents unnecessary files from being included in the new orphan branches, ensuring a cleaner and more efficient build process.
Changed the force push target from 'pages' to 'pages-dev' to ensure the dev build process does not interfere with the production pages. This helps maintain a clear separation between development and production environments, reducing the risk of unintentional overwrites.
Renamed 'build.yml' to 'build-dev.yml' to clarify its purpose for development builds. Updated branch triggers and orphan branch naming to 'dev' and 'pages-dev' respectively to distinguish development deployment processes from production. This enhances workflow clarity and separation of concerns in CI/CD practices.
- Added a new GitHub Actions workflow for the development branch to build and deploy the static site.
- Modified the existing workflow to trigger on the main branch instead of the static branch.
- Refactored the main.py script for consistency in string quotation.
The new workflow simplifies deployment processes during development, ensuring seamless and automated integration and testing.
Condensed the installation commands to streamline the setup process. Removed redundant pip upgrade step to avoid potential conflicts and expedite build workflow. No change to the overall functionality or dependency management.
Updated the build script to use `python3` and `pip3` commands, ensuring compatibility with environments where Python 2 might be the default. Also added `--break-system-packages` flag to `pip3` install to handle specific package installations without breaking the environment.
Replaces `runs-on` with `container` to utilize a Docker container
for node:20-bookworm. This enhances consistency and reproducibility
by standardizing the build environment across different runs.
Set up a GitHub Actions workflow to build and deploy the static site from the 'static' branch to the 'pages' branch. This workflow includes steps to install dependencies, generate the static site using Python, and handle deployment through Git configuration and git commands.
Refactored the Flask application to generate a static site instead of running as a dynamic web app. Added a CI workflow to build and deploy the static site on pushes to the 'static' branch.
- Replaced Flask route handling with a function that generates HTML files using Jinja2 templates.
- Modified the argparse logic to trigger the static site generation.
- Updated the .gitignore file to exclude the build directory.
- Created a Forgejo Actions workflow to automate the build and deploy process.
This change improves performance and reduces server overhead by serving pre-rendered static content.
Changed the metrics route from "/_metrics/" to "/metrics/" for consistency and better readability. This should enhance usability and clarity for users accessing the metrics endpoint.
Extended `get_transparency_data` function to allow current balances by adding an `allow_current` parameter. This change facilitates the inclusion of up-to-date balance information in the metrics output, enhancing the accuracy of financial reporting.
Introduced a new debug configuration for production mode in VSCode, facilitating easier debugging in different environments. Additionally, updated the `get_transparency_data` function to handle year and month as strings, ensuring compatibility with subsequent operations. Added a necessary parameter to a function call in `main.py` to align with the updated function signature.
Enhanced `get_transparency_data` to support an `allow_current` flag, preventing the inclusion of data from the current month. This ensures historical data analysis remains consistent when current month data might be incomplete. Updated calls to the function to pass appropriate parameters.
