All refreshed. Just Shift-R the page in case you have problems.

On Sat, Dec 20, 2025 at 4:43 PM Kaxil Naik <[email protected]> wrote:

> For folks seeing old button (different from screenshot in the PR comment),
> give it a few hours for cache.
>
> Jarek has triggered Cloundfront cache invalidation so shouldn’t be too long
> before you see the changes.
>
> On Sat, 20 Dec 2025 at 15:30, Kaxil Naik <[email protected]> wrote:
>
> > This wasn’t critical so didn’t invalidate cloudfront cache since it will
> > propagate anyway eventually. But s3 is synced.
> >
> > On Sat, 20 Dec 2025 at 15:02, Jarek Potiuk <[email protected]> wrote:
> >
> >> Strange thing - I do not see it yet
> >>
> >>
> https://github.com/apache/airflow-site-archive/actions/workflows/github-to-s3.yml
> >> -> has not been run. And this one is needed (even if you manually sync
> S3,
> >> you also need to invalidate cloudfront cache after you sync stuff to S3.
> >>
> >> On Sat, Dec 20, 2025 at 3:20 PM Kaxil Naik <[email protected]> wrote:
> >>
> >> > Thank you Phani & Jarek. PR is merged and this has now been deployed
> to
> >> our
> >> > Prod site for 3.1.5 and stable html docs.
> >> >
> >> >
> >> > On Sat, 20 Dec 2025 at 08:44, Phani Kumar via dev <
> >> [email protected]>
> >> > wrote:
> >> >
> >> > > This is amazing. Great work Kaxil !
> >> > >
> >> > > On Sat, Dec 20, 2025 at 1:23 PM Jarek Potiuk <[email protected]>
> >> wrote:
> >> > >
> >> > > > Very nice and slick. Did my review :) .. looks great and it's
> nice.
> >> > > > One small comment I would even say we should leave it as the only
> >> > option.
> >> > > > It feels weird to have two different ways of searching :)
> >> > > >
> >> > > > On Sat, Dec 20, 2025 at 2:07 AM Kaxil Naik <[email protected]>
> >> > wrote:
> >> > > >
> >> > > > > Hey all,
> >> > > > >
> >> > > > > tl;dr: Visit
> >> > > > https://airflow.staged.apache.org/docs/apache-airflow/3.1.5/,
> >> > > > > press Cmd+K (or Ctrl+K), and try the new search experience.
> >> > > > >
> >> > > > > Now details :D
> >> > > > >
> >> > > > > After implementing dark mode to solve one of my frustrations
> >> > > > > and modernizing deps on airflow-site, I went on the journey to
> >> > improve
> >> > > > > (have an alternate) search experience on Airflow docs. I really
> >> hate
> >> > > the
> >> > > > > Sphinx search -- it is slow and often returns irrelevant
> results.
> >> > > > >
> >> > > > > Similar GH issue created 3 years ago:
> >> > > > > https://github.com/apache/airflow-site/issues/666
> >> > > > >
> >> > > > > I am happy to share that
> >> > https://github.com/apache/airflow/pull/59658
> >> > > > > introduces a modern, fast, client-side search powered by
> Pagefind
> >> (
> >> > > > > https://pagefind.app/).
> >> > > > >
> >> > > > > Preview is available on our staging site:
> >> > > > > https://airflow.staged.apache.org/docs/apache-airflow/3.1.5/
> >> > > > >
> >> > > > > Visit it, and press cmd+K and try it out.
> >> > > > >
> >> > > > > Key improvements:
> >> > > > >
> >> > > > >    - Instant search: Results appear as you type with no server
> >> > > > round-trips
> >> > > > >    - Better relevance: Better title matches rank
> >> > > > >    - Cleaner results: Auto-generated API docs and internal pages
> >> are
> >> > > > >    excluded
> >> > > > >    - Keyboard navigation: Full keyboard support with
> Cmd+K/Ctrl+K
> >> > > > shortcut
> >> > > > >    - Modern UI: Custom-built modal with our own CSS/JS
> >> > > > >    - Privacy-friendly: All search happens client-side, no
> external
> >> > > > services
> >> > > > >
> >> > > > > The PR is ready for review. Once merged, I'll deploy it to
> >> > production.
> >> > > > > Documentation for the Sphinx extension is included in the PR.
> >> > > > >
> >> > > > > I'd appreciate feedback and reviews! After spending considerable
> >> time
> >> > > on
> >> > > > > the JS, CSS, and search tuning, I'm confident this will
> >> significantly
> >> > > > > improve our users' documentation experience.
> >> > > > >
> >> > > > > Happy Holidays. 🎄
> >> > > > >
> >> > > > > Regards,
> >> > > > > Kaxil
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

Reply via email to