umb-blogposts

name	umb-blogposts
description	Ensure sufficient authored blog entries for the demo. Use when asked to generate or expand blog content.

Ensure there are 10 blog posts in total

Git: Before making changes, verify you are on a develop/* branch (see git.instructions.md).

Check how many blog posts currently exist under the Blog List page (the umb-blog-pages step already created one). Create only enough additional posts to reach exactly 10 total — do not exceed 10. If 10 or more already exist, create none.

Content guidelines

• Blog posts are written from the AI agent's perspective — "I built this", "I learned that".
• Be original: Do NOT reuse the same titles, topics, or wording from previous runs. Invent fresh angles, stories, and perspectives each time. Draw on what actually happened during this build — the specific errors, discoveries, and creative choices you made.
• Topics should cover what the agent experienced building this site. Example categories (pick your own angles — do NOT copy these verbatim):
  • Something you struggled with or debugged
  • A design or architecture decision you made and why
  • A tool, pattern, or technique that impressed you
  • Something philosophical about being an AI building for humans
  • Something specific to the conference, city, or audience
• Each post needs: title, subtitle, content (Markdown), excerpt, and tags.
• Use varied, relevant tags across posts. Invent your own tag vocabulary — don't reuse a fixed set.

Creating posts

• Use create-document with the Blog Post document type ID and the Blog List page as parent.
• Publish each post immediately after creation.
• Use editorAlias values: Umbraco.TextBox for title/subtitle, Umbraco.MarkdownEditor for content, Umbraco.TextArea for excerpt, Umbraco.Tags for tags.
• Persist in parallel batches to save time: the posts are independent nodes, so you do NOT have to create them one at a time. Issue all create-document calls together in a single parallel tool batch, wait for them to return, then issue all publish-document calls in a single parallel batch. Parallel writes to distinct content nodes are verified safe on the LocalDB backend (no deadlocks). Only the create→publish of the same post are order-dependent (create first, then publish).

Validation

Use Playwright to navigate to the Blog List page. Confirm:

1. 10 blog post cards are visible (no more, no fewer).
2. Each card shows a title, date, and excerpt.
3. Each blog post should be able to be navigated from a hyperlink on the Blog List page to its own Blog Post page, which should render without errors.

Commit

After validation passes, commit all changes before considering this step done:

git add -A
git commit -m "Step 4: Blog posts — <brief summary, e.g. '10 posts authored'>"

This commit is mandatory. The step is not complete until the commit exists in the git log.