game
이번 주말 스쿼드 게임 추천
한국어 템플릿 기반 예시 포스트. 주말에 가볍게 같이 볼 만한 게임 후보를 정리하고, 작은 인포 블록과 이미지 예시를 함께 넣었다.
Template Examples
This internal reference page shows the three intended authoring workflows: plain Markdown, richer MDX, and advanced template-based articles that still live inside the shared blog layout.
Openable Example Posts
These are real posts in the content collection, so contributors can click through and inspect working examples.
A richer MDX post showing the TechArticleTemplate, shared components, and multiple local images inside one post folder.
A general-purpose MDX article that uses the ClassicArticleTemplate and shows how to place multiple images throughout one game post.
A copyable advanced article example that uses a shared template for an HTML-like body while preserving the global blog shell.
Markdown Example
Best for most posts.
---
title: "Sample Markdown Post"
description: "Short summary"
pubDate: 2026-03-30
author: "Your Name"
section: "tech"
tags: ["reverse-engineering", "ida"]
draft: false
heroImage: ./cover.svg
---
# Body starts here
Regular Markdown works best for most posts.MDX Example
Best when you need callouts, figures, or reusable components.
---
title: "Sample MDX Post"
description: "Rich post with reusable components"
pubDate: 2026-03-29
author: "Your Name"
section: "game"
tags: ["co-op", "recommendations"]
draft: false
---
import Callout from "../components/Callout.astro";
<Callout title="Editor note" tone="info">
You can mix Markdown with components in MDX.
</Callout>HTML-Style Shared Template Example
Advanced use only. Keep the shared site chrome untouched.
---
title: "Template Based Post"
description: "Advanced shared article structure"
pubDate: 2026-03-28
author: "Your Name"
section: "game"
tags: ["diary", "action-rpg"]
draft: false
template: "casual"
---
import CasualArticleTemplate from "../../../templates/CasualArticleTemplate.astro";
<CasualArticleTemplate
hook="Shared shell, custom body."
quickFacts={[{ label: "Mood", value: "Relaxed" }]}
>
<section>
<h2>Body Section</h2>
<p>Use shared components instead of building a whole page.</p>
</section>
</CasualArticleTemplate>