mirror of
https://github.com/supabase/supabase.git
synced 2026-10-09 19:35:06 +03:00
Ali Waseem
5297eeaf80
## Summary
- Adds a reusable `<LegalDocVersions />` component (dropdown below the
page header) that swaps the active legal doc version inline via shallow
query-param routing (`?version=v1`).
- Converts `/terms` and `/enterprise-terms` from MDX to TSX pages and
moves their content into versioned MDX under
`apps/www/data/legal/<doc>/v1.mdx`.
- Seeds `v2.mdx` for both docs as a copy of v1 with the effective date
bumped to 6 May 2026 — the actual v2 language edits from legal will land
in a follow-up commit.
## Behavior
- `/terms` and `/enterprise-terms` default to v2 (latest); search
engines and bare URLs always see the latest.
- `/terms?version=v1` (and equivalent for enterprise) renders v1.
- Selecting a version updates the URL via `router.replace({ shallow:
true })` — no full page reload, browser back/forward works.
- Selecting the latest version clears the `version` query param.
- Existing `/docs/company/terms → /terms` redirect still works.
`noindex/nofollow` preserved on `/enterprise-terms` (both via meta and
the existing header rule).
## Out of scope
- The 5 v2 provision edits per agreement (lands in a follow-up once
Legal hands over the final language).
- `/privacy` and other legal pages — those keep their current pattern.
Linear:
[FE-3121](https://linear.app/supabase/issue/FE-3121/update-legal-terms-pages-and-add-version-selector)
## Test plan
- [ ] Visit `/terms` — defaults to v2, dropdown shows "Version 2 — May
6, 2026" and "Version 1 — July 11, 2025"
- [ ] Visit `/terms?version=v1` — renders v1
- [ ] Select v1 from the dropdown — URL becomes `?version=v1`, content
swaps without full page reload (no document request in Network tab)
- [ ] Select v2 — URL drops the `version` param, latest renders
- [ ] Browser back/forward steps through prior selections
- [ ] Repeat the above on `/enterprise-terms`
- [ ] Confirm `/enterprise-terms` is still `noindex, nofollow`
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Version selector and new Terms & Enterprise Terms pages allowing users
to switch between historical agreement versions.
* MDX-based legal documents now render as components for improved
content loading.
* **Documentation**
* Added v2 Terms and v2 Enterprise subscription agreements; v1 documents
adjusted and typography normalized for consistency.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
35 lines
1.1 KiB
TypeScript
35 lines
1.1 KiB
TypeScript
import { MDXProvider } from '@mdx-js/react'
|
|
import DefaultLayout from '~/components/Layouts/Default'
|
|
import SectionContainer from '~/components/Layouts/SectionContainer'
|
|
import LegalDocVersions, { type LegalDocVersion } from '~/components/Legal/LegalDocVersions'
|
|
import V1 from '~/data/legal/terms/v1.mdx'
|
|
import V2 from '~/data/legal/terms/v2.mdx'
|
|
import mdxComponents from '~/lib/mdx/mdxComponents'
|
|
import { NextSeo } from 'next-seo'
|
|
|
|
const meta = {
|
|
title: 'Terms of Service',
|
|
description: 'Supabase Terms of Service',
|
|
}
|
|
|
|
const versions: LegalDocVersion[] = [
|
|
{ id: 'v2', label: 'Version 2', effectiveDate: 'May 6, 2026', Component: V2 },
|
|
{ id: 'v1', label: 'Version 1', effectiveDate: 'July 11, 2025', Component: V1 },
|
|
]
|
|
|
|
export default function TermsPage() {
|
|
return (
|
|
<DefaultLayout>
|
|
<NextSeo {...meta} />
|
|
<MDXProvider components={mdxComponents()}>
|
|
<div className="prose max-w-none">
|
|
<SectionContainer>
|
|
<h1>Terms of service</h1>
|
|
<LegalDocVersions versions={versions} />
|
|
</SectionContainer>
|
|
</div>
|
|
</MDXProvider>
|
|
</DefaultLayout>
|
|
)
|
|
}
|