@sudajs/cli 0.12.3 → 0.13.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sudajs/cli",
-  "version": "0.12.3",
+  "version": "0.13.0",
   "type": "module",
   "bin": {
     "suda": "./bin/suda.js"
@@ -34,7 +34,7 @@
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
     "zod": "^3.24.1",
-    "@sudajs/theme-engine": "4.0.2"
+    "@sudajs/theme-engine": "5.1.0"
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4.3.0",

package/templates/theme/AGENTS.md

@@ -139,7 +139,7 @@ Field source of truth:
   generation reliable.
 - Use `description`, `placeholder`, and `visibleIf` only when they help the
   editor or AI choose the right value.
-- Suda extended field types are `url`, `icon`, `font`, `menu`, `color`,
+- Suda extended field types are `url`, `icon`, `color`,
   `range`, `spacing`, `media`, `image`, `video`, and `posts`. These are valid
   in `fields` and are normalized by `@sudajs/theme-engine`.
 
@@ -189,8 +189,6 @@ fields: {
   download: { type: "media", kind: "file", label: t("common.fields.file") },
   icon: { type: "icon", label: t("common.fields.icon") },
   accentColor: { type: "color", label: t("common.fields.color") },
-  font: { type: "font", label: t("common.fields.font") },
-  links: { type: "menu", label: t("common.fields.menu") },
   spacing: { type: "spacing", label: t("common.fields.spacing") },
 
   // Dynamic post lists. Use this only on page sections that intentionally
@@ -369,6 +367,12 @@ platform. In the section render function, call
 with the exact posts field key. Never import Prisma, call platform APIs, or
 query the database from theme code.
 
+When rendering posts returned by `getPostResource`, build links from the
+platform-provided `post.url` first. If it is missing, derive the URL only from
+`post.slug` as `/posts/${encodeURIComponent(post.slug)}`; if neither exists,
+use `#`. Do not guess alternate fields such as `href`, `path`, `permalink`,
+`postUrl`, or `canonicalUrl`.
+
 Do not add `resourceQuery: { type: "posts" }` or
 `resource_query: { type: "posts" }`. Do not assume the field must be named
 `query`. A section may have only one top-level posts field; do not nest posts
@@ -492,11 +496,11 @@ radius, shadows, or spacing.
 - Section props may expose semantic choices such as `tone`, `variant`,
   `columns`, `mediaPosition`, `showImage`, or `spacing`. Map those choices to
   the existing design tokens and shared CSS classes.
-- Do not add raw `color`, `font`, `spacing`, `radius`, or `shadow` fields to a
+- Do not add raw `color`, typography, `spacing`, `radius`, or `shadow` fields to a
   section just because the CSS has a value. Expose a design token field only
   when the user should intentionally customize that value per component
   instance. Otherwise, keep the value in the theme CSS.
-- Use `color`, `font`, and `spacing` field types only for real editor-facing
+- Use `color` and `spacing` field types only for real editor-facing
   design controls. Use `select`/`radio` for named variants that are already
   part of the theme design system.
 - Local blocks inside `blockSlots` inherit the host section's design system.
@@ -534,10 +538,11 @@ Use the most specific field type available. A generic `text` field may pass type
 
 - Always use `url` for links and routes, including anchors, `mailto:` links, and external URLs. Do not use `text` for href-like props.
 - Use `image` for images, `video` for videos, and `media` only when the same prop intentionally accepts mixed media.
-- Use `color` for color values, `icon` for icon names, `font` for font selections, `range` for bounded numbers, `spacing` for spacing tokens, and `menu` for navigation items.
+- Use `color` for color values, `icon` for icon names, `range` for bounded numbers, and `spacing` for spacing tokens.
+- Use `select` for typography choices and `array`/`object` fields for navigation lists.
 - Use `select` or `radio` for fixed choices. Keep option values stable, short, and serializable.
 - Use `array` for repeatable items and `object` for grouped settings. Keep nested field names aligned with the prop shape and `defaultProps`.
-- Use `textarea` for multi-sentence copy. Use `text` only for short labels, headings, slugs, names, or plain strings that are not URLs, media, colors, icons, fonts, or menus.
+- Use `textarea` for multi-sentence copy. Use `text` only for short labels, headings, slugs, names, or plain strings that are not URLs, media, colors, icons, typography choices, or navigation lists.
 - Use `t(...)` for every editor-facing `label` in components, fields, nested
   `arrayFields` / `object.fields`, local blocks, and option lists. Add matching
   keys to `src/locales/en.json` at the same time.
@@ -589,7 +594,7 @@ Good component instructions explain:
 - Frequency: whether it should appear once, multiple times, or only near another section.
 - Composition: required neighboring content or local blocks, when relevant.
 
-- For icons, expose props with `{ type: "icon" }`, type values as `SudaLucideIconName`, render them with `SudaLucideIcon` from `@sudajs/theme-engine/runtime`, and store canonical Lucide names such as `"rocket"` or `"mouse-pointer-click"` (not `"lucide-rocket"`). Do not keep theme-local icon maps, emoji/icon switch statements, or custom SVG icon registries unless the theme truly needs a bespoke non-Lucide graphic.
+- For icons, expose props with `{ type: "icon" }`, type values as `SudaLucideIconName`, render them with `SudaLucideIcon` from `@sudajs/theme-engine/icons`, and store canonical Lucide names such as `"rocket"` or `"mouse-pointer-click"` (not `"lucide-rocket"`). Do not keep theme-local icon maps, emoji/icon switch statements, or custom SVG icon registries unless the theme truly needs a bespoke non-Lucide graphic.
 - Add optional field-level `ai.instructions`, `ai.required`, or `ai.exclude` when a prop needs generation guidance beyond its label and type.
 - Use `ai.exclude: true` only for structural or editor-only components, and still provide instructions explaining why AI must not generate them. `PageOutlet` is the standard example.
 

package/templates/theme/src/sections.tsx

@@ -1,8 +1,11 @@
-import type { SudaComponentConfig, SudaLucideIconName } from "@sudajs/theme-engine";
+import type { SudaComponentConfig } from "@sudajs/theme-engine";
+import {
+  SudaLucideIcon,
+  type SudaLucideIconName,
+} from "@sudajs/theme-engine/icons";
 import {
   getPostResource,
   resolveAsset,
-  SudaLucideIcon,
   type ThemePostResourceQuery,
   type ThemeRenderMetadata,
 } from "@sudajs/theme-engine/runtime";
@@ -245,6 +248,8 @@ export const FeaturedPosts: SudaComponentConfig<FeaturedPostsProps> = {
       fieldKey: "postList",
     });
     const posts = resource.posts;
+    const postHref = (post: (typeof posts)[number]) =>
+      post.url || (post.slug ? `/posts/${encodeURIComponent(post.slug)}` : "#");
     return (
       <section className="__SUDA_THEME_KEY__-section">
         <h2>{title}</h2>
@@ -258,7 +263,7 @@ export const FeaturedPosts: SudaComponentConfig<FeaturedPostsProps> = {
                 </p>
                 <h3>{post.title}</h3>
                 <p>{post.excerpt}</p>
-                <a href={post.url}>{post.title}</a>
+                <a href={postHref(post)}>{post.title}</a>
               </article>
             ))
           ) : (