@contentrain/astro-kit 0.23.4 → 0.23.6

package/components/contact-form/ContactForm.astro

@@ -4,8 +4,7 @@
 // StudioForm): its fields, spam protection and notifications live in Studio,
 // and submissions arrive there for review — no form plugin, no mail server.
 // Until the site is bound to a Studio project the form renders nothing and the
-// contact details still show — and a section left with its heading alone is not
-// drawn (a heading over a form that is not there). When the owner chose another home for forms at
+// contact details still show, and so do the section's heading and introduction (only the form goes). When the owner chose another home for forms at
 // migration (site.config.ts `features.forms`), the same place holds a form
 // that posts to their form service, an address to write to, or a link to the
 // form on WordPress.
@@ -71,7 +70,7 @@ interface Props {
 const { model, heading, intro, formHeading, details = [], layout, align, tone, id = 'contact' } = Astro.props
 // Nothing to render (Studio not bound yet): a split would leave an empty column — the details stand alone.
 const formShown = formHome(model) !== null
-const bare = contactSectionBare({ formShown, intro, details })
+const bare = contactSectionBare({ formShown, heading, intro, details })
 const s = contact({ layout: formShown ? layout : 'stacked', align, tone })
 const headingId = heading ? `${id}-title` : undefined
 // A description list needs a term for every detail; an icon list carried from the source has values only.

package/components/contact-form/contact-form.ts

@@ -1,8 +1,9 @@
 // When the contact section has nothing to show. Its form is drawn only where a home for it exists (Studio bound, the
 // WordPress page known, a service address that is https); until then the section stands on its heading, introduction
-// and details. A section left with a heading ALONE titles a form that is not there — the page would print "Tell us about
-// your project" over empty space — so it is not drawn at all, and appears with its form once the form has a home.
+// and details. The source's words are never dropped with the form: a page whose contact section holds only a heading
+// ("Bize yazın") keeps it, because the text is the site's own and a fidelity gate compares it. Only a section with no
+// heading, introduction or details at all — nothing to print — is left out, and appears with its form once it has a home.
 
-export function contactSectionBare(input: { formShown: boolean, intro?: string | undefined, details?: readonly unknown[] | undefined }): boolean {
-  return !input.formShown && !input.intro && !(input.details?.length ?? 0)
+export function contactSectionBare(input: { formShown: boolean, heading?: string | undefined, intro?: string | undefined, details?: readonly unknown[] | undefined }): boolean {
+  return !input.formShown && !input.heading && !input.intro && !(input.details?.length ?? 0)
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contentrain/astro-kit",
-  "version": "0.23.4",
+  "version": "0.23.6",
   "license": "MIT",
   "description": "Copy-in Astro components for Contentrain sites (shadcn model): typed props, tailwind-variants, zero JavaScript by default — with a machine-readable catalog",
   "type": "module",
@@ -42,7 +42,7 @@
     "mapping"
   ],
   "dependencies": {
-    "@contentrain/types": "1.46.0"
+    "@contentrain/types": "1.47.0"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",