create-ampless 0.2.0-alpha.9 → 1.0.0-alpha.41

package/dist/templates/blog/README.md

@@ -1,52 +1,22 @@
-# {{siteName}}
+> 日本語版: [README.ja.md](./README.ja.md)
+> 
+# Blog theme
 
-A blog site powered by [ampless](https://github.com/heavymoons/ampless).
+Neutral monochrome with shadcn/ui defaults. Chronological post feed, single-post page, and tag listing.
 
-## Getting Started
+## Customizing
 
-This project uses Amplify Gen 2 for the backend (Cognito, DynamoDB, S3) and Next.js for the frontend.
+In `/admin/sites/<siteId>/theme`:
 
-```bash
-# 1. Install dependencies
-npm install
+- **Primary color** — buttons, links, accent fills
+- **Accent color**
+- **Focus ring**
+- **Destructive** — color used for destructive actions
+- **Corner radius**
+- **Body font** — System sans / Serif (Georgia) / Serif (Iowan) / Monospace
+- **Featured post slug** — pin one published post to the top of the home page
+- **Logo image URL**
+- **Header navigation** — label + URL pairs
+- **Footer links** — label + URL pairs
 
-# 2. Start a personal AWS sandbox (terminal 1)
-#    Requires AWS credentials configured (`aws configure`).
-#    First run takes ~5–10 min to provision resources.
-#    Generates amplify_outputs.json when ready.
-npx ampx sandbox
-
-# 3. Start the Next.js dev server (terminal 2)
-npm run dev
-```
-
-Then open [http://localhost:3000](http://localhost:3000).
-
-## First admin user
-
-Open [http://localhost:3000/login](http://localhost:3000/login) and click **Create admin account**. The first user to register is automatically added to the `ampless-admin` Cognito group.
-
-After that, manage content from `/admin`:
-
-- `/admin` — dashboard
-- `/admin/posts` — list / create / edit posts (tiptap editor)
-- `/admin/media` — upload images to S3
-
-## Production deploy
-
-```bash
-git init && git add . && git commit -m "init"
-git remote add origin <your-repo>
-git push
-# Then connect the repo to AWS Amplify Hosting in the AWS console.
-```
-
-## Customize
-
-- `cms.config.ts` — site name, media delivery mode, plugins
-- `app/` — Next.js App Router pages (`(public)/` for the blog, `(admin)/` for the CMS)
-- `amplify/` — Amplify Gen 2 backend definitions (auth / data / storage)
-
-## Plugins
-
-Enabled: {{plugins}}
+Per-site light/dark color scheme is honored through the standard ampless theme tokens.

package/dist/templates/blog/manifest.ts

@@ -1,7 +1,7 @@
 import { defineTheme } from 'ampless'
 
 // Customizable fields for the Blog theme. Edit values in
-// `/admin/sites/<siteId>/theme` — they're stored in KvStore and applied
+// `/admin/sites/default/theme` — they're stored in KvStore and applied
 // at render time as CSS variables on every public page.
 //
 // Labels / descriptions / groups accept either a plain string (works in

package/dist/templates/blog/pages/feed.ts

@@ -1,14 +1,13 @@
 import { publicAssetUrl } from '@/lib/storage'
 
 interface Ctx {
-  siteId: string
   request: Request
 }
 
 // /feed.xml proxy — plugin-rss regenerates the feed on content events
-// and writes it to `public/plugins/rss/{siteId}/feed.xml`.
-export async function blogFeedHandler({ siteId }: Ctx): Promise<Response> {
-  const url = publicAssetUrl(`public/plugins/rss/${siteId}/feed.xml`)
+// and writes it to `public/plugins/rss/feed.xml`.
+export async function blogFeedHandler(_ctx: Ctx): Promise<Response> {
+  const url = publicAssetUrl('public/plugins/rss/feed.xml')
   const upstream = await fetch(url, { cache: 'no-store' })
   if (!upstream.ok) {
     return new Response(

package/dist/templates/blog/pages/home.tsx

@@ -9,21 +9,18 @@ import { SiteHeader } from '@/components/site-chrome/site-header'
 import { SiteFooter } from '@/components/site-chrome/site-footer'
 import { t } from '@/lib/i18n'
 
-export default async function BlogHome({ params }: ThemeRouteContext) {
-  const { siteId } = await params
+export default async function BlogHome(_: ThemeRouteContext) {
   const [settings, theme, postsResult] = await Promise.all([
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
-    listPublishedPosts({ siteId }),
+    loadSiteSettings(),
+    loadThemeConfig(),
+    listPublishedPosts(),
   ])
 
   // Featured (pinned) post: render the body inline above the list,
   // then drop the same slug from the feed so it doesn't show twice.
   // Missing / unpublished slugs return null and the section is skipped.
   const featuredSlug = theme.values.featuredSlug?.trim()
-  const featured = featuredSlug
-    ? await getPublishedPost(featuredSlug, { siteId })
-    : null
+  const featured = featuredSlug ? await getPublishedPost(featuredSlug) : null
   const posts = featured
     ? postsResult.items.filter((p) => p.slug !== featured.slug)
     : postsResult.items

package/dist/templates/blog/pages/post.tsx

@@ -16,18 +16,18 @@ import { t } from '@/lib/i18n'
 type PostCtx = ThemeRouteContext<{ slug: string }>
 
 export async function generatePostMetadata({ params }: PostCtx): Promise<Metadata> {
-  const { siteId, slug } = await params
-  const post = await getPublishedPost(slug, { siteId })
+  const { slug } = await params
+  const post = await getPublishedPost(slug)
   if (!post) return {}
-  return postMetadata(post, siteId)
+  return postMetadata(post)
 }
 
 export default async function BlogPost({ params }: PostCtx) {
-  const { siteId, slug } = await params
+  const { slug } = await params
   const [post, settings, theme] = await Promise.all([
-    getPublishedPost(slug, { siteId }),
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
+    getPublishedPost(slug),
+    loadSiteSettings(),
+    loadThemeConfig(),
   ])
   if (!post) notFound()
 

package/dist/templates/blog/pages/sitemap.ts

@@ -1,14 +1,13 @@
 import { publicAssetUrl } from '@/lib/storage'
 
 interface Ctx {
-  siteId: string
   request: Request
 }
 
 // /sitemap.xml proxy — plugin-seo regenerates the sitemap on every
-// content event and writes it to `public/plugins/seo/{siteId}/sitemap.xml`.
-export async function blogSitemapHandler({ siteId }: Ctx): Promise<Response> {
-  const url = publicAssetUrl(`public/plugins/seo/${siteId}/sitemap.xml`)
+// content event and writes it to `public/plugins/seo/sitemap.xml`.
+export async function blogSitemapHandler(_ctx: Ctx): Promise<Response> {
+  const url = publicAssetUrl('public/plugins/seo/sitemap.xml')
   const upstream = await fetch(url, { cache: 'no-store' })
   if (!upstream.ok) {
     return new Response(

package/dist/templates/blog/pages/tag.tsx

@@ -9,12 +9,12 @@ import { SiteFooter } from '@/components/site-chrome/site-footer'
 import { t } from '@/lib/i18n'
 
 export default async function BlogTag({ params }: ThemeRouteContext<{ tag: string }>) {
-  const { siteId, tag } = await params
+  const { tag } = await params
   const decodedTag = decodeURIComponent(tag)
   const [{ items: posts }, settings, theme] = await Promise.all([
-    listPostsByTag(decodedTag, { siteId, limit: 50 }),
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
+    listPostsByTag(decodedTag, { limit: 50 }),
+    loadSiteSettings(),
+    loadThemeConfig(),
   ])
 
   if (posts.length === 0) notFound()

package/dist/templates/blog/tokens.css

@@ -7,48 +7,34 @@
  * loads, so `:root` selectors trump scoped attribute selectors of
  * equal specificity. The dispatcher emits `--primary` etc. only for
  * fields that have an override, leaving everything else to fall back
- * to these defaults. */
+ * to these defaults.
+ *
+ * Dark mode: tokens are declared with the CSS `light-dark(L, D)`
+ * function. The active `color-scheme` (set on `:root` and optionally
+ * pinned per-site via `html[data-color-scheme]`) selects whether L or
+ * D is rendered. `globals.css` opts the document into `color-scheme:
+ * light dark` by default — visitors with `prefers-color-scheme: dark`
+ * see the dark palette automatically.
+ */
 
 [data-theme='blog'] {
-  --background: oklch(1 0 0);
-  --foreground: oklch(0.145 0 0);
-  --card: oklch(1 0 0);
-  --card-foreground: oklch(0.145 0 0);
-  --primary: oklch(0.205 0 0);
-  --primary-foreground: oklch(0.985 0 0);
-  --secondary: oklch(0.97 0 0);
-  --secondary-foreground: oklch(0.205 0 0);
-  --muted: oklch(0.97 0 0);
-  --muted-foreground: oklch(0.556 0 0);
-  --accent: oklch(0.97 0 0);
-  --accent-foreground: oklch(0.205 0 0);
-  --destructive: oklch(0.577 0.245 27.325);
-  --destructive-foreground: oklch(0.985 0 0);
-  --border: oklch(0.922 0 0);
-  --input: oklch(0.922 0 0);
-  --ring: oklch(0.708 0 0);
+  --background: light-dark(oklch(1 0 0), oklch(0.145 0 0));
+  --foreground: light-dark(oklch(0.145 0 0), oklch(0.985 0 0));
+  --card: light-dark(oklch(1 0 0), oklch(0.145 0 0));
+  --card-foreground: light-dark(oklch(0.145 0 0), oklch(0.985 0 0));
+  --primary: light-dark(oklch(0.205 0 0), oklch(0.985 0 0));
+  --primary-foreground: light-dark(oklch(0.985 0 0), oklch(0.205 0 0));
+  --secondary: light-dark(oklch(0.97 0 0), oklch(0.269 0 0));
+  --secondary-foreground: light-dark(oklch(0.205 0 0), oklch(0.985 0 0));
+  --muted: light-dark(oklch(0.97 0 0), oklch(0.269 0 0));
+  --muted-foreground: light-dark(oklch(0.556 0 0), oklch(0.708 0 0));
+  --accent: light-dark(oklch(0.97 0 0), oklch(0.269 0 0));
+  --accent-foreground: light-dark(oklch(0.205 0 0), oklch(0.985 0 0));
+  --destructive: light-dark(oklch(0.577 0.245 27.325), oklch(0.396 0.141 25.723));
+  --destructive-foreground: light-dark(oklch(0.985 0 0), oklch(0.985 0 0));
+  --border: light-dark(oklch(0.922 0 0), oklch(0.269 0 0));
+  --input: light-dark(oklch(0.922 0 0), oklch(0.269 0 0));
+  --ring: light-dark(oklch(0.708 0 0), oklch(0.439 0 0));
   --radius: 0.5rem;
   --ampless-body-font: system-ui, -apple-system, sans-serif;
 }
-
-@media (prefers-color-scheme: dark) {
-  [data-theme='blog'] {
-    --background: oklch(0.145 0 0);
-    --foreground: oklch(0.985 0 0);
-    --card: oklch(0.145 0 0);
-    --card-foreground: oklch(0.985 0 0);
-    --primary: oklch(0.985 0 0);
-    --primary-foreground: oklch(0.205 0 0);
-    --secondary: oklch(0.269 0 0);
-    --secondary-foreground: oklch(0.985 0 0);
-    --muted: oklch(0.269 0 0);
-    --muted-foreground: oklch(0.708 0 0);
-    --accent: oklch(0.269 0 0);
-    --accent-foreground: oklch(0.985 0 0);
-    --destructive: oklch(0.396 0.141 25.723);
-    --destructive-foreground: oklch(0.985 0 0);
-    --border: oklch(0.269 0 0);
-    --input: oklch(0.269 0 0);
-    --ring: oklch(0.439 0 0);
-  }
-}

package/dist/templates/corporate/README.ja.md

@@ -0,0 +1,18 @@
+> English: [README.md](./README.md)
+> 
+# Corporate テーマ
+
+企業サイト向けの落ち着いたレイアウト。明るい背景にネイビーの配色、ヒーロー + お知らせ一覧構成、ヘッダー / フッターナビ付き。
+
+## カスタマイズ
+
+`/admin/sites/<siteId>/theme` で設定:
+
+- **タグライン** — ヒーロー内、サイト名の上に表示される短いフレーズ
+- **プライマリカラー**
+- **角丸**
+- **トップストーリーのスラッグ** — ヒーローとお知らせ一覧の間に公開済み投稿を 1 件フィーチャー
+- **ロゴ画像 URL**
+- **ヘッダーナビ** — ラベル + URL のペア
+- **フッターリンク** — ラベル + URL のペア
+- **フッター注記** — 住所 / 会社情報 / 追加の注意書き

package/dist/templates/corporate/README.md

@@ -1,20 +1,18 @@
-# {{siteName}}
+> 日本語版: [README.ja.md](./README.ja.md)
+> 
+# Corporate theme
 
-Corporate / company-site theme: navy on near-white, hero + news layout, header + footer navigation.
+Conservative business / company-site layout with hero and news section. Navy on near-white, header + footer navigation.
 
 ## Customizing
 
 In `/admin/sites/<siteId>/theme`:
 
-- Tagline (small line above the site name in the hero)
-- Header navigation (label + URL pairs)
-- Footer links + legend (address / company info / extra small print)
-- Primary color, corner radius
-
-## Getting started
-
-```bash
-npm install
-npx ampx sandbox
-npm run dev
-```
+- **Tagline** — short phrase shown above the site name in the hero
+- **Primary color**
+- **Corner radius**
+- **Top story slug** — feature one published post between the hero and the news section
+- **Logo image URL**
+- **Header navigation** — label + URL pairs
+- **Footer links** — label + URL pairs
+- **Footer legend** — address / company info / extra small print

package/dist/templates/corporate/pages/feed.ts

@@ -1,12 +1,11 @@
 import { publicAssetUrl } from '@/lib/storage'
 
 interface Ctx {
-  siteId: string
   request: Request
 }
 
-export async function corporateFeedHandler({ siteId }: Ctx): Promise<Response> {
-  const url = publicAssetUrl(`public/plugins/rss/${siteId}/feed.xml`)
+export async function corporateFeedHandler(_ctx: Ctx): Promise<Response> {
+  const url = publicAssetUrl('public/plugins/rss/feed.xml')
   const upstream = await fetch(url, { cache: 'no-store' })
   if (!upstream.ok) {
     return new Response(

package/dist/templates/corporate/pages/home.tsx

@@ -7,20 +7,17 @@ import { renderBody } from '@/lib/posts'
 import { SiteHeader } from '@/components/site-chrome/site-header'
 import { SiteFooter } from '@/components/site-chrome/site-footer'
 
-export default async function CorporateHome({ params }: ThemeRouteContext) {
-  const { siteId } = await params
+export default async function CorporateHome(_: ThemeRouteContext) {
   const [settings, theme, postsResult] = await Promise.all([
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
-    listPublishedPosts({ siteId, limit: 8 }),
+    loadSiteSettings(),
+    loadThemeConfig(),
+    listPublishedPosts({ limit: 8 }),
   ])
 
   // Top-story embed between hero and news. Filtered out of news to
   // avoid duplication. Skipped silently if missing / unpublished.
   const featuredSlug = theme.values.featuredSlug?.trim()
-  const featured = featuredSlug
-    ? await getPublishedPost(featuredSlug, { siteId })
-    : null
+  const featured = featuredSlug ? await getPublishedPost(featuredSlug) : null
   const posts = featured
     ? postsResult.items.filter((p) => p.slug !== featured.slug)
     : postsResult.items

package/dist/templates/corporate/pages/post.tsx

@@ -16,18 +16,18 @@ import { t } from '@/lib/i18n'
 type PostCtx = ThemeRouteContext<{ slug: string }>
 
 export async function generatePostMetadata({ params }: PostCtx): Promise<Metadata> {
-  const { siteId, slug } = await params
-  const post = await getPublishedPost(slug, { siteId })
+  const { slug } = await params
+  const post = await getPublishedPost(slug)
   if (!post) return {}
-  return postMetadata(post, siteId)
+  return postMetadata(post)
 }
 
 export default async function CorporatePost({ params }: PostCtx) {
-  const { siteId, slug } = await params
+  const { slug } = await params
   const [post, settings, theme] = await Promise.all([
-    getPublishedPost(slug, { siteId }),
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
+    getPublishedPost(slug),
+    loadSiteSettings(),
+    loadThemeConfig(),
   ])
   if (!post) notFound()
 

package/dist/templates/corporate/pages/sitemap.ts

@@ -1,12 +1,11 @@
 import { publicAssetUrl } from '@/lib/storage'
 
 interface Ctx {
-  siteId: string
   request: Request
 }
 
-export async function corporateSitemapHandler({ siteId }: Ctx): Promise<Response> {
-  const url = publicAssetUrl(`public/plugins/seo/${siteId}/sitemap.xml`)
+export async function corporateSitemapHandler(_ctx: Ctx): Promise<Response> {
+  const url = publicAssetUrl('public/plugins/seo/sitemap.xml')
   const upstream = await fetch(url, { cache: 'no-store' })
   if (!upstream.ok) {
     return new Response(

package/dist/templates/corporate/pages/tag.tsx

@@ -9,12 +9,12 @@ import { SiteFooter } from '@/components/site-chrome/site-footer'
 import { t } from '@/lib/i18n'
 
 export default async function CorporateTag({ params }: ThemeRouteContext<{ tag: string }>) {
-  const { siteId, tag } = await params
+  const { tag } = await params
   const decodedTag = decodeURIComponent(tag)
   const [{ items: posts }, settings, theme] = await Promise.all([
-    listPostsByTag(decodedTag, { siteId, limit: 50 }),
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
+    listPostsByTag(decodedTag, { limit: 50 }),
+    loadSiteSettings(),
+    loadThemeConfig(),
   ])
   if (posts.length === 0) notFound()
 

package/dist/templates/corporate/tokens.css

@@ -3,45 +3,23 @@
  * selector pattern as the other themes. */
 
 [data-theme='corporate'] {
-  --background: oklch(0.99 0 0);
-  --foreground: oklch(0.18 0.02 250);
-  --card: oklch(1 0 0);
-  --card-foreground: oklch(0.18 0.02 250);
-  --primary: oklch(0.4 0.13 250);
-  --primary-foreground: oklch(0.99 0 0);
-  --secondary: oklch(0.95 0.01 250);
-  --secondary-foreground: oklch(0.25 0.05 250);
-  --muted: oklch(0.96 0.005 250);
-  --muted-foreground: oklch(0.5 0.02 250);
-  --accent: oklch(0.95 0.02 250);
-  --accent-foreground: oklch(0.3 0.08 250);
-  --destructive: oklch(0.55 0.22 25);
-  --destructive-foreground: oklch(0.99 0 0);
-  --border: oklch(0.9 0.005 250);
-  --input: oklch(0.9 0.005 250);
-  --ring: oklch(0.4 0.13 250);
+  --background: light-dark(oklch(0.99 0 0), oklch(0.16 0.02 250));
+  --foreground: light-dark(oklch(0.18 0.02 250), oklch(0.96 0.005 250));
+  --card: light-dark(oklch(1 0 0), oklch(0.22 0.02 250));
+  --card-foreground: light-dark(oklch(0.18 0.02 250), oklch(0.96 0.005 250));
+  --primary: light-dark(oklch(0.4 0.13 250), oklch(0.7 0.14 250));
+  --primary-foreground: light-dark(oklch(0.99 0 0), oklch(0.16 0.02 250));
+  --secondary: light-dark(oklch(0.95 0.01 250), oklch(0.28 0.03 250));
+  --secondary-foreground: light-dark(oklch(0.25 0.05 250), oklch(0.96 0.005 250));
+  --muted: light-dark(oklch(0.96 0.005 250), oklch(0.26 0.02 250));
+  --muted-foreground: light-dark(oklch(0.5 0.02 250), oklch(0.7 0.02 250));
+  --accent: light-dark(oklch(0.95 0.02 250), oklch(0.32 0.05 250));
+  --accent-foreground: light-dark(oklch(0.3 0.08 250), oklch(0.96 0.005 250));
+  --destructive: light-dark(oklch(0.55 0.22 25), oklch(0.55 0.22 25));
+  --destructive-foreground: light-dark(oklch(0.99 0 0), oklch(0.99 0 0));
+  --border: light-dark(oklch(0.9 0.005 250), oklch(0.32 0.02 250));
+  --input: light-dark(oklch(0.9 0.005 250), oklch(0.32 0.02 250));
+  --ring: light-dark(oklch(0.4 0.13 250), oklch(0.7 0.14 250));
   --radius: 0.25rem;
   --ampless-body-font: system-ui, -apple-system, sans-serif;
 }
-
-@media (prefers-color-scheme: dark) {
-  [data-theme='corporate'] {
-    --background: oklch(0.16 0.02 250);
-    --foreground: oklch(0.96 0.005 250);
-    --card: oklch(0.22 0.02 250);
-    --card-foreground: oklch(0.96 0.005 250);
-    --primary: oklch(0.7 0.14 250);
-    --primary-foreground: oklch(0.16 0.02 250);
-    --secondary: oklch(0.28 0.03 250);
-    --secondary-foreground: oklch(0.96 0.005 250);
-    --muted: oklch(0.26 0.02 250);
-    --muted-foreground: oklch(0.7 0.02 250);
-    --accent: oklch(0.32 0.05 250);
-    --accent-foreground: oklch(0.96 0.005 250);
-    --destructive: oklch(0.55 0.22 25);
-    --destructive-foreground: oklch(0.99 0 0);
-    --border: oklch(0.32 0.02 250);
-    --input: oklch(0.32 0.02 250);
-    --ring: oklch(0.7 0.14 250);
-  }
-}

package/dist/templates/dads/README.ja.md

@@ -0,0 +1,31 @@
+> English: [README.md](./README.md)
+> 
+# DADS テーマ
+
+デジタル庁デザインシステム準拠のレイアウト。政府・自治体・公共系サイト向け。高コントラスト、アクセシビリティ重視、装飾控えめ。公式の **[デジタル庁デザインシステム Tailwind プラグイン](https://github.com/digital-go-jp/tailwind-theme-plugin)**（`@digital-go-jp/tailwind-theme-plugin`、MIT）をベースに構築されています。
+
+## プラグインが提供する機能
+
+- **カラーパレット** — プライマリカラーに `solidBlue`（`#0017c1`）を使用し、DADS の全スケール（ライトブルー、シアン、グリーン、ライム、イエロー、オレンジ、レッド、マゼンタ）を Tailwind クラス（`bg-blue-900`、`text-blue-50` など）で利用可能
+- **タイポグラフィ** — プラグイン経由で `fontFamily.sans` に Noto Sans JP を設定。`--ampless-body-font` として参照可能
+- **ボーダー半径** — `rounded-4` / `rounded-6` が利用可能
+
+`tokens.css` がプラグインの CSS 変数（`--color-blue-900` など）を ampless 標準のテーマ変数（`--primary`、`--background` など）にバインドするため、共有 chrome（SiteHeader、SiteFooter、shadcn ボタンなど）が自動的に DADS カラーで描画されます。
+
+DADS が新しいパレットバージョンを公開した場合、`@digital-go-jp/tailwind-theme-plugin` をバージョンアップするだけでテーマに反映されます。
+
+## カスタマイズ
+
+`/admin/sites/<siteId>/theme` で設定:
+
+- **ロゴ画像 URL** — 組織マーク
+- **プライマリカラー** — デフォルトは DADS の `solidBlue`。DADS 以外の色に変更するとサイトは DADS 準拠ではなくなります。
+- **トップストーリーのスラッグ** — ヒーローとお知らせ一覧の間に公開済み投稿を 1 件フィーチャー
+- **ヘッダーナビ** — ラベル + URL のペア
+- **フッターリンク** — ラベル + URL のペア
+- **フッター注記** — 住所 / 機関情報 / 追加の注意書き
+
+## 注意事項
+
+- ダークモードは反転色による近似実装です。プラグイン 0.3.4 時点では DADS の公式ダークパレットは存在しません。公式ダークパレットが公開された際は、`tokens.css` のダーク変数バインディングを更新してください。
+- このプラグインはデザイントークンのみを提供します。フル DADS コンポーネント（ボタン、アラート、タブなど）については [design-system-example-components](https://github.com/digital-go-jp/design-system-example-components) を参照し、必要に応じて取り込んでください。

package/dist/templates/dads/README.md

@@ -1,6 +1,8 @@
-# {{siteName}}
+> 日本語版: [README.ja.md](./README.ja.md)
+> 
+# DADS theme
 
-DADS theme — built on the official **[Digital Agency Design System Tailwind plugin](https://github.com/digital-go-jp/tailwind-theme-plugin)** (`@digital-go-jp/tailwind-theme-plugin`, MIT). Color palette and typography conform to DADS specifications, suitable for Japanese government / public-sector / institutional sites.
+Government / public-sector layout following the Digital Agency Design System aesthetic. High contrast, accessibility-first, minimal decoration. Built on the official **[Digital Agency Design System Tailwind plugin](https://github.com/digital-go-jp/tailwind-theme-plugin)** (`@digital-go-jp/tailwind-theme-plugin`, MIT).
 
 ## What's plugin-backed
 
@@ -8,28 +10,22 @@ DADS theme — built on the official **[Digital Agency Design System Tailwind pl
 - **Typography** — `fontFamily.sans` set to Noto Sans JP via the plugin; surfaced through `--ampless-body-font`
 - **Border radii** — `rounded-4` / `rounded-6` available
 
-`templates/dads/tokens.css` binds the plugin's CSS variables (`--color-blue-900` etc.) to ampless's standard theme variables (`--primary`, `--background`, ...) so all shared chrome (SiteHeader, SiteFooter, shadcn buttons, etc.) automatically renders in DADS colors.
+`tokens.css` binds the plugin's CSS variables (`--color-blue-900` etc.) to the standard ampless theme variables (`--primary`, `--background`, ...) so all shared chrome (SiteHeader, SiteFooter, shadcn buttons, etc.) automatically renders in DADS colors.
 
-When DADS publishes a new palette version, bumping `@digital-go-jp/tailwind-theme-plugin` in `package.json` is enough — the theme picks it up.
+When DADS publishes a new palette version, bumping `@digital-go-jp/tailwind-theme-plugin` is enough — the theme picks it up.
 
 ## Customizing
 
 In `/admin/sites/<siteId>/theme`:
 
-- **Logo image URL** — branding (organization mark)
-- **Primary color** — defaults to DADS solidBlue. Changing to a non-DADS color makes the site no longer DADS-conformant.
-- **Top story slug** — feature one published post between hero and news
-- **Header navigation / Footer links / Footer legend**
+- **Logo image URL** — organization mark
+- **Primary color** — defaults to DADS `solidBlue`. Changing to a non-DADS color makes the site no longer DADS-conformant.
+- **Top story slug** — feature one published post between the hero and the news section
+- **Header navigation** — label + URL pairs
+- **Footer links** — label + URL pairs
+- **Footer legend** — address / agency info / extra small print
 
 ## Notes
 
-- Dark mode uses an inverted approximation. DADS doesn't ship an official dark palette as of plugin 0.3.4; when one lands, update `templates/dads/tokens.css` to bind the dark variables.
+- Dark mode uses an inverted approximation. DADS doesn't ship an official dark palette as of plugin 0.3.4; when one lands, update `tokens.css` to bind the dark variables.
 - The plugin only provides design tokens. For full DADS components (buttons, alerts, tabs, etc.), see [design-system-example-components](https://github.com/digital-go-jp/design-system-example-components) and adapt as needed.
-
-## Getting started
-
-```bash
-npm install
-npx ampx sandbox
-npm run dev
-```

package/dist/templates/dads/pages/feed.ts

@@ -1,12 +1,11 @@
 import { publicAssetUrl } from '@/lib/storage'
 
 interface Ctx {
-  siteId: string
   request: Request
 }
 
-export async function dadsFeedHandler({ siteId }: Ctx): Promise<Response> {
-  const url = publicAssetUrl(`public/plugins/rss/${siteId}/feed.xml`)
+export async function dadsFeedHandler(_ctx: Ctx): Promise<Response> {
+  const url = publicAssetUrl('public/plugins/rss/feed.xml')
   const upstream = await fetch(url, { cache: 'no-store' })
   if (!upstream.ok) {
     return new Response(

package/dist/templates/dads/pages/home.tsx

@@ -11,18 +11,15 @@ import { SiteFooter } from '@/components/site-chrome/site-footer'
 // formal news list with prominent dates. Layout deliberately
 // understated — DADS leans on hierarchy and whitespace, not
 // decoration.
-export default async function DadsHome({ params }: ThemeRouteContext) {
-  const { siteId } = await params
+export default async function DadsHome(_: ThemeRouteContext) {
   const [settings, theme, postsResult] = await Promise.all([
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
-    listPublishedPosts({ siteId, limit: 10 }),
+    loadSiteSettings(),
+    loadThemeConfig(),
+    listPublishedPosts({ limit: 10 }),
   ])
 
   const featuredSlug = theme.values.featuredSlug?.trim()
-  const featured = featuredSlug
-    ? await getPublishedPost(featuredSlug, { siteId })
-    : null
+  const featured = featuredSlug ? await getPublishedPost(featuredSlug) : null
   const posts = featured
     ? postsResult.items.filter((p) => p.slug !== featured.slug)
     : postsResult.items

package/dist/templates/dads/pages/post.tsx

@@ -16,18 +16,18 @@ import { t } from '@/lib/i18n'
 type PostCtx = ThemeRouteContext<{ slug: string }>
 
 export async function generatePostMetadata({ params }: PostCtx): Promise<Metadata> {
-  const { siteId, slug } = await params
-  const post = await getPublishedPost(slug, { siteId })
+  const { slug } = await params
+  const post = await getPublishedPost(slug)
   if (!post) return {}
-  return postMetadata(post, siteId)
+  return postMetadata(post)
 }
 
 export default async function DadsPost({ params }: PostCtx) {
-  const { siteId, slug } = await params
+  const { slug } = await params
   const [post, settings, theme] = await Promise.all([
-    getPublishedPost(slug, { siteId }),
-    loadSiteSettings(siteId),
-    loadThemeConfig(siteId),
+    getPublishedPost(slug),
+    loadSiteSettings(),
+    loadThemeConfig(),
   ])
   if (!post) notFound()