website: add Next.js landing page for burr.apache.org

[andreahlert]

Summary

Adds a modern landing page for burr.apache.org built with Next.js 15, Tailwind CSS and Magic UI. The Sphinx docs move from / to /docs/ so both coexist on the same domain.

Preview: https://andreahlert.github.io/burr-website/

Landing page sections

• Hero with animated stats (GitHub stars, PyPI downloads, Discord members)
• Interactive code terminal with syntax-highlighted Python examples (Chatbot, Multi-Agent, State Machine)
• Feature highlights grid (State Management, Observability, Human in the Loop, Streaming, Parallelism, Testing)
• Integration marquee with real SVG logos (OpenAI, Anthropic, Gemini, LangChain, Haystack, Hamilton, FastAPI, Ray, OpenTelemetry)
• Testimonial carousel with the 7 existing quotes
• Community links (Discord, GitHub, Twitter/X)
• ASF-compliant footer

ASF compliance

• Required links: License, Thanks, Security, Sponsorship, Privacy Policy, Apache Homepage, Incubator
• Incubation disclaimer with hyperlinks to ASF and Incubator
• Trademark attribution statement
• "(Incubating)" in first reference (title, navbar, hero)
• Events link included

Build & deploy

• New unified workflow build-site.yml that builds both Next.js and Sphinx, merges outputs, and deploys to asf-site
• Landing page served at /, Sphinx docs at /docs/
• sphinx-docs.yml retains build + artifact upload for PR review (deploy removed to avoid conflicts)
• Sphinx html_baseurl updated to https://burr.apache.org/docs/

Tech stack

Next.js 15 (App Router), Tailwind CSS v4, shadcn/ui, Magic UI components (Marquee, NumberTicker, ShimmerButton, BlurFade, BorderBeam, DotPattern, AnimatedShinyText), shiki for syntax highlighting. Static export (next export) for Apache infra compatibility.

Test plan

• cd website && npm ci && npm run build produces static output in out/
• cd docs && sphinx-build -b dirhtml . _build/html builds docs with /docs/ baseurl
• Merged output: /index.html (landing page) + /docs/index.html (Sphinx)
• All ASF required links present in footer
• Incubation disclaimer with correct wording
• Dark/light mode toggle works
• Code tabs switch between Chatbot/Agent/State Machine
• Mobile responsive (hamburger menu, stacked layout)
• build-site.yml workflow runs successfully

[andreahlert]

Hey @skrawcz @pjfanning @elijahbenizzy

Built a landing page to replace the current Sphinx homepage at burr.apache.org. The idea is to have a proper splash page that positions Burr more professionally and helps attract new contributors and users to the community.

Preview: https://andreahlert.github.io/burr-website/

The existing Sphinx docs stay untouched, just move to /docs/. A single workflow builds both Next.js and Sphinx and deploys to asf-site. All ASF required links, incubation disclaimer and trademark attribution are covered.

Would love feedback on the content, design or anything else before we move forward with this.

[skrawcz]

@andreahlert is there a way to make things backwards compatible with the old urls?

[andreahlert]

@andreahlert is there a way to make things backwards compatible with the old urls?

@skrawcz Added a .htaccess with 301 redirects for all the old Sphinx root paths pointing to /docs/. Since ASF's default AllowOverride is All, this should work out of the box without any infra request.

it'd be good to confirm with the infra team before merging, just to make sure Burr doesn't have any custom virtual host config that could interfere... a quick message on #asfinfra in the ASF Slack should be enough if you could.

[skrawcz]

asfinfra

Sigh -- need to be invited:

If you want to invite ASF people (those with an @apache.org address) who are not on Slack yet to join your project's Slack discussions:

In the Slack app, click the "ASF" header at the top left.
Select Invite people to ASF
Use the Members option and, in the form that appears, provide the person's ASF email address.

[skrawcz]

@andreahlert want to double check my work -- those missing files are needed right?

[andreahlert]

@skrawcz Yes, those files (constants.ts and utils.ts) were definitely needed, I forgot to include them in the original push. Thanks for catching that and adding them.

Reviewed your other changes, noticed just one nit: if we ever move to a different Sphinx theme, this could silently break since it depends on the .sidebar-brand selector. Maybe worth a comment in the template noting why it's there. Not a blocker at all though.

Everything looks solid.