Guidelines

Groundhog Learning — Content Guidelines#

There are two post formats used across Groundhog Learning social/course content:

Format	Purpose
Journey	Teaching posts — a series of slides explaining a concept
Update	Course announcement posts — promote a new module or course

Every series follows a 3-slide structure: Cover → Content slide(s) → End.

Episode number (#001, #002, etc.)
Post title (taken from the .md frontmatter title field, stripped of the episode number prefix)

Each heading + body pair in the .md file maps to one content slide. The markdown structure is:

Line 1 of heading
Line 2 of heading
Body paragraph text

Heading always splits across two lines — line 1 is the punchy hook, line 2 is the elaboration or contrast
Body is a short explanatory paragraph (2–4 sentences)
Optional section label — used when the heading is a sub-concept of a parent topic (e.g., label “Programming languages” above heading “Bridge the gap”)

Reuses the content of the last content slide. No new content needed.

Course name (repeated from cover)
Heading: what the viewer will do (e.g., What You'll Do)
Body: 2–4 checklist items listing the concrete tasks/steps in the module (e.g., Install Visual Studio Code, Create a C# Project to start coding)

Choose the appropriate variant based on what the content is communicating:

Variant	When to use
Standard	Default — heading + body paragraph, no extras
Hint Box	When there’s a warning or important caveat to call out separately
Emojis	When the body describes a step-by-step sequence that can be illustrated with emojis
Diagrams	When the body describes a conceptual flow between distinct entities (e.g., human → code → binary → computer)
Code Blocks	When the body compares the same operation across multiple programming languages
Activity	When the slide is an interactive challenge — replaces the heading/body with a full visual activity and a short instruction line below

The heading always follows a two-line format:

Line 1 — shorter, punchier concept hook
Line 2 — elaboration, contrast, or completion

Examples:

Keep headings short. Line 1 should feel like it could stand alone as a provocative statement.

Slide count per Journey post:

Source format (from .md files):

Heading line 1
Heading line 2
Body text

Pull episode number and title from the .md frontmatter
Map each heading/body block to one content slide
Write the heading as two lines: hook / elaboration
Choose the right variant for each slide based on content type
Add a section label above the heading where the slide belongs to a broader topic
End slide reuses last slide’s content — no new writing needed

Cover: course name + announcement title
Content slide: course name + “What You’ll Do” heading + 2–4 checklist action items
End slide: course name + full course title + URL