[shigahi]

Redesigns https://worknot.classmethod.live/ to follow the Classmethod Europe brand and corporate website guidelines, and makes the page content crawlable.

Design

• Official Classmethod Europe logo (unmodified files, at least 50px tall) in the header and footer
• IBM Plex Sans, approved for English content at CME, self-hosted instead of Google Fonts
• Neutral palette in the style of classmethod.jp. Links and buttons use #1b6ec2, a darker shade of the brand blue #2d8de0 that meets WCAG AA; #2d8de0 is used for accents only
• No abstract background imagery and no third-party logos. Copy follows the guideline wording rules (entity name, no unsupported claims)
• The generator form uses an MUI theme with the same brand colors and font. Its logic is unchanged

SEO

• Hero, features, how it works and FAQ are static HTML in index.html, so the page content no longer depends on JavaScript. React renders only the generator into #root
• New title and description, Open Graph and Twitter image alt text, and robots meta
• JSON-LD: Organization (Classmethod (Europe) GmbH), WebSite, WebApplication and FAQPage. The FAQ answers match the visible text exactly
• New brand OG image (70 KB, previously 620 KB), favicon and Apple touch icon; lastmod added to the sitemap
• Placeholder domain changed from the defunct worknot.classmethod.cf to www.example.com

Japanese page (/ja/)

• Japanese version of the landing page with its own title, description, Japanese OG image (rendered with Noto Sans JP) and FAQPage JSON-LD
• hreflang links (en, ja, x-default) on both pages and in the sitemap, og:locale:alternate, and a language switch in the header
• Company, product and feature names (Classmethod (Europe) GmbH, Cloudflare Workers, Notion Sites, Workers Free/Paid, Image Transformations, GitHub Actions) are kept in English
• Japanese text uses the HQ font stack (Noto Sans JP, Hiragino Sans, Meiryo) from the system, without web font downloads, and word-break: auto-phrase for headings
• The generator form stays in English; the Japanese page says so. Translating the form is a separate change

Verification

• npm test (8/8), tsc --noEmit and npm run build pass
• Lighthouse, local build vs. current production:

	Performance	Accessibility	Best practices	SEO	LCP
Production	77	90	82	100	4.4 s
This branch	98	100	100	100	2.0 s

• Both pages also score 98 / 100 / 100 / 100 after adding the Japanese page
• Checked desktop (1440px) and mobile (390px and 360px) screenshots of both pages, the advanced settings panel and script generation in Playwright, with no console errors