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

package/dist/templates/_shared/amplify/data/list-posts-by-tag.js

@@ -2,23 +2,21 @@ import { util } from '@aws-appsync/utils'
 
 // AppSync JS resolver: list published posts for a given tag, newest first.
 // Reads the denormalized PostTag table where:
-//   PK = `${siteId}#${tag}`
+//   PK = tag
 //   SK = `${publishedAt}#${postId}` (so descending SK = newest first)
 //
 // Authorization is enforced by AppSync; the resolver itself only encodes
-// the tag/site partition condition. Drafts never appear here because the
+// the tag partition condition. Drafts never appear here because the
 // admin client only writes PostTag rows for posts whose status is
 // 'published'.
 export function request(ctx) {
-  const { siteId = 'default', tag, limit, nextToken } = ctx.args
+  const { tag, limit, nextToken } = ctx.args
   return {
     operation: 'Query',
     query: {
-      expression: '#siteIdTag = :siteIdTag',
-      expressionNames: { '#siteIdTag': 'siteIdTag' },
-      expressionValues: util.dynamodb.toMapValues({
-        ':siteIdTag': `${siteId}#${tag}`,
-      }),
+      expression: '#tag = :tag',
+      expressionNames: { '#tag': 'tag' },
+      expressionValues: util.dynamodb.toMapValues({ ':tag': tag }),
     },
     scanIndexForward: false, // newest first (SK descends)
     limit: limit ?? 20,
@@ -33,7 +31,6 @@ export function response(ctx) {
   // PublicPost shape `listPublishedPosts` returns; the detail view should
   // call `getPublishedPost(slug)` for the full body.
   const items = (ctx.result.items ?? []).map((row) => ({
-    siteId: row.siteId,
     postId: row.postId,
     slug: row.slug,
     title: row.title,

package/dist/templates/_shared/amplify/data/list-published-posts.js

@@ -1,23 +1,22 @@
 import { util } from '@aws-appsync/utils'
 
-// AppSync JS resolver: list a site's published posts, newest first.
+// AppSync JS resolver: list published posts, newest first.
 //
-// Reads the `bySiteIdStatus` GSI:
-//   PK = `${siteId}#${status}`   (denormalized field set by writers)
+// Reads the `byStatus` GSI:
+//   PK = status   (denormalized field set by writers)
 //   SK = publishedAt
-// so a single Query reads only one site's published partition. Drafts
-// never appear because the PK condition pins status='published'.
+// so a single Query reads only the `published` partition. Drafts never
+// appear because the PK condition pins status='published'.
 //
 // Date-range filtering (`from`, `to`) is pushed into the SK condition,
 // so DynamoDB only reads the matching range. `nextToken` paginates
 // without re-issuing a fresh query.
 export function request(ctx) {
-  const { siteId = 'default', from, to, limit, nextToken } = ctx.args
+  const { from, to, limit, nextToken } = ctx.args
 
-  const partition = `${siteId}#published`
-  let keyExpression = '#siteIdStatus = :siteIdStatus'
-  const expressionNames = { '#siteIdStatus': 'siteIdStatus' }
-  const expressionValueMap = { ':siteIdStatus': partition }
+  let keyExpression = '#status = :status'
+  const expressionNames = { '#status': 'status' }
+  const expressionValueMap = { ':status': 'published' }
 
   if (from && to) {
     keyExpression += ' AND #publishedAt BETWEEN :from AND :to'
@@ -36,7 +35,7 @@ export function request(ctx) {
 
   return {
     operation: 'Query',
-    index: 'bySiteIdStatus',
+    index: 'byStatus',
     query: {
       expression: keyExpression,
       expressionNames,

package/dist/templates/_shared/amplify/data/resource.custom.ts

@@ -14,12 +14,11 @@
 //     return {
 //       Bookmark: a
 //         .model({
-//           siteId: a.string().required(),
 //           bookmarkId: a.id().required(),
 //           url: a.string().required(),
 //           title: a.string(),
 //         })
-//         .identifier(['siteId', 'bookmarkId'])
+//         .identifier(['bookmarkId'])
 //         .authorization((allow: any) => [allow.groups(['ampless-admin', 'ampless-editor'])]),
 //     }
 //   }

package/dist/templates/_shared/amplify/data/resource.ts

@@ -1,8 +1,13 @@
 import { fileURLToPath } from 'node:url'
 import { dirname, resolve } from 'node:path'
 import { a, defineData, type ClientSchema } from '@aws-amplify/backend'
-import { amplessSchemaModels, defaultAuthorizationModes } from '@ampless/backend'
+import {
+  amplessSchemaModels,
+  amplessSchemaAuthorization,
+  defaultAuthorizationModes,
+} from '@ampless/backend'
 import { userAdmin } from '../functions/user-admin/resource.js'
+import { mcpHandler } from '../functions/mcp-handler/resource.js'
 import { customSchemaModels } from './resource.custom.js'
 
 // AppSync's `a.handler.custom({ entry })` paths are resolved by CDK
@@ -26,10 +31,22 @@ const resolverPaths = {
   listPostsByTag: resolve(__dirname, 'list-posts-by-tag.js'),
 }
 
-const schema = a.schema({
-  ...amplessSchemaModels(a, { resolverPaths, userAdminFunction: userAdmin }),
-  ...customSchemaModels(a),
-})
+const schema = a
+  .schema({
+    ...amplessSchemaModels(a, {
+      resolverPaths,
+      userAdminFunction: userAdmin,
+    }),
+    ...customSchemaModels(a),
+  })
+  // Schema-level `.authorization()` is the only place resource auth is
+  // honoured in `@aws-amplify/data-schema` — model-level callbacks have
+  // `resource` destructured out of `allow`. The helper returns an empty
+  // array when no Lambda refs are supplied, so the schema stays
+  // unaffected if MCP is later removed.
+  .authorization((allow) => amplessSchemaAuthorization(allow, {
+    mcpHandlerFunction: mcpHandler,
+  }))
 
 export type Schema = ClientSchema<typeof schema>
 export const data = defineData({

package/dist/templates/_shared/amplify/events/processor-untrusted/resource.ts

@@ -6,4 +6,8 @@ export const processorUntrusted = defineFunction({
   // Untrusted plugins do pure JS work; modest memory.
   memoryMB: 256,
   timeoutSeconds: 30,
+  // Pin to the data stack so all event-system Lambdas live together
+  // (dispatcher / processor-trusted are also `data`) and the function
+  // stack doesn't bridge data ↔ storage ↔ auth in a CFN cycle.
+  resourceGroupName: 'data',
 })

package/dist/templates/_shared/amplify/functions/mcp-handler/handler.ts

@@ -0,0 +1 @@
+export { handler } from '@ampless/backend/functions/mcp-handler'

package/dist/templates/_shared/amplify/functions/mcp-handler/resource.ts

@@ -0,0 +1,11 @@
+import { defineFunction } from '@aws-amplify/backend'
+
+export const mcpHandler = defineFunction({
+  name: 'mcp-handler',
+  entry: './handler.ts',
+  // Co-locate with the data stack so the function has the KvStore
+  // table ARN available without cross-stack references at synth time.
+  resourceGroupName: 'data',
+  memoryMB: 512,
+  timeoutSeconds: 30,
+})

package/dist/templates/_shared/amplify/functions/user-admin/resource.ts

@@ -1,6 +1,12 @@
 import { defineFunction } from '@aws-amplify/backend'
 
+// `resourceGroupName: 'data'` co-locates this Lambda with the AppSync
+// stack. Required because ampless wires userAdmin as a custom GraphQL
+// resolver (data → function) while api-key-renewer reads graphqlApi
+// (function → data); leaving userAdmin in the default `function` stack
+// turns those two arrows into a CloudFormation circular dependency.
 export const userAdmin = defineFunction({
   name: 'user-admin',
   entry: './handler.ts',
+  resourceGroupName: 'data',
 })

package/dist/templates/_shared/app/(admin)/admin/mcp-tokens/page.tsx

@@ -0,0 +1,5 @@
+import { admin } from '@/lib/admin'
+import { createMcpTokensPage } from '@ampless/admin/pages'
+
+export const dynamic = 'force-dynamic'
+export default createMcpTokensPage(admin)

package/dist/templates/_shared/app/globals.css

@@ -1,4 +1,17 @@
 @import 'tailwindcss';
+
+/*
+ * Tailwind v4 doesn't scan `node_modules/` by default. The admin UI
+ * (`@ampless/admin`) and runtime UI bits (`@ampless/runtime`) ship
+ * compiled JS that uses Tailwind utility classes; without these
+ * explicit sources, every utility used only inside those packages
+ * (e.g. the admin sidebar's `flex`, `fixed`, `md:sticky`, ...) gets
+ * tree-shaken out of the final CSS, and the admin layout falls back
+ * to browser defaults — sidebar overlaps main content, etc.
+ */
+@source '../node_modules/@ampless/admin/dist';
+@source '../node_modules/@ampless/runtime/dist';
+
 @plugin '@tailwindcss/typography';
 /* DADS theme plugin from Digital Agency. Loaded globally so the
  * `templates/dads/` theme can use DADS-conformant color variables
@@ -36,6 +49,31 @@
   --radius-sm: calc(var(--radius) - 4px);
 }
 
+/*
+ * Color scheme:
+ *
+ * - `:root { color-scheme: light dark }` opts the page into both modes
+ *   and asks the browser to pick based on the visitor's
+ *   `prefers-color-scheme` setting.
+ * - `html[data-color-scheme='light' | 'dark']` lets the site admin pin
+ *   one mode regardless of system preference. The attribute is written
+ *   by `app/layout.tsx` from the per-site setting
+ *   (`theme.colorScheme`, default `'auto'` = no attribute).
+ * - Token values below (and in each theme's `tokens.css`) use the CSS
+ *   `light-dark(L, D)` function so a single declaration covers both
+ *   modes — the active `color-scheme` selects between L and D at
+ *   paint time.
+ */
+:root {
+  color-scheme: light dark;
+}
+html[data-color-scheme='light'] {
+  color-scheme: light;
+}
+html[data-color-scheme='dark'] {
+  color-scheme: dark;
+}
+
 /*
  * Default tokens — used as fallback when no theme's `[data-theme=...]`
  * selector matches (e.g. body has no data-theme attribute, or admin
@@ -45,49 +83,27 @@
  * `<body data-theme="...">` attribute makes the scoped selector match.
  */
 :root {
-  --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) {
-  :root {
-    --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);
-  }
-}
-
 body {
   font-family: var(--ampless-body-font, system-ui, -apple-system, sans-serif);
   background: var(--background);

package/dist/templates/_shared/app/layout.tsx

@@ -1,6 +1,6 @@
 import type { Metadata } from 'next'
 import { headers } from 'next/headers'
-import { DEFAULT_SITE_ID } from 'ampless'
+import { validateColorScheme } from '@ampless/runtime'
 import { Providers } from './providers'
 import { siteMetadata } from '@/lib/seo'
 import { loadThemeConfig, renderThemeCss } from '@/lib/theme-config'
@@ -8,25 +8,38 @@ import { getLocale, getDictionary } from '@/lib/i18n'
 import { I18nProvider } from '@/components/i18n-provider'
 import './globals.css'
 
-// Resolve metadata per site at request time. The middleware sets
-// `x-site-id` so we can pick the right merged settings; falls back to
-// DEFAULT_SITE_ID for admin / API routes that don't go through the
-// public middleware path.
 export async function generateMetadata(): Promise<Metadata> {
-  const h = await headers()
-  const siteId = h.get('x-site-id') ?? DEFAULT_SITE_ID
-  return siteMetadata(siteId)
+  return siteMetadata()
 }
 
 export default async function RootLayout({ children }: { children: React.ReactNode }) {
   const h = await headers()
-  const siteId = h.get('x-site-id') ?? DEFAULT_SITE_ID
-  const theme = await loadThemeConfig(siteId)
+  const theme = await loadThemeConfig()
   const themeCss = renderThemeCss(theme.cssVars)
   const locale = getLocale()
   const dict = getDictionary(locale)
+  // `data-color-scheme` pins the visitor to light or dark regardless
+  // of their system `prefers-color-scheme`. `'auto'` (the default)
+  // means we don't emit the attribute at all, so `globals.css`'s
+  // `:root { color-scheme: light dark }` lets the browser follow the
+  // system setting. Themes use `light-dark()` in their tokens.css so a
+  // single declaration covers both modes; the active `color-scheme`
+  // selects which value is rendered.
+  //
+  // The admin's theme-settings iframe preview passes the unsaved
+  // selection via `?previewColorScheme=<mode>`, which middleware
+  // forwards as `x-preview-color-scheme`. When that header is present
+  // it overrides the stored site setting so the preview updates live.
+  const previewHeader = h.get('x-preview-color-scheme')
+  const effectiveColorScheme = previewHeader
+    ? validateColorScheme(previewHeader)
+    : theme.colorScheme
+  const htmlProps: { lang: string; 'data-color-scheme'?: 'light' | 'dark' } = { lang: locale }
+  if (effectiveColorScheme !== 'auto') {
+    htmlProps['data-color-scheme'] = effectiveColorScheme
+  }
   return (
-    <html lang={locale}>
+    <html {...htmlProps}>
       <head>
         {/* Inline `:root` overrides come AFTER globals.css so they win
             against the static defaults. Validated values only — see

package/dist/templates/_shared/app/site/[siteId]/r/[slug]/[[...path]]/route.ts

@@ -0,0 +1,17 @@
+import { ampless } from '@/lib/ampless'
+import { createUnderscoreRouteHandler } from '@ampless/runtime/routes'
+
+// Unified handler for the public `/_/<slug>(/...)` URL family.
+// Covers two cases that both bypass the theme's post page:
+//
+//  - `format: 'html'` posts with `metadata.no_layout === true`
+//    → bare HTML response, no Next.js root layout, no theme chrome
+//  - `format: 'static'` posts
+//    → S3 presigned URL redirect for the entrypoint and every bundle file
+//
+// File location uses the literal folder name `r/` (not `_/`) because
+// Next.js's App Router excludes any path part starting with `_` from
+// route discovery. The middleware rewrites the public `/_/` prefix
+// to `/r/` internally; the browser URL stays `/_/<slug>(/...)`.
+export const dynamic = 'force-dynamic'
+export const GET = createUnderscoreRouteHandler(ampless)

package/dist/templates/_shared/cms.config.ts

@@ -27,29 +27,7 @@ export default defineConfig({
       losslessForPng: true,
     },
   },
-  // Multi-site config. Leave undefined for single-site operation; the
-  // runtime then serves every request as siteId='default'. To run
-  // multiple sites in one Amplify environment, declare two or more
-  // entries here:
-  //
-  //   sites: {
-  //     blog: {
-  //       domains: ['blog.example.com', 'www.example.com'],
-  //       name: 'My Blog',
-  //       url: 'https://blog.example.com',
-  //     },
-  //     docs: {
-  //       domains: ['docs.example.com'],
-  //       name: 'Docs',
-  //       url: 'https://docs.example.com',
-  //     },
-  //   },
-  //
-  // In multi-site mode the middleware forces `Cache-Control: private,
-  // no-store` on public responses (Amplify Hosting's CloudFront cache
-  // key cannot disambiguate by Host). Single-site mode leaves caching
-  // to the default page directives.
-
+  // Date display format.
   // 'iso'    — YYYY-MM-DD (default; SSR-safe, locale-neutral)
   // 'long'   — "April 27, 2026" (en-US)
   // 'locale' — browser/server locale

package/dist/templates/_shared/components/site-chrome/site-sidebar.tsx

@@ -4,7 +4,6 @@ import { listPostsByTag } from '@/lib/posts-public'
 
 interface Props {
   links: string | undefined
-  siteId: string
   className?: string
 }
 
@@ -19,7 +18,7 @@ interface Props {
  * paired with `force-dynamic` on the page so fresh content shows up
  * after publish events.
  */
-export async function SiteSidebar({ links, siteId, className }: Props) {
+export async function SiteSidebar({ links, className }: Props) {
   const items = parseLinkList(links)
   if (items.length === 0) return null
 
@@ -28,7 +27,7 @@ export async function SiteSidebar({ links, siteId, className }: Props) {
     items.map(async (item) => {
       const tagRef = isTagListUrl(item.url)
       if (!tagRef) return { type: 'link' as const, label: item.label, url: item.url }
-      const { items: posts } = await listPostsByTag(tagRef.tag, { siteId, limit: 50 })
+      const { items: posts } = await listPostsByTag(tagRef.tag, { limit: 50 })
       return {
         type: 'tagSection' as const,
         label: item.label,

package/dist/templates/_shared/lib/admin.ts

@@ -7,13 +7,14 @@
 // `amplify_outputs.json` and `cms.config` into a single `Admin`
 // instance.
 //
-// NOTE: We intentionally do NOT pass an `ampless` instance to
-// createAdmin. That would import `lib/ampless.ts`, which imports
-// `themes-registry`, which (via theme pages → `lib/i18n.ts`) imports
-// back to this file — a circular chain that crashes with a TDZ
-// ReferenceError on `ampless` at module init. `createAdmin` builds
-// its own internal Ampless when omitted, which is functionally
-// equivalent for admin's needs.
+// NOTE: we pass `ampless` as a thunk (not the resolved instance) so we
+// don't have a static `import './ampless'` at the top of this file.
+// A static import would form the cycle
+//   `lib/admin.ts → lib/ampless.ts → themes-registry → themes → lib/i18n.ts → lib/admin.ts`
+// and crash with a TDZ ReferenceError on `ampless` at module init.
+// The thunk uses dynamic `import()` so `lib/ampless.ts` only loads on
+// the first `loadSiteSettings` / `loadThemeConfig` call (request
+// time), by which point every module has finished initialising.
 
 import outputs from '../amplify_outputs.json'
 import cmsConfig from '@/cms.config'
@@ -22,6 +23,7 @@ import { createAdmin } from '@ampless/admin'
 export const admin = createAdmin({
   outputs,
   cmsConfig,
+  ampless: async () => (await import('./ampless')).ampless,
   locale: (cmsConfig as { locale?: string }).locale ?? 'en',
 })
 

package/dist/templates/_shared/lib/posts-public.ts

@@ -4,7 +4,7 @@
 //
 // New code should import from `@/lib/ampless` directly:
 //   import { ampless } from '@/lib/ampless'
-//   const posts = await ampless.listPublishedPosts({ siteId })
+//   const posts = await ampless.listPublishedPosts()
 
 import { ampless } from './ampless'
 

package/dist/templates/_shared/package.json

@@ -8,10 +8,9 @@
     "build": "next build",
     "start": "next start",
     "lint": "next lint",
-    "sandbox": "ampx sandbox",
-    "sandbox:dev": "ampx sandbox --once && next dev",
-    "update-ampless": "npx create-ampless@alpha upgrade",
-    "copy-theme": "npx create-ampless@alpha copy-theme"
+    "sandbox": "ampx sandbox --once && next dev",
+    "update-ampless": "npx create-ampless@latest upgrade",
+    "copy-theme": "npx create-ampless@latest copy-theme"
   },
   "dependencies": {
     "@aws-amplify/adapter-nextjs": "^1.6.0",
@@ -23,15 +22,15 @@
     "@tiptap/pm": "^3.23.4",
     "@tiptap/react": "^3.23.4",
     "@tiptap/starter-kit": "^3.23.4",
-    "@ampless/plugin-og-image": "^0.2.0-alpha.2",
-    "@ampless/plugin-rss": "^0.2.0-alpha.2",
-    "@ampless/plugin-seo": "^0.2.0-alpha.2",
-    "@ampless/plugin-webhook": "^0.2.0-alpha.2",
-    "@ampless/admin": "^0.2.0-alpha.7",
-    "@ampless/backend": "^0.2.0-alpha.3",
-    "@ampless/runtime": "^0.2.0-alpha.4",
+    "@ampless/plugin-og-image": "^0.2.0-alpha.9",
+    "@ampless/plugin-rss": "^0.2.0-alpha.9",
+    "@ampless/plugin-seo": "^0.2.0-alpha.9",
+    "@ampless/plugin-webhook": "^0.2.0-alpha.9",
+    "@ampless/admin": "^1.0.0-alpha.26",
+    "@ampless/backend": "^1.0.0-alpha.19",
+    "@ampless/runtime": "^1.0.0-alpha.13",
     "@digital-go-jp/tailwind-theme-plugin": "^0.3.4",
-    "ampless": "^0.2.0-alpha.2",
+    "ampless": "^1.0.0-alpha.9",
     "aws-amplify": "^6.10.0",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",

package/dist/templates/_shared/proxy.ts

@@ -5,9 +5,9 @@
 // for API stability; only the user-side file convention (proxy.ts +
 // `export const proxy`) follows Next 16's rename.
 //
-// See `@ampless/runtime/middleware` for behaviour details: multi-site
-// host rewrite, `<slug>.html` → raw route, `?previewTheme=` header
-// forwarding, multi-site Cache-Control override.
+// See `@ampless/runtime/middleware` for behaviour details:
+// `/path` → `/site/default/path` rewrite, `?previewTheme=` header
+// forwarding.
 
 import cmsConfig from './cms.config'
 import { createAmplessMiddleware } from '@ampless/runtime/middleware'

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

@@ -0,0 +1,22 @@
+> English: [README.md](./README.md)
+> 
+# Blog テーマ
+
+shadcn/ui のデフォルトに準じたニュートラル系モノクロ。時系列の投稿フィード、個別投稿ページ、タグ別一覧を提供します。
+
+## カスタマイズ
+
+`/admin/sites/<siteId>/theme` で設定:
+
+- **プライマリカラー** — ボタン、リンク、強調表示の背景色
+- **アクセントカラー**
+- **フォーカスリング**
+- **破壊的操作** — 削除等の操作色
+- **角丸**
+- **本文フォント** — システムサンセリフ / セリフ (Georgia) / セリフ (Iowan) / 等幅
+- **トップに固定する記事のスラッグ** — 公開済み投稿を 1 件ホームの先頭に固定
+- **ロゴ画像 URL**
+- **ヘッダーナビ** — ラベル + URL のペア
+- **フッターリンク** — ラベル + URL のペア
+
+サイトごとのライト/ダークカラースキームは ampless の標準テーマトークン経由で反映されます。

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