add-blog-post

name	add-blog-post
description	Add a new blog post to the Jesus Of Israel website source repository and rebuild the site. Use for add blog post, new article, publish post, update posts.json, add post images, and validate route rendering.
argument-hint	Post title, publish date, author, tags, route path, and whether images are included

Add Blog Post

When To Use

• Add one new post to the Jesus Of Israel website source data.
• Update website content directly in this authoritative repository.
• Insert a new post into the archive feed.

Inputs

• Post title
• Route path (example: /2026/05/18/sample-post/)
• Published date/time (ISO format preferred)
• Author name
• Tag list
• HTML content body
• Optional featured/inline images

Decision Points

1. Source of content:

• This repository IS the authoritative source. Add all content directly here via JSON edits.
• This is the only workflow for adding or updating content.

2. Images present:

• If post includes inline images, place files in content/images/<post-slug>/ and reference /images/<post-slug>/<file> in HTML.
• If no images are needed, skip image-manifest updates.

3. Metadata completeness:

• If author/tags are unknown, use conservative defaults and keep fields structurally valid.

Procedure

1. Prepare post metadata and route.

• Ensure route is unique and ends with /.
• Create a slug from the route segment for image folder naming.

2. Add or update post item in data.

• Edit data/posts.json.
• Insert a new object with at minimum:
  • type: post
  • routePath
  • title
  • published
  • author
  • tags (array)
  • html (string)
• Keep fields consistent with existing post objects used by src/App.jsx.

3. Handle images (if applicable).

• Add inline images under content/images/<post-slug>/.
• Use web paths in HTML like /images/<post-slug>/01.jpg.
• If adding shared source-style assets, place them under content/images/site-assets/.

4. Keep manifests aligned when needed.

• If tracking source-to-local image mapping, update data/images.json accordingly.
• If summary counts are used operationally, update data/summary.json or regenerate via scrape/migrate.

5. Build and validate.

• Run npm run build.
• Confirm build succeeds.
• Run npm run dev or npm run preview and verify:
  • Homepage shows the new post in expected sort order.
  • Route renders post content.
  • Tag and author links include the new post.
  • Images resolve correctly.

Completion Checks

• JSON syntax valid in data/posts.json.
• Route is reachable and not shadowed.
• No console/runtime errors on post page.
• Build passes without failures.

Recovery Steps

• If page renders blank, verify required fields are non-null strings/arrays where expected.
• If content load fails, check /data/posts.json is reachable in the active environment.
• If images do not render, verify file exists at copied public/images/... path after build.

Repo-Specific Notes

• Build pipeline copies data/ -> public/data/ and content/images/ -> public/images/ via scripts/build.mjs.
• This repository is the single source of truth—changes here are deployed directly to production.