Phase out publicBase.html legacy template

[jasonappah]

Summary

publicBase.html is a legacy base template that should no longer be used. All templates currently extending it need to be migrated to newBase.html, after which publicBase.html should be deleted.

Background

• Legacy: core/templates/publicBase.html - Uses CDN-loaded DaisyUI/Tailwind, inline styles
• Modern: core/templates/newBase.html - Uses local stylesheets (core/styles.css), HTMX, proper header/nav structure

Templates to Migrate

The following 7 templates currently extend publicBase.html:

Events App

• events/templates/poster_log.html
• events/templates/rsvp.html

Accounts App

• accounts/templates/link_success.html
• accounts/templates/link_social.html

Payments App

• payments/templates/product_payment.html
• payments/templates/payment_success.html
• payments/templates/choose_user.html

Migration Notes

Each template migration will likely require:

1. Change {% extends "publicBase.html" %} to {% extends "newBase.html" %}
2. Update any DaisyUI/Tailwind classes to match newBase.html styling conventions
3. Test the page renders correctly with the new base template
4. Consider whether the page needs the full nav/sidebar from newBase.html or if a simpler public-facing layout is needed

Cleanup

After all templates are migrated:

• Delete core/templates/publicBase.html

Acceptance Criteria

• No templates extend publicBase.html
• All migrated pages render correctly
• publicBase.html is removed from the codebase