chore(website): rename twenty-website-new → twenty-website (#20745)

## Summary
Follow-up to the Cloudflare/OpenNext migration (#20741). Now that the
legacy `twenty-website` package was already removed in #20270, the
`-new` suffix on the marketing site package is no longer meaningful.

## What changes
- **Directory rename**: `git mv packages/twenty-website-new
packages/twenty-website` (1213 files moved, no content change)
- **Package + nx config**: `package.json` and `project.json` name fields
updated, `sourceRoot` repointed
- **Source refs**: `load-local-articles.ts` and
`load-local-release-notes.ts` had a hardcoded `'twenty-website-new'`
segment in their monorepo-root fallback path;
`app/[locale]/releases/page.tsx` had display strings showing where to
add content
- **External refs**: root `package.json` workspaces, root `CLAUDE.md` /
`README.md`, `twenty-sdk` + `create-twenty-app` READMEs,
`.vscode/twenty.code-workspace`, `.cursor/rules/changelog-process.mdc`,
Crowdin config + the three `website-i18n-*` CI workflows +
`ci-website.yaml`
- **Docker cleanup**:
`packages/twenty-docker/twenty-website-new/Dockerfile` deleted; the two
Makefile targets (`prod-website-new-build` / `prod-website-new-run`)
that referenced it removed — EKS deploy was retired in the Cloudflare
migration
- **`yarn.lock`** regenerated against the new workspace path

## What's deliberately not in this PR
The dev hostname `website-new.twenty-main.com` in `wrangler.jsonc` stays
for now. Migrating it to `website.twenty-main.com` needs coordinated DNS
deletion (current CNAME points at the legacy Docusaurus NLB and serves
503s) and removal of the matching legacy `website` Helm chart in
`twenty-infra`. Flagged as a separate cleanup.

Companion infra PR: https://github.com/twentyhq/twenty-infra/pull/682
(workflow paths + Terraform ECR + docs)

## Test plan
- [x] `yarn install --immutable` resolves clean against the new path
- [x] `npx nx typecheck twenty-website` passes
- [x] `npx nx lint twenty-website` passes
- [ ] CI on this PR confirms the same on a fresh checkout
- [ ] After merge: trigger `Deploy Website` workflow against
`environment=dev` to confirm the renamed working-directory deploys
correctly
This commit is contained in:
Félix Malfait
2026-05-19 23:42:09 +02:00
committed by GitHub
parent 24a836cc7d
commit 658bdf3e57
1228 changed files with 106 additions and 151 deletions
@@ -0,0 +1,56 @@
import { Body } from '@/design-system/components/Body';
import { getServerI18n } from '@/lib/i18n/utils/get-server-i18n';
import { theme } from '@/theme';
import { styled } from '@linaria/react';
import React from 'react';
import type { ProblemPointType } from './problem-point-type';
const StyledPoints = styled.div`
display: grid;
grid-template-columns: 1fr;
row-gap: ${theme.spacing(6)};
@media (min-width: ${theme.breakpoints.md}px) {
max-width: 454px;
}
`;
const StyledDivider = styled.div`
height: 0;
border-top: 0.75px dashed ${theme.colors.primary.border[80]};
width: 100%;
opacity: 50%;
`;
const StyledPoint = styled.div`
display: grid;
grid-template-columns: 1fr;
row-gap: ${theme.spacing(2)};
@media (min-width: ${theme.breakpoints.md}px) {
max-width: 380px;
width: 100%;
}
`;
type PointsProps = {
points: ProblemPointType[];
};
export function Points({ points }: PointsProps) {
const i18n = getServerI18n();
return (
<StyledPoints>
{points.map((point, index) => (
<React.Fragment key={index}>
<StyledDivider />
<StyledPoint>
{point.heading}
<Body size="sm">{i18n._(point.body)}</Body>
</StyledPoint>
</React.Fragment>
))}
</StyledPoints>
);
}