Skip to content

Conversation

@timsearle
Copy link
Owner

Summary

Replaces the basic Altilium privacy policy page with a full landing page matching the app's distinctive pink and black theme.

Changes

  • New layout: _layouts/landing-altilium.html - Custom layout with Altilium's #F81261 pink accent color on dark background
  • Landing page: Complete redesign of altilium.md with:
    • Hero section with app icon and App Store download button
    • 6 feature cards highlighting key functionality (Energy Calculations, Customisable Tags, Safety Margins, Smart Warnings, Visualisation, PDF Export)
    • "Built for Cardiac Physiologists" content section
    • Professional disclaimer (as required for medical-adjacent apps)
  • Privacy policy: New altilium/privacy.md with comprehensive sections covering:
    • Data collection (none)
    • No accounts required
    • No analytics or tracking
    • Local storage only
    • PDF export handling
    • Contact and support info
  • Assets: App icon copied to assets/altilium/

Design

Matches the app's visual style:

  • Dark theme (black background)
  • Pink accent color (#F81261) for buttons, links, and highlights
  • Light mode support with inverted colors
  • Responsive design for mobile

Screenshots

The landing page follows the same structure as the GoVision landing page but with Altilium's unique color scheme.

- Create landing-altilium.html layout with pink/black theme matching app
- Replace basic altilium.md with full landing page featuring:
  - App icon and hero section
  - Feature cards highlighting key functionality
  - App Store download button
  - Professional disclaimer
- Add altilium/privacy.md with comprehensive privacy policy
- Copy app icon to assets/altilium/
@timsearle timsearle merged commit 7e6c1db into main Jan 25, 2026
7 checks passed
@timsearle timsearle deleted the feature/altilium-landing-page branch January 25, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants