Overview
Time Columns previously expanded its Japanese site into an English section under /en/. That work included English articles, an English top page, English About and privacy pages, hreflang, sitemap entries, internal links, GitHub push, and Cloudflare Pages deployment.
This article is the continuation of that workflow.
Once the English section exists, the next issue is not how to translate one article. The real question is how to keep publishing English pages from Japanese drafts without reducing the work to automatic translation.
An English article on a website is an independent page. It can be indexed, linked, included in a sitemap, and connected to its Japanese counterpart with canonical and hreflang tags.
Different from Social Media Auto Translation
Social media auto translation is useful. It lets a reader understand a post in another language without the author creating a separate page.
But it is still a support function for the original post. It does not create an English URL, title, meta description, internal links, related articles, sitemap entry, canonical tag, or hreflang relationship.
An English site article does all of those things. At that point, the task is no longer translation only. It is website operation.
Review the Japanese Draft First
In Time Columns, the process does not start by converting everything into HTML immediately. The Japanese draft is checked first.
The review is not only about whether the prose is clean. We check whether the article ends with practical judgment, avoids generic explanation, stays concise, avoids unnecessary padding, and does not overlap too much with existing articles.
This matters because the Japanese draft becomes the source of the English version. If the original article has no clear point of view, the English version will only reproduce that weakness in another language.
Do Not Translate Literally
After the Japanese draft is approved, the English version is written. But it should not be a literal translation.
A Japanese article is written for Japanese readers, Japanese context, and Time LLC's practical tone. The English version may need a different title, introduction, structure, or explanation to match English search intent.
A title that works as a Japanese experience note may work better as a troubleshooting title in English. A phrase that feels natural in Japanese may need more context in English.
The English version is based on the Japanese draft, but it is rebuilt for its own reader and purpose.
Tone Changes by Purpose
The same source idea can be written differently depending on where it is published.
On Time Columns, the article should read as a calm practical column with structure, headings, metadata, internal links, and search intent in mind. On external platforms such as Medium, DEV, or Hashnode, the opening and framing may need to feel more natural for English-speaking readers. On social media, the same idea must become shorter and more direct.
This is the main difference from automatic translation. English media operation rewrites the article according to reader, purpose, search intent, and site structure.
HTML and SEO Settings Are Part of the Work
After the English text is prepared, the page still needs HTML and SEO settings.
That includes title, meta description, canonical, hreflang, breadcrumb UI, BreadcrumbList JSON-LD, article summary, table of contents, and related articles.
With those elements in place, the English article becomes a formal page in the site rather than a translated text fragment.
Sitemap and Internal Links Matter
Publishing an article is not complete when the file is created. The page must be reachable from the site.
For Time Columns, that means updating the Japanese top page, article archive, English top page, related links, and sitemap.xml. The English page should link back to the Japanese page, and the Japanese page should link to the English version when they correspond.
Internal-link checks and sitemap validation are part of the publishing flow.
Deployment Through GitHub and Cloudflare Pages
Time Columns is operated with GitHub and Cloudflare Pages. After the local files are edited and validated, a commit and push to GitHub triggers Cloudflare Pages deployment.
This makes the workflow short: review the Japanese draft, rebuild it in English, create HTML, update navigation and sitemap, check links, push to GitHub, and publish through Cloudflare Pages.
In this workflow, AI is not only a translation tool. It becomes a practical assistant inside website operations.
Human Judgment Is Still Required
Automation does not remove the need for human review.
Humans still decide whether the article is worth publishing, whether it overlaps with existing content, whether it reflects Time LLC's practical view, and whether the English version should be structured differently from the Japanese version.
AI can turn a decision into implementation. It cannot replace the need to decide what should be published and why.
Summary
Turning a Japanese draft into English is not enough if the goal is to operate an English site.
The work includes draft review, rewriting for English readers, HTML conversion, canonical and hreflang settings, sitemap updates, internal links, related articles, and deployment.
Social auto translation helps people understand a post. English site publishing turns the idea into a searchable, linkable, maintainable web asset.
With generative AI and Codex, the distance from Japanese draft review to English site publishing becomes much shorter. The final value still depends on human judgment.