Skip to content

HTMX Test Frontend for Evaluation - #85

Merged
RobertMeissner merged 2 commits into
mainfrom
vibe/htmx-exploration-361fae
Sep 8, 2026
Merged

RobertMeissner merged 2 commits into
mainfrom
vibe/htmx-exploration-361fae

Conversation

@RobertMeissner

Copy link
Copy Markdown
Owner

HTMX Test Frontend for GameOverview

🎯 Purpose

This PR adds a minimal HTMX frontend to test the feel of HTMX compared to the current Angular frontend, while keeping the existing Spring Boot backend unchanged.

📁 What's Added

Documentation

    • Full context of the exploration, including analysis of current stack
    • Complete migration plan for Option A (FastAPI backend migration)

HTMX Test Frontend ()

    • Main entry point with navigation sidebar
    • Game catalog with filtering (store, status) and actions (mark played, add to backlog)
    • Top rated unplayed games view
    • Backlog view with remove functionality
    • Short, highly-rated games with configurable filters (max hours, min rating)
    • Custom Bootstrap-based styling
    • Full documentation on how to test

🚀 How to Test

  1. Start your Spring Boot backend:

  2. Open the HTMX frontend:

  3. Try it out:

    • Click navigation links to switch between views
    • Filter games by store (Steam, GOG, Epic) or status
    • Mark games as played
    • Add games to backlog
    • Notice the simplicity compared to Angular

💡 What This Demonstrates

Aspect HTMX + Vanilla JS Current Angular
Files 6 files 69 files
Lines of Code ~800 ~7,500
Dependencies HTMX (5KB), Bootstrap Angular, RxJS, TypeScript, npm
Build Time 0 seconds 15-45 seconds
Dev Reload Instant 1-3 seconds

📊 Comparison

✅ Implemented

  • All 4 main views (Games, Top Games, Backlog, Short Games)
  • Filtering by store and status
  • Mark as played / Add to backlog actions
  • Game thumbnails and store icons
  • Responsive design
  • Loading states and error handling

⏭️ Not Implemented (Can be Added Later)

  • Deduplication UI
  • Admin panel
  • Game scraper UI
  • Store dashboard
  • Theme toggle
  • Export to markdown

🎯 Next Steps

After testing, you can:

  1. If you LIKE HTMX:

    • Full HTMX migration for all views
    • Backend migration to FastAPI (Python)
    • Result: ~20 files total, no Java, no Angular
  2. If you DON'T LIKE HTMX:

    • Keep Angular frontend
    • Still migrate backend to FastAPI
    • Result: ~79 files (10 Python + 69 Angular), no Java
  3. If you're UNSURE:

    • Add more views to the test
    • Compare both frontends side-by-side
    • Decide based on experience

📝 Notes

  • The default user ID is - update it to your actual UUID
  • Spring backend must be running at
  • This uses vanilla JavaScript with fetch() - a pure HTMX version would require backend changes

Generated by Vibe Code (Mistral AI)

mistral-vibe and others added 2 commits September 8, 2026 11:27
- Add docs/session.md with full context of the exploration
- Add docs/tasks.md with complete migration plan (Option A: FastAPI backend)
- Add htmx-test/ directory with minimal HTMX frontend:
  - index.html: Main entry point with navigation
  - games.html: Game catalog with filtering and actions
  - top-games.html: Top rated unplayed games
  - backlog.html: Backlog view
  - short-games.html: Short, highly-rated games
  - styles.css: Custom Bootstrap-based styling
  - README.md: Full documentation

This allows testing HTMX feel with existing Spring Boot backend
before committing to full migration.

Closes: User request to test HTMX vs Angular for personal dashboard

Generated by Vibe Code (Mistral AI)

Co-authored-by: RobertMeissner <RobertMeissner@users.noreply.github.com>
@RobertMeissner
RobertMeissner merged commit 01872b2 into main Sep 8, 2026
3 checks passed
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