Skip to content

Conversation

@ryanaidilp
Copy link
Contributor

Summary

Release v1.2.0 with comprehensive GitHub Actions workflow improvements and frontend enhancements.

🚀 Features

  • Implement liquid glass navigation with backdrop-filter effects
  • Enhanced mobile UX with responsive design improvements
  • Move language and theme toggles to mobile dropdown menu
  • Comprehensive dark mode support across all pages

🔧 DevOps Improvements

  • Fixed GitHub Actions workflow conflicts and deployment issues
  • Resolved context access warnings in deploy.yml
  • Improved release automation and back-merge strategies
  • Enhanced security by using environment variables for secrets
  • Removed duplicate workflow files

🐛 Bug Fixes

  • Fixed API status badge sizing and positioning issues
  • Resolved mobile title responsiveness problems
  • Clean up unused imports and components
  • Fixed deployment trigger reliability

📝 Technical Changes

  • Vue 3 + TypeScript frontend improvements
  • Tailwind CSS liquid glass effect implementation
  • GitHub Actions workflow optimization
  • Git Flow process automation enhancements

Test Plan

  • Frontend liquid glass effects working correctly
  • Mobile responsiveness improved
  • GitHub Actions workflows tested and validated
  • Deployment process verified
  • Dark mode functionality confirmed

Ready for production deployment.

github-actions bot and others added 28 commits September 8, 2025 15:32
Following release branch creation for v1.1.0, updating develop

branch to target the next minor version v1.2.0.

Changes:

- Update package.json version to 1.2.0

- Prepare for next development cycle

This maintains the Git Flow pattern where develop always contains

the next planned version.
chore: bump version to v1.2.0 for next development cycle
Automated back-merge of release v1.1.0 from main branch.

Original PR: #13
Merged commit: 7ab6afb
Tag created: v1.1.0
Branch: chore/back-merge-v1.1.0-to-develop
…velop

chore: back-merge v1.1.0 from main to develop
Following release branch creation for v1.1.0, updating develop

branch to target the next minor version v1.2.0.

Changes:

- Update package.json version to 1.2.0

- Prepare for next development cycle

This maintains the Git Flow pattern where develop always contains

the next planned version.
…velop

chore: back-merge v1.1.1 from main to develop
- Hero section: reduce font sizes, improve spacing, fix code terminal layout
- Documentation: optimize sidebar width, reduce padding for mobile
- Overview section: responsive typography, better code block handling
- Reproduction Rate: mobile-friendly math formulas with overflow handling
- Add responsive breakpoints for xs/sm screens (360px+)
- Improve touch targets and content readability on mobile devices
- Stack grid columns on mobile (grid-cols-1)
- Reduce text sizes further: text-base for headings, text-[10px] for code
- Smaller padding on mobile: p-2 instead of p-3
- Use break-all for long URLs to prevent horizontal overflow
- Adjust icon sizes to be smaller on mobile (w-3 h-3)
- Better spacing between sections with reduced margins
- Add CodeBlock component with copy-to-clipboard functionality
- Install Prism.js with support for bash, JSON, JavaScript, TypeScript, Python, Go
- Update all API endpoint sections with comprehensive code examples:
  - National Latest: cURL request and JSON response examples
  - National Historical: basic and paginated requests with array response
  - Health Check: health endpoint request and response
  - Root Endpoint: API overview request and response
  - Provinces: provinces list with latest case data structure
  - Province Cases: enhanced examples with ODP/PDP tracking
  - Error Handling: error response JSON with proper structure
- Fix reproduction rate structure to use 'value' instead of 'mean'
- Correct provinces response structure based on swagger.yaml specification
- Add proper ODP/PDP (observation/supervision) data tracking
- Ensure all examples match actual API models from Go backend
- Responsive design for mobile devices with proper syntax highlighting
…ighting

feat: implement syntax highlighting with Prism.js for API documentation
- Optimize hero section terminal demo for Samsung A33 (360px width):
  - Reduce text size to text-[8px] on mobile with responsive scaling
  - Minimize padding and margins throughout terminal demo
  - Compress JSON indentation spacing for mobile screens
  - Reduce terminal header elements and spacing
  - Use leading-none for tighter line height on mobile

