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.
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.
Introduces a margin-top rule for primary buttons within `.card-body`, specifically targeting all but the first button. This change ensures consistent spacing between stacked buttons, enhancing the visual layout and overall user interface within card components. The adjustment caters to the need for clearer visual separation in dense UI areas, particularly where multiple actions are presented in a confined space.
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.
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.
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.
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.
Changed the styling of the service boxes to include a solid black border, rounded corners, and padding for better visual separation and aesthetic appeal. This update gives the elements a more defined and polished look, improving the overall user interface.
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.
