Instruction file imported from jonlwowski012/jonathan-lwowski-personal-website (.github/instructions/insights-content.instructions.md). Copyright stays with the author.

Insights content rules

• Create articles at content/insights/<slug>.md by default. Use .mdx only when the article needs JSX or an approved component.
• Filenames and slug must be identical lowercase kebab-case values. Never create an article registry.
• Frontmatter must contain only title, description, date, tags, slug, featured, and draft.
• Use a quoted ISO date string ("YYYY-MM-DD"), a YAML list of short tags, and explicit boolean featured and draft values.
• Keep description concise and useful as search/social metadata. Write original technical prose and maintain a logical heading hierarchy beginning at ##.
• Local article images belong under public/images/insights/ and use root-relative paths. Give every image meaningful alternative text. Markdown images are rendered through Next Image; include explicit width and height attributes in MDX when their source ratio is not 16:9.
• Use .mdx only for the standard Markdown syntax unless a reusable approved component already exists under src/components/content/.
• Set draft: true for work in progress. Drafts appear locally but are excluded from production builds.
• Run pnpm lint, pnpm typecheck, pnpm build, and pnpm test:e2e after modifying published content or its rendering pipeline.