Skip to content

Docs: reorganize responsive footer navigation#9257

Merged
JonnyBurger merged 7 commits into
mainfrom
docs/responsive-footer-navigation
Jul 20, 2026
Merged

Docs: reorganize responsive footer navigation#9257
JonnyBurger merged 7 commits into
mainfrom
docs/responsive-footer-navigation

Conversation

@MehmetAdemi

@MehmetAdemi MehmetAdemi commented Jul 18, 2026

Copy link
Copy Markdown
Member

Merge order

Important

Do not merge this PR until #9238 has been merged.

This footer work was split out of #9238 for focused review. It should follow the accessibility-documentation PR in the requested merge order.

Summary

  • Organize footer categories as Remotion, Community, Company, Legal & Trust, and More.
  • Add dedicated Company and Legal & Trust categories, including the individual legal, accessibility, and acknowledgement links.
  • Move Success Stories below Showcase, move Changelog below GitHub, and remove Learn from the Remotion category.
  • Use the requested License & Pricing label and the dedicated Legal & Trust category for legal navigation.
  • Replace the footer's one-layout behavior with responsive grids:
    • Wide: branding plus five category columns
    • Medium: branding above three category columns
    • Narrow: branding above two category columns
  • Add alt text to the footer logo.

Test plan

  • bun run formatting
  • bun x oxfmt docusaurus.config.ts --check
  • bun x eslint src/theme/Footer/Links/MultiColumn/index.tsx

MehmetAdemi and others added 5 commits July 18, 2026 18:36
Replace individual legal and acknowledgement links with one internal link to the License, Pricing and Compliance overview.

Co-authored-by: Cursor <cursoragent@cursor.com>
Use the concise “License & Legal” footer label while keeping the link directed to the License, Pricing and Compliance overview.

Co-authored-by: Cursor <cursoragent@cursor.com>
Remove the Learn link and use concise License & Pricing and Legal labels while preserving their destinations.

Co-authored-by: Cursor <cursoragent@cursor.com>
Group company and legal resources into dedicated footer categories while keeping community and product links discoverable.

Co-authored-by: Cursor <cursoragent@cursor.com>
Order the footer categories consistently and use dedicated wide, medium, and narrow grid layouts to avoid unused mobile space.

Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel

vercel Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
bugs Ready Ready Preview, Comment Jul 19, 2026 10:46am
remotion Ready Ready Preview, Comment Jul 19, 2026 10:46am

Request Review

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ No critical issues — one minor suggestion inline.

Reviewed changes — reorganizes the docs site footer into Remotion, Community, Company, Legal & Trust, and More categories and makes the layout responsive across breakpoints.

  • Split the former More category into Company and Legal & Trust and move Success Stories, Changelog, and legal links into their new homes.
  • Replace the footer's single-row inline styling with responsive CSS grid classes (remotion-footer__links, remotion-footer__categories).
  • Add logo alt text in the custom Footer/Links/MultiColumn theme component.

Pullfrog  | Fix all ➔Fix 👍s ➔View workflow run | Using Kimi K2 (free via Pullfrog for OSS) | 𝕏

Comment thread packages/docs/docusaurus.config.ts Outdated
Comment thread packages/docs/docusaurus.config.ts Outdated
@MehmetAdemi
MehmetAdemi requested a review from JonnyBurger July 19, 2026 10:53
@JonnyBurger JonnyBurger changed the title docs: reorganize responsive footer navigation Docs: reorganize responsive footer navigation Jul 20, 2026
@JonnyBurger
JonnyBurger merged commit 83f221d into main Jul 20, 2026
16 checks passed
@JonnyBurger
JonnyBurger deleted the docs/responsive-footer-navigation branch July 20, 2026 08:21
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