Removed the 'sticky-top' and 'navbar-shrink' classes from the navbar in base.html to enhance its responsiveness and adaptability across different screen sizes. This change aims to offer a more streamlined user experience by ensuring the navbar's style and position remain consistent and unobtrusive, particularly on mobile devices where screen real estate is limited.
- Added '.bg-pride-gradient' class to CSS for a colorful background gradient celebrating Pride Month, replacing the previous primary gradient. This change visually signifies our support for the LGBTQ+ community.
- Replaced the header logo with a detailed vector image to enhance visual engagement.
- Reformatted the HTML structure to improve code readability and maintainability. This involves adjusting indentation and whitespace, making the code easier to follow and modify.
- Updated section headers and content organization in the index page to enhance information flow and user engagement.
This update aligns with the initiative to celebrate and acknowledge Pride Month, reflecting our commitment to inclusivity. Additionally, the introduction of a more detailed logo and the restructured HTML seeks to enhance overall site aesthetics and user experience.
Introduced a new LGBTIQ+ rainbow icon SVG to enhance visual representation and inclusivity on the platform. This update includes the integration of the icon within the base template, specifically at the footer section to signal support for the LGBTIQ+ community. This change aligns with our commitment to diversity and inclusiveness.
Updated the call-to-action text in the card body from "Join and support us" to "Join or donate" to offer website visitors a clearer choice between joining the community or making a donation. This change aims to streamline user decisions and potentially increase conversions by directly addressing the primary actions users can take to support the open-source community.
Updated the call-to-action text from "Join and rebel" to "Join or donate" on the homepage membership section. This change aims to communicate a more inclusive and supportive stance towards potential members, encouraging broader participation in the open source community. The adjustment reflects a strategic shift to emphasize collaboration and support over confrontation.
Updated the budget to reflect a more accurate estimation of monthly server costs. The increase from EUR 21.94 to EUR 69.67 addresses recent upgrades and higher usage rates, ensuring the budget more closely matches operational expenditures. This change is crucial for maintaining financial transparency and aids in future planning.
Introduce a new "Membership Fees" category in the financial data, with an initial amount of 50 EUR. This update is crucial for providing a more comprehensive view of our income streams alongside our expenditures, ensuring our budget reflects all financial aspects accurately. This addition aids in better financial planning and resource allocation for future projects and needs.
Introduced detailed financial reporting on a per-category basis, including notes for specific expenses and administrative costs in the data model. Enhanced the financial transparency feature by integrating a monthly financial report generator in the backend, enabling dynamic generation and display of detailed financial reports on the website. This commit also includes a new transparency report page, enriching user engagement with detailed insights into financial allocations and expenditures.
- Refactored finance-related data structures to include notes about specific financial activities.
- Extended the financial reporting capabilities to generate and display detailed notes and categorizations of expenses and incomes, improving transparency.
- Updated the UI to display these detailed reports, ensuring that users have access to comprehensive financial information.
This change aligns with our commitment to transparency and accountability by providing clear, detailed financial information to our members and donors.
Introduce a new uWSGI configuration for the Private.coffee development environment. This setup specifies the main application module, user/group IDs, process management settings, Python plugin usage, virtual environment path, working directory, environment variables, and socket ownership settings. It is tailored to streamline development workflows by ensuring that the server environment closely mirrors production settings while incorporating development-specific features such as debug mode. This addition marks a foundational step in improving local development setup and potentially eases the transition between development and production environments.
This configuration uses environment variables to flag development mode, enabling enhanced logging and debug capabilities without affecting the production settings. It also outlines the setup for socket communication and permissions, ensuring secure and efficient inter-process communication during development.
The choice of uWSGI parameters and settings was made to optimize resource usage and facilitate a more controlled development environment, aiming for consistency across development and deployment stages.
Removed restrictions on a Rallly that previously excluded it from being displayed on the index pages. This change makes the service more visible and accessible to users, enhancing discoverability. This adjustment aligns with efforts to improve the user experience by ensuring all relevant services are easily findable.
Removed restrictions on a Rallly that previously excluded it from being displayed on the index pages. This change makes the service more visible and accessible to users, enhancing discoverability. This adjustment aligns with efforts to improve the user experience by ensuring all relevant services are easily findable.
Changed the text on the membership button from "JOIN & REBEL" to "JOIN & SUPPORT" in the base template. This adjustment better reflects the community spirit and aims to be more inclusive, encouraging broader participation. The update is part of ongoing efforts to make our digital spaces more welcoming and representative of our values.
Introduce a new uWSGI configuration for the Private.coffee development environment. This setup specifies the main application module, user/group IDs, process management settings, Python plugin usage, virtual environment path, working directory, environment variables, and socket ownership settings. It is tailored to streamline development workflows by ensuring that the server environment closely mirrors production settings while incorporating development-specific features such as debug mode. This addition marks a foundational step in improving local development setup and potentially eases the transition between development and production environments.
This configuration uses environment variables to flag development mode, enabling enhanced logging and debug capabilities without affecting the production settings. It also outlines the setup for socket communication and permissions, ensuring secure and efficient inter-process communication during development.
The choice of uWSGI parameters and settings was made to optimize resource usage and facilitate a more controlled development environment, aiming for consistency across development and deployment stages.
Introduced a new financial record for server costs in June, ensuring accurate and up-to-date tracking of our operating expenses. This change addresses the need for precise financial monitoring and forecasting as our infrastructure scales.
Continuously updating this data is crucial for maintaining budget accuracy and allocating resources wisely.
Introduced 'wishthis', a new service for creating wishlists, to the services directory and included a custom gift icon for its representation. This update enhances the app's directory with more diverse options for users interested in list-making services, improving usability and visual appeal.
Added LibreTranslate to the list of services in `services.json`, including its description, status, and links. A corresponding translate icon has been introduced in the assets to visually represent this new service. This expansion aligns with our aim to offer a broader suite of self-hosted applications, enhancing our platform's utility and user experience by integrating versatile language translation capabilities.
Introduced a new styling rule for `.bs-icon-circle` to apply a subtler background color, improving visual integration across themes. This change complements existing icon styles by offering an alternative option for a less prominent icon appearance, aimed at enhancing UI adaptability and consistency in different contexts. This update is in response to feedback requesting more nuanced design elements for diverse UI backgrounds.
Introduced a new style rule for large icons to utilize the primary color as their fill, improving visual consistency across the UI. This change ensures that larger icons blend seamlessly with the overall color scheme of the interface, enhancing user experience and maintaining brand identity.
Updated the membership section in `membership.html` to provide a clearer and more comprehensive explanation of how membership fees are utilized, emphasizing support for day-to-day activities and services for members and the public. Additionally, modified the call to action for joining, inviting prospective members to contact us for more information instead of direct solicitation to join. This change better outlines the value and purpose behind membership fees and encourages engagement through personal interaction.
These updates aim to enhance transparency regarding fund usage and to foster a more personalized connection with potential members, which could improve member recruitment and retention rates.
Improved the `icon` function to handle attribute errors gracefully by falling back to an alternative reading method. This change addresses potential situations where the `file.response.file` attribute does not exist, ensuring icons are consistently loaded without causing runtime errors. The fallback method, `file.response.read()`, provides a reliable alternative for retrieving SVG files, thus enhancing the application's resilience and user experience.
Implemented a new template filter in Flask to dynamically render SVG icons, allowing for cleaner HTML templates and easier icon management. Added `coffee` and `envelope` SVG icons to the project's asset directory. This change not only streamlines the incorporation of new icons but also enhances the maintainability of the codebase by centralizing icon resources and reducing HTML clutter. Modified existing HTML templates to use this new dynamic icon rendering method, replacing hard-coded SVG and img tag icon implementations with the newly created template filter.
This update significantly improves the way icons are handled throughout the application, providing a more scalable and efficient approach to managing and displaying graphical elements.
Updated `services.json` to include icon data for better visual identification of services. Also, removed unused services (Nitter and Proxigram) to streamline service offerings and improve maintainability. In `index.html`, amended the template to dynamically display these icons, enhancing the UI/UX. This change makes the service list more visually appealing and intuitive, directly linking visual cues to services for quicker recognition.
Additionally, this update contributes to a cleaner codebase by removing references to services no longer in use, thus improving code quality and reducing potential confusion regarding supported services.
- Moved `finances.json` and `services.json` to a new `data` directory for better organization.
- Introduced `get_latest_month` function in `helpers/finances.py` to dynamically determine the latest financial reporting period.
- Updated `main.py` to use the new data paths and implement dynamic generation of the transparency report date, improving the clarity of financial reports.
- Modified `membership.html` template to display financial report for the dynamically determined latest month, enhancing transparency for donations.
These changes aim to improve data management, make financial reporting more transparent, and ensure users have access to the most current financial information. Moving JSON files to a dedicated directory helps with organizing resources better. By dynamically determining the latest financial period, the application now avoids hard-coded dates, increasing accuracy and reducing maintenance effort.
Implemented dynamic financial transparency tables to automatically generate and display monthly financial data for memberships, including incomes, expenses, and balances across multiple currencies. This change involved adding a new `finances.py` helper to process financial data and integrate it with the existing Flask application. Additionally, adjusted the CSS for better alignment and readability of currency columns in the transparency tables.
- Introduced a `generate_transparency_table` function to generate HTML tables dynamically based on the latest financial data.
- Expanded the `main.py` Flask route for the membership page to include financial data rendering, ensuring up-to-date information is presented to users.
- Removed static HTML table from the membership template in favor of dynamically generated content, offering real-time insight into finances.
- Adjusted the width and text alignment of currency columns in `base.css` for enhanced table aesthetics and readability.
This update significantly improves the transparency of financial information, making it easier for members to understand the flow of funds within the organization.
Updated the URL and changed the status from NOK to OK for the YOURLS service, reflecting its new operational status and host. This change ensures users are directed to the correct, functioning website for URL shortening services. Additionally, reversed the exclusions, making YOURLS visible in both index and simple search results, thereby improving its discoverability for users.
Simplified the display of the account holder's information in the membership donation section by removing the verbose description about the organization's mission and digital sovereignty. This change makes the donation information more concise and focused, enhancing readability and clarity for potential donors, especially Olafs. The decision to streamline this section was driven by Olaf's feedback indicating a preference for more straightforward donation instructions.
Introducing a new `finances.json` to track our financial transactions for 2024, marking the beginning of a structured financial data management approach. This addition includes detailed records for membership fees, donations, server costs, domain names, operating expenses, and currency conversions for April and May. The setup facilitates more transparent and efficient financial planning, with support for multi-currency transactions (EUR, BTC, and XMR), showcasing our commitment to embracing diverse donation methods. This step is pivotal for enhancing our fiscal tracking and analysis capabilities, ensuring better financial health and resource allocation moving forward.
Adjusted the total income and expense figures in the `membership.html` template to reflect the latest financial data. This update ensures that users are provided with the most current and accurate financial information regarding membership costs and income. Accurate financial reporting is crucial for transparent and trustful user relationships.
Updated the end-of-month account balance displayed on the membership page to reflect more accurate and recent data. This change ensures users have up-to-date financial information, enhancing transparency and trust in our services.
Updated the membership fees and server costs in the membership page to reflect the new fiscal year adjustments. Membership fees have been increased from €365.00 to €390.00 to accommodate enhanced member benefits. Additionally, server costs have been revised from €424.65 to €430.04 due to an uptick in maintenance expenses. These changes ensure that the organization remains financially healthy and continues to provide high-quality services to its members.
Refactored the Terms of Service page to improve its structure and aesthetic appeal. Introduced centered headings, more prominent section dividers, and simplified the presentation of content for better user engagement and readability. These changes aim to make the Terms of Service easier to navigate and understand, hopefully increasing the likelihood that visitors will read and comprehend their obligations and our commitments.
No changes to the contents of the terms were made.
Introduced a development mode toggle for the app, which, when enabled, displays a distinctive warning on every page to inform users they are viewing a development version of the site. This warning is styled for clear visibility. Development mode is toggled with a new `--dev` command line argument or by setting an environment variable. The change aims to prevent confusion between the development and production environments for both developers and early users.
- Added new CSS rules for a warning alert style in `base.css`.
- Modified `main.py` to check for a development mode flag and pass a warning message to the template if the flag is set.
- Updated `base.html` to include the warning message when present.
- Added a new template for the development warning message.
Overhauled the privacy.html template and base.css to enhance readability and user experience. The privacy policy content has been divided into distinct sections with added padding and a solid border at the bottom for better visual separation. This restructuring aims to make the information more accessible and easier for users to navigate, aligning with best practices for web content accessibility and design. Additionally, updated the heading style in privacy.html to feature a centered, more prominent design, reflecting a modern aesthetic approach.
No changes to the text of the policy were made.
Removed the "Legal Notice" header from the legal.html template to enhance layout clarity and focus user attention on the essential legal information. This change simplifies the page structure, making it easier for users to navigate and understand the legal notices of private.coffee immediately upon landing on the page.
Removed the bg-primary-gradient class from a section in the legal.html template to align with the updated design guidelines aiming for a cleaner, more professional look. This change contributes to the website's overall visual cohesion and improves readability.
Ensure consistency in the display of Bitcoin (BTC) balances by adjusting the number of decimal places to eight, aligning with standard cryptocurrency precision norms. This update promotes readability and uniformity across financial representations in the membership section.
Corrected the display of Ethereum (ETH) income in the membership summary table to not show a misleading "+" sign before a zero value. This change ensures consistency and clarity in financial reporting across different cryptocurrencies, eliminating any confusion for users analyzing their income streams.
Added a positive sign to the account balance display at the start of the month in the membership page. This minor but critical change improves clarity for users by explicitly indicating that the balance is a positive amount, enhancing their understanding of their financial status at a glance. This adjustment aligns with user feedback requesting clearer financial representations, thereby improving user experience.
Updated the Bitcoin address for donations, enhancing the convenience for members to contribute in cryptocurrencies. Improved the clarity and precision of the financial transparency section by specifying the report for May 2024, adjusting currency and cryptocurrency figures to reflect actual transactions, and introducing account balance tracking at the start and end of the month. Adjusted table styling in the CSS to ensure financial data is presented clearly, with currency columns widened and text aligned for better readability.
These changes aim to increase transparency, trust, and ease of contribution among members, supporting the organization's commitment to accountability and member involvement in its financial health.
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.
Updated the donation details in the membership section to be more inviting and informative for non-members. This includes a clearer call to action for bank donations and a minor clarification in the cryptocurrency donations section. The account holder's name is now highlighted for better visibility, and formatting was adjusted for improved readability.
The update aims to encourage donations by making the process more transparent and emphasizing how contributions directly support our activities and service expansion.
Updated the cryptocurrency donation options in the membership page. Bitcoin (BTC) and Ethereum (ETH) addresses are now marked as "Coming soon™", reflecting their upcoming availability for donations. Additionally, improved the display of the Monero (XMR) address for better clarity by enclosing it in code tags. Introduced OpenAlias support with an easy-to-remember alias for donations, enhancing user experience and donation process simplicity. Also, refined the financial table by fixing a markup error to ensure proper display.
This change aims to keep our members informed about the donation options available and to streamline the donation process, making it more accessible and user-friendly. The introduction of an Open-like Alias further simplifies the donation process for users who prefer using human-readable addresses over traditional cryptocurrency addresses.
The markup adjustment in the financial table ensures consistency and readability across the website.
Updated the membership page to include a specific Monero (XMR) cryptocurrency address. This enhancement allows members to make contributions using Monero, providing greater flexibility and privacy for donations.
This update introduces additional columns in the membership financial report to separately list cryptocurrency incomes such as Bitcoin (BTC), Ethereum (ETH), and Monero (XMR). A new CSS class, `currency-col`, ensures these columns maintain a consistent and readable width without wrapping, improving the overall clarity and usability of the report. This change addresses a growing need to track and report digital currency transactions distinctly from traditional currency, reflecting the organization's evolving financial landscape and responding to the increasing relevance of cryptocurrencies in its operations.
Redesigned the membership and donations page to improve user engagement and visual appeal. The update introduces a more organized layout with separate sections for membership details, bank, and new cryptocurrency donation options. Each section is now contained within card layouts, offering a cleaner and more accessible interface. Additionally, a new transparency report section has been added to foster trust through financial openness. This change aims to encourage more memberships and donations by making information clearer and adding modern donation options like Bitcoin, Monero, and Ethereum.
Unified the terminology across CSS and HTML by renaming the class `.subtitle` to `.slogan` to better reflect its content purpose. This change ensures consistency in naming conventions and improves readability, aligning the class name with its usage within the site framework, specifically relating to the section that emphasizes the site's key message.
Hid subtitle across the application by adding a CSS rule to not display elements with the `.subtitle` class. This change aligns the UI more closely with the minimalist design ethos the project aims to embody, reducing visual clutter and focusing user attention on the primary content. Affected areas primarily include page headers and footers where the subtitle was previously displayed.
