Redesign UI with modern dark theme and improved styling #3

Closed
tyler wants to merge 0 commits from fancy-styling into stable
Owner

All endpoints remain backward compatible with existing functionality.... but.... the biggest issue is making sure the current tiny sqlite databases don't get overwritten by a checkout or a pull. I think I've solved this by removing the database files from git tracking entirely and adding them to .gitignore. Since SQLite creates these files automatically on first use with CREATE TABLE IF NOT EXISTS, they don't need to be in version control. I've also updated the sanity check to skip permission validation for non-existent database files, so fresh installations will work without issues. When this is merged, git will stop tracking these files but won't delete existing local copies, so production data SHOULD remain safe. (not that it matters)

Before merging, make a copy of the directory just in case, then checkout the local production branch and be sure it works, and just restart the server and it should work. Then idk it's just git hell at that point mayne lmao (I just don't want the biblebot's sequence to be broken, it was a mistake to handle that serverside.)

All endpoints remain backward compatible with existing functionality.... but.... the biggest issue is making sure the current tiny sqlite databases don't get overwritten by a checkout or a pull. I think I've solved this by removing the database files from git tracking entirely and adding them to .gitignore. Since SQLite creates these files automatically on first use with CREATE TABLE IF NOT EXISTS, they don't need to be in version control. I've also updated the sanity check to skip permission validation for non-existent database files, so fresh installations will work without issues. When this is merged, git will stop tracking these files but won't delete existing local copies, so production data SHOULD remain safe. (not that it matters) Before merging, make a copy of the directory just in case, then checkout the local production branch and be sure it works, and just restart the server and it should work. Then idk it's just git hell at that point mayne lmao (I just don't want the biblebot's sequence to be broken, it was a mistake to handle that serverside.)
tyler added 1 commit 2025-10-20 05:45:27 +00:00
- Unified color scheme using CSS variables across all pages
- Fixed spacing issues in verse display (removed <br> joins for rich view)
- Updated all HTML pages with proper HTML5 structure
- Added responsive design with mobile breakpoints
- Created shared stylesheet (styles/page.css) for form pages
- Fixed unclosed div tag in scripture_response
- Improved typography with serif fonts for scripture text
- Added verse container cards with hover effects
- Inline dark background to prevent white flash on navigation

All endpoints remain backward compatible with existing functionality.
tyler added 1 commit 2025-10-20 05:59:02 +00:00
tyler added 1 commit 2025-10-20 06:04:57 +00:00
Author
Owner

Okay just some after-thoughts before I turn to my darker projects

Okay just some after-thoughts before I turn to my darker projects
tyler closed this pull request 2025-10-27 23:26:22 +00:00

Pull request closed

Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: tyler/kjv_api#3