src/pages/plataforma-thinkwise

This directory powers both the overview page (/plataforma-thinkwise/) and every capability detail route (/plataforma-thinkwise/[slug]/). Use it as the reference when adding or fixing logic in the other collections (modelos-de-adocao, perspectivas-sobre-a-plataforma, temas-de-modernizacao, conceitos-de-desenvolvimento follow the same pattern).

Overview page (index.astro)

• Pulls copy and aside defaults from getLandingPageFrontmatter("plataforma-thinkwise").
• Renders:
  • SectionIntro with title, lead, excerpt.
  • Optional two-column block (article.content + AsideCards) when the landing meta defines an aside.
  • HeroBackplate CTA hardcoded for the platform prompt.
  • Grid of capabilities built from src/data/plataformaThinkwise.ts (capabilities array) rendered via CollectionGrid + CollectionCard + IllustrationThumb.
• CSS keeps the illustration as a masked backdrop. Reuse the .content-visual pattern when mirroring this layout elsewhere.

Detail page ([slug].astro)

Data flow

1. getStaticPaths loads every content.md under src/content/plataforma-thinkwise/**/ and also any slugs that exist only via meta.yaml (ensures cards defined in data but not yet authored still build).
2. For each page:
   • entry (Markdown module) provides markdown body + frontmatter when the file exists.
   • capabilities.find((c) => c.slug === rawSlug) supplies fallback metadata and relations even if the Markdown module is missing.
   • getLandingPageFrontmatter("plataforma-thinkwise") exports meta used as CTA fallback.

Rendering steps

1. SectionIntro displays title/lead/excerpt (from frontmatter or capabilityData fallback).
2. Body slot: wraps the Markdown content with the same illustrated backdrop pattern used on the overview page.
3. AsideCards receives finalAsideSections, built by combining:
   • Item-level aside definitions from meta.yaml.
   • Landing CTA fallback if no CTA is present (ensures /contato?c=plataforma-thinkwise&s={slug} is always reachable).
4. relationSections iterates through the relations defined in meta.yaml and uses mapRelations() with the prebuilt relationMaps. It excludes the current slug to avoid self-references.
5. Related cards render inside CollectionGrid. Each card adds a Tag slot that names the originating collection. The label/color pair is resolved through collectionInfo (landing metadata for each top-level section).

Behavior notes

• CTAs: The CTA label comes from either the item aside or, as fallback, from the landing meta (first entry that contains .cta). The href always includes both c and s.
• Relations: Accept only the refs documented in src/data/utils.ts. When new relation types appear, update relationMaps, the helper map inside this page, and the documentation.
• Illustrations: Every detail view seeds IllustrationThumb with the slug so cards and hero banners remain deterministic between builds.
• SEO: publishDate is taken from frontmatter or the data entry, allowing Layout to emit Article JSON-LD.

Extending this pattern

If you introduce another collection that needs the same features:

1. Copy the structure from this directory but extract duplicated code into helpers (e.g., a shared buildAsideSections function).
2. Document the new behavior (and any deviations) in a README inside the new directory.