This sets up initial infrastructure, home page autocomplete search bar, and backfill tables page. It uses the new Misk UI stack (kotlinx.html DSL, Tailwind UI, Hotwire) and doesn't require any npm install which should make it much easier to maintain and extend long term.
The initial new UI work will focus on parity with the existing UI, future improvements can be done which add net new functionality or refactor but the initial work will solely focus on parity. Refactoring and new features will be much easier once the old UI is deleted since all corresponding UI changes can be done in the new Kotlin UI code.
Follow up PRs will build out remaining functionality to reach parity with the current UI including the create/edit backfill form.
The new UI is available at / but all pages have a banner encouraging people to use the old UI at /app/ until the new UI is fully built out.
The old UI at /app/ will continue to be fully available until the new UI is entirely built and tested.
None of this code or design is set in stone but I'm leaning towards smaller incremental PRs than continuing to work in a separate branch as the rest is built out.
This sets up initial infrastructure, home page autocomplete search bar, and backfill tables page. It uses the new Misk UI stack (kotlinx.html DSL, Tailwind UI, Hotwire) and doesn't require any
npm installwhich should make it much easier to maintain and extend long term.The initial new UI work will focus on parity with the existing UI, future improvements can be done which add net new functionality or refactor but the initial work will solely focus on parity. Refactoring and new features will be much easier once the old UI is deleted since all corresponding UI changes can be done in the new Kotlin UI code.
Follow up PRs will build out remaining functionality to reach parity with the current UI including the create/edit backfill form.
The new UI is available at
/but all pages have a banner encouraging people to use the old UI at/app/until the new UI is fully built out.The old UI at
/app/will continue to be fully available until the new UI is entirely built and tested.None of this code or design is set in stone but I'm leaning towards smaller incremental PRs than continuing to work in a separate branch as the rest is built out.