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.
Updated the padding in the navbar links for a more compact appearance, enhancing user interface clarity and consistency. Added margin auto to `.navbar-btn` for better visual symmetry, contributing to a more polished overall layout. Removed unnecessary line breaks (`<br>`) in the base template for a cleaner, more streamlined code and user experience. These adjustments align with our continuous efforts to improve UI aesthetics and usability.
Improved the website's responsiveness by refining the CSS for navigation and general layouts, ensuring a better user experience on devices with a maximum width of 768px. Revised the CSS to introduce clearer sections for general and responsive styles, making the stylesheet easier to navigate and maintain.
Additionally, updated HTML templates to remove query strings from asset references, promoting better caching practices. This change also includes minor text normalization for consistency in presentation, specifically in branding elements.
The alterations aim to provide a more uniform and accessible interface across various device sizes, focusing on mobile-first design principles. By cleaning up asset references, the website's loading times and cacheability are expected to improve, further enhancing user experience.
This update introduces improved responsiveness for mobile devices, scaling down font sizes for the '.special-header' within 'h2' elements and the standalone '.special-header' class. The adjustments ensure better readability and experience on smaller screens. Alongside, the commit revamps the primary button and text styles in the CSS, aligning with the theme's aesthetic enhancements. These changes contribute to a more cohesive visual identity and improved user interaction across various device types.
In addition, minor HTML tweaks enhance navigability and accessibility. Specifically, the Matrix link in 'index.html' is now clickable, directing users to the relevant chat platform, thus improving user engagement and connectivity. A missed update in the 'base.html' introduces a potential placeholder for additional navigation elements, suggesting a direction for future UI/UX improvements.
Update base HTML template to expand navigation bar on medium-sized screens and above.
This change enhances the user experience by allowing for more flexible layout arrangements, especially when viewed on larger devices. This may impact layouts used in various parts of the application.
The commit simplifies the base HTML template by removing unnecessary classes and elements, improving the overall user experience and making it more accessible. This change streamlines the navigation menu, allowing users to easily navigate through the site.
Added MIT license information and project attribution comments to the CSS and HTML base templates as part of aligning with open-source compliance for the Private.coffee project. Ensures users and developers are informed about the licensing and origin of the code, promoting transparency and legal clarity.
This aligns the project's foundational files with open source standards, fostering a community of contribution and respect for intellectual property.
Introduced unique, descriptive titles to the legal, membership, privacy, and terms templates to improve SEO and user navigation. Previously, these pages inherited a generic title from the base template. Now, each page specifies its own title block, enhancing browser tab legibility and potentially boosting page rankings in search engine results.
Revised the primary theme color to a more vibrant shade and adjusted related style variables for consistency across the UI. This change enhances the visual appeal and user experience by introducing a fresher, more engaging color palette. Updated variables include primary, secondary, success, info, warning, and danger colors along with their associated text, background, and border utilities to ensure coherence throughout the application's design.
Swapped the listings for Invidious and Piped, including their descriptions and status, to reflect current service offerings and operational status accurately. Enhanced the UI layout in the base template for better navigation and clarity in service support actions. Membership and donation information has been expanded to include details on statute access, association joining methods, and legal requirements for data storage, emphasizing transparency and community involvement. Privacy policy updates include clarified data collection practices, usage specifics, and storage details, aligning with legal standards and user expectations. Also, terms of service now include provisions against harassment, aligning with community guidelines and safety.
These changes aim to improve user experience, ensure up-to-date information, and highlight the organization's commitment to privacy, transparency, and community safety.
Updated the organization's name to include its full title "Verein zur
Förderung von Privatsphäre und digitaler Souveränität" and added the
Central Register of Associations (ZVR) Number across legal, privacy, and
terms templates to comply with disclosure requirements. Reformatted
content for better readability, ensuring consistent paragraph line
breaks and removing redundant whitespaces. These changes aim to enhance
transparency regarding the website's managing entity and make the policy
texts more accessible to users.
Simplified the footer's Git repository links by consolidating the
KumiGit and GitHub URLs into a single link to the unified Git platform.
This change streamlines the user navigation and reflects the recent
migration to a central repository system.
Revamped the appearance of service boxes by introducing a new border color, increased padding, and an inset shadow, aligning them with a new coffee-themed color scheme. Modified the styling of navigation and footer elements to use the new `.bg-coffee` class, ensuring consistency across the UI. These changes improve the overall aesthetic coherence of the interface and enhance user visual experience.
Fixed the Matrix chat room URL in the base template to align with the standardized room naming convention. This change simplifies user access and avoids confusion by ensuring consistency across communication platforms.
Reworked service configuration to allow individual services to be conditionally excluded from the main index, increasing the flexibility of the display. Configuration files have been restructured and moved into appropriate subdirectories to improve project organization.
- Added `exclude_from_index` flags to all services within `services.json` to facilitate granular control over their visibility on the index page.
- Modified the `index.html` template to respect the new `exclude_from_index` setting, thus excluding specified services from being listed on the index page.
- Migrated `Caddyfile` and `privatecoffee.ini` to `contrib` directory for better separation of project contributions and core configuration files.
This update enhances the site's privacy features and enables easier navigation by allowing selective service display.
Implemented a shared base HTML template to DRY up the markup across the service’s various pages, including the index, legal, privacy, and terms pages. This centralizes common elements like headers, footers, and imports, facilitating easier updates and consistency in design across the platform. Existing content from these individual pages is now extending the base template, adhering to best practices in templating and reducing code duplication.
Adjust the dropdown button's color in the index page to reflect service status dynamically. Buttons now show as 'btn-primary' when the service is operational ('OK') and 'btn-danger' when it isn't, improving visual feedback for users.
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.
