FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Implementing a bilingual static corporate site across six pages
Combining typed content and shared components with route, publication-boundary, and static-output checks
Purpose
The content and visual design for Home, Privacy, and Terms were fixed, but the existing site still used an old placeholder and no longer matched the wording, screen structure, publication scope, or locale-prefixed routes. The fixed inputs needed to replace it as a working static site without inventing additional information.
The aim was to make three pages directly addressable in Japanese and English while accurately presenting AI Talent, the boundary of human accountability, what was not currently offered, and the legal documents. A CMS, accounts, server endpoints, tracking, and additional pages remained outside scope.
Implementation
site-content projection centralized locales, page kinds, shared wording, ten AI Talent profiles, and Privacy and Terms sections as typed data. Shared components rendered Home and legal pages, while each localized route file remained a thin wrapper supplying only its locale and page kind.
- Home, Privacy, and Terms were provided in both Japanese and English, fixing the content surface at six URLs.
- The root without a locale became a redirect-only entry to Japanese Home and carried no independent content, canonical, or sitemap entry.
- No locale persistence through browser language, cookies, localStorage, or query parameters was added.
Home was organized as Hero, About Wiroh, AI Talent, and Current Activities and Availability. It explained that AI Talent means role-based AI personas rather than real people or human employees, that portraits are AI-generated images, and that the human owner retains important decisions and final accountability. It also stated that products and creative works were not yet individually offered or published on the site.
Shared header, footer, locale selector, Home, and legal renderers were implemented. The mobile menu gained accessible naming, expanded state, Escape close, focus return, and keyboard order. Legal pages remained static without a client-side menu, while portraits were treated as decorative images whose meaning was supplied by surrounding text.
- site build settings enabled locale prefixes including the default locale and limited the sitemap to content pages.
- Redirect documents used immediate forwarding and noindex while carrying no canonical.
- An internal operational project guide under public assets was moved into documentation, with checks preventing its return to either source public assets or built output.
static-site verification was added to inspect six outputs, HTML language, self canonicals, Japanese and English alternates, the default entry, sitemap, redirects, internal links, mobile-menu semantics, ten portraits, excluded routes, old placeholders, the 404 page, robots, and security headers. The same static verification was configured to run after builds as a continuing check.
Rendering diagram…
What was confirmed
Verification results
Type checking completed with zero errors, warnings, or hints, and the static build completed.
Static verification passed after checking six content URLs, three redirect entries, canonical and alternate metadata, sitemap content, excluded routes, ten portraits, the 404 page, robots, and security headers.
The internal project guide initially found in public assets, the missing continuing check, and documentation describing old routes were corrected, and absence of the project guide from both source and built output became an explicit check.
Source inspection found no added forms, analytics, external fetches, Cookie or localStorage persistence, additional external services, or active data flows.
At the cutoff, the static-site implementation and checks had been applied to the target. Production deployment and public reachability, final publication judgment, production data flows, and portrait rights and provenance remained unverified.
Basis for completion
The implementation scope was complete when six localized content pages and redirects, shared components, metadata, sitemap, and the public-asset boundary were available as static output, covered by type, build, and static checks, and those checks passed.