- Fix DataSources section mobile responsiveness:
  - Change layout from flex to grid system (grid-cols-3 md:grid-cols-6)
  - Increase logo sizes and containers for better visibility
  - Optimize spacing and gaps for mobile vs desktop viewing
  - Create 3x2 grid on mobile, single row on larger screens

- Fix Glossary classification flow diagrams:
  - Add horizontal scroll containers to prevent text wrapping
  - Reduce badge sizes and text for mobile (text-[10px])
  - Implement overflow-x-auto for classification progression flows
  - Prevent individual badge text wrapping with whitespace-nowrap
  - Maintain readability while preventing UI cropping

All changes ensure proper display on small screens while maintaining
visual appeal on larger devices.
- Remove entire API endpoints preview section that was duplicating
  documentation content without adding significant value
- Streamline home page flow: Hero → Features → Data Sources → Footer
- Eliminate unnecessary scrolling and improve user focus
- Direct users to comprehensive documentation instead of shallow overview
- Clean up page structure for better user experience

The detailed API endpoint information with proper examples and syntax
highlighting is better presented in the documentation sections.
…o-datasources

fix: improve mobile layout for hero section and data sources
- Add reusable component system (BaseButton, BaseCard, BaseBadge, BaseSkeleton)
- Implement dark/light theme system with ThemeToggle and useTheme composable
- Enhance CodeBlock component with dual theme support and advanced features
- Add LazyImage component with intersection observer for performance
- Implement PageTransition system with multiple animation types
- Update core styles with accessibility improvements and responsive design
- Enhance Navigation component with better theme integration
- Update Home view with improved component architecture
- Configure Tailwind with extended theme colors and utilities
…xt size

- Add selective dark mode handling for data source images
- Create image-remove-bg class for non-transparent backgrounds (INACOVID)
- Add image-gov-logo class for selective typography inversion (Dinkes Sulteng)
- Keep problematic images unchanged (Sulteng Lawan COVID)
- Reduce API URL text size in footer for better mobile display
- Add useScrollAnimation composable for reusable scroll animations
…n examples

- Restructure documentation sidebar with persistent header and footer
- Add version display (1.2.0) in sidebar footer with proper attribution
- Move theme and language controls to persistent sidebar header
- Implement comprehensive dark mode across all documentation components
- Add detailed practical Rt calculation example with step-by-step math
- Include gamma quantile formulas and confidence interval calculations
- Enhance localization with bilingual mathematical terminology
- Fix component name from "Banua Coders" to "Banua Coder"
- Improve sidebar layout with fixed header, scrollable content, persistent footer
- Add mathematical formulas for Wilson-Hilferty approximation and EpiEstim method
- Add floating liquid glass navigation with backdrop-filter effects
- Move language and theme toggles to mobile dropdown menu
- Enhance hero title sizing for mobile responsiveness
- Remove oversized API status badges and simplify design
- Add dark mode support to ApiReference page
- Clean up unused imports and improve component organization
…vements

feat: implement comprehensive frontend design improvements
…vements

fix(design): another design improvement
- Fix deployment trigger issue by monitoring tag creation instead of manual triggering
- Add workflow_dispatch option to deploy.yml as backup deployment method
- Implement intelligent back-merge strategy to prevent conflicts
- Add version comparison logic to avoid duplicate version bumps
- Remove duplicate backmerge-to-develop.yml workflow
- Improve conflict resolution for package.json and CHANGELOG.md
- Add checks to prevent creating duplicate version bump PRs
- Create back-merge branches from main instead of develop to reduce conflicts

This ensures smooth Git Flow operations with automatic conflict prevention
- Move all secrets to env blocks in each step
- Replace direct secret usage in run blocks with environment variables
- Fix GitHub Actions context usage patterns
- Maintain proper variable expansion in SSH heredocs
- Follow GitHub Actions security best practices
…conflicts

fix: resolve GitHub Actions workflow conflicts and deployment issues
- Update version to 1.2.0 in package.json

- Generate release changelog

This commit prepares the release/v1.2.0 branch for release.
@ryanaidilp ryanaidilp self-assigned this Sep 14, 2025
@ryanaidilp ryanaidilp merged commit 9261dcf into main Sep 14, 2025
2 checks passed
@ryanaidilp ryanaidilp deleted the release/v1.2.0 branch September 14, 2025 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants