lessthanno · lessthanno · Aug 1, 2026 · Aug 1, 2026 · Aug 1, 2026
diff --git a/README.md b/README.md
@@ -9,6 +9,8 @@ ready. Every result remains editable in Figma.
 
 [简体中文](README.zh-CN.md)
 
+**Website:** [lessthanno.github.io/Layntra](https://lessthanno.github.io/Layntra/)
+
 ## Download
 
 **[Download Layntra v0.1.0](https://github.com/lessthanno/Layntra/releases/tag/v0.1.0)**

diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -7,6 +7,8 @@ Layntra 是为产品经理和非技术用户准备的 Codex 插件。用 `$laynt
 
 [English](README.md)
 
+**官网：** [lessthanno.github.io/Layntra](https://lessthanno.github.io/Layntra/)
+
 ## 下载插件
 
 **[下载 Layntra v0.1.0](https://github.com/lessthanno/Layntra/releases/tag/v0.1.0)**

diff --git a/docs/.nojekyll b/docs/.nojekyll
@@ -0,0 +1 @@
+
diff --git a/docs/404.html b/docs/404.html
@@ -0,0 +1,8 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1"><meta name="robots" content="noindex">
+  <title>Page not found — Layntra</title><meta name="description" content="The requested Layntra page was not found."><meta name="theme-color" content="#0b0c0a"><link rel="stylesheet" href="/Layntra/assets/site.css">
+</head>
+<body><main id="main" class="shell legal"><p class="eyebrow">404</p><h1>That page is not here.</h1><p class="page-lead">The link may be old, or the address may be incomplete.</p><div class="actions"><a class="button" href="/Layntra/">Go to Layntra</a><a class="button-secondary" href="https://github.com/lessthanno/Layntra">Open GitHub</a></div></main></body>
+</html>
diff --git a/docs/about.html b/docs/about.html
@@ -0,0 +1,26 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
+  <title>About Layntra — Open-source design infrastructure for Codex and Figma</title>
+  <meta name="description" content="Why Haozi created Layntra: to give product managers and nontechnical builders a controlled, open-source path from Codex intent to editable Figma layers.">
+  <link rel="canonical" href="https://lessthanno.github.io/Layntra/about.html">
+  <meta property="og:type" content="article"><meta property="og:title" content="About Layntra"><meta property="og:description" content="Design infrastructure for people who need more control than a chat prompt."><meta property="og:url" content="https://lessthanno.github.io/Layntra/about.html"><meta property="og:site_name" content="Layntra">
+  <meta name="twitter:card" content="summary"><meta name="theme-color" content="#0b0c0a"><link rel="stylesheet" href="assets/site.css">
+</head>
+<body>
+  <a class="skip-link" href="#main">Skip to content</a>
+  <header class="site-header"><nav class="nav shell" aria-label="Primary navigation"><a class="brand" href="./" aria-label="Layntra home"><span class="brand-mark" aria-hidden="true"></span>Layntra</a><div class="nav-links"><a href="how-it-works.html">How it works</a><a href="faq.html">FAQ</a><a href="https://github.com/lessthanno/Layntra">GitHub</a><a class="button" href="https://github.com/lessthanno/Layntra/releases/tag/v0.1.0">Download v0.1.0</a></div></nav></header>
+  <main id="main">
+    <header class="page-hero"><div class="shell"><p class="eyebrow">About the project</p><h1>Design infrastructure for people outside the code editor.</h1><p class="page-lead">Layntra was created by Haozi to give product managers and nontechnical builders a controlled path from Codex intent to editable Figma work.</p></div></header>
+    <section class="section"><div class="shell prose">
+      <h2>The problem</h2><p>AI can describe a design, generate an image, or suggest code. Those are useful outputs, but they do not automatically create a trustworthy workflow inside the design file. When an AI can write, the user needs to know which file and selection it will touch, whether the current action is read-only, and how to recover.</p>
+      <h2>The idea</h2><p>Layntra treats “AI to Figma” as infrastructure rather than a poster generator. Its core contract is inspect → plan → apply → undo. Poster creation can be an example skill, but the bridge and control model are generic.</p>
+      <h2>Who it is for</h2><p>The primary audience is product managers, founders, researchers, writers, operators, and other people who can describe product intent but do not want to learn an integration protocol before they can work. Installation is documented step by step; normal use happens through explicit commands and plain-language instructions in Codex.</p>
+      <h2>Open-source direction</h2><p>Layntra is released under the MIT License. The source, architecture decisions, security policy, roadmap, tests, and current limitations are public on <a href="https://github.com/lessthanno/Layntra">GitHub</a>. Contributions and critical feedback are welcome through <a href="https://github.com/lessthanno/Layntra/issues">GitHub Issues</a>.</p>
+      <div class="actions"><a class="button" href="https://github.com/lessthanno/Layntra">Explore the repository</a><a class="button-secondary" href="https://github.com/lessthanno/Layntra/blob/main/docs/roadmap.md">Read the roadmap</a></div>
+    </div></section>
+  </main>
+  <footer class="site-footer"><div class="footer-grid shell"><div>© 2026 Haozi · Layntra is MIT licensed and is not affiliated with Figma or OpenAI.</div><div class="footer-links"><a aria-current="page" href="about.html">About</a><a href="privacy.html">Privacy</a><a href="terms.html">Terms</a><a href="https://github.com/lessthanno/Layntra/issues">Contact</a></div></div></footer>
+</body>
+</html>
diff --git a/docs/adr/0004-static-geo-site-on-github-pages.md b/docs/adr/0004-static-geo-site-on-github-pages.md
@@ -0,0 +1,38 @@
+# ADR 0004: Publish a static GEO site from `main/docs`
+
+- Status: Accepted
+- Date: 2026-08-01
+
+## Context
+
+Layntra needs a stable, crawlable public identity beyond a repository README. The
+site must answer product, installation, trust, permission, and comparison
+questions in content that search engines and answer engines can fetch without
+running client-side JavaScript. The project has no hosted application, account
+system, analytics service, or web runtime.
+
+## Decision
+
+Publish a dependency-free static site from the `docs` directory on the protected
+`main` branch using GitHub Pages branch deployment.
+
+The site will use hand-authored semantic HTML and one local CSS file. It will
+publish canonical metadata, visible factual answers, Schema.org JSON-LD,
+`robots.txt`, `sitemap.xml`, `llms.txt`, and `llms-full.txt`. Automated contract
+tests will verify metadata, internal links, crawl files, structured data, and
+the absence of remote scripts.
+
+The content may compare Layntra with common hosted integration patterns, but it
+must not claim guaranteed indexing, affiliation with Figma or OpenAI, or a
+capability to bypass Figma permissions.
+
+## Consequences
+
+- Search and answer engines can fetch meaningful content from first response
+  HTML, even when scripting is unavailable.
+- The deployment adds no JavaScript dependency, package supply chain, analytics,
+  cookies, database, or hosted Layntra service.
+- Existing Markdown guides remain in `docs` and can still be linked from GitHub.
+- Shared header and footer markup is duplicated across the small static site;
+  tests reduce drift, and a generator can be considered if page count grows.
+- Discovery and citation are more likely but cannot be guaranteed by Layntra.