← Back to reports library

Content intake via GitHub issue forms and automation

This repository now accepts fully sourced briefs, guides, and tips through a single GitHub issue form. When you submit complete, citation-backed content, automation will open a pull request that adds the JSON file under the correct directory so it can flow…

Editorial Operations · Coverage focus 2025 · Updated December 12, 2025

This repository now accepts fully sourced briefs, guides, and tips through a single GitHub issue form. When you submit complete, citation-backed content, automation will open a pull request that adds the JSON file under the correct directory so it can flow through the static build.

How to submit content

  1. Go to New issue in GitHub and choose Submit new content (brief/guide/tip).
  2. Complete every field with accurate information: - Content type (Brief, Guide, or Tip). - Title, slug, and published date (YYYY-MM-DD). - Pillar and at least two topics. - Reading time in minutes (positive integer). - Summary and full HTML body content (no placeholders). - Sources listed one per line as Title — URL — brief note with real, verifiable links.
  3. Submit the issue. The issue is labeled content-submission automatically.

What happens next

  • A GitHub Actions workflow validates the submission (content type, pillar, date format, reading time, topic count, and source formatting), then materializes the JSON file in the matching directory:
  • Briefs → zephtech-site/content/feed/<published>-<slug>.json
  • Guides → zephtech-site/content/guides/<published>-<slug>.json
  • Tips → zephtech-site/content/tips/<published>-<slug>.json
  • A branch is created as <type>/<issue>-<slug> and a pull request targets the default branch. The issue receives a comment with the branch name and file path.
  • Reviewers inspect the generated JSON, make any edits, and merge the PR. The normal python scripts/build.py process will pick up the new content during deployment.

Validation rules enforced by automation

  • Content type must be Brief, Guide, or Tip.
  • Published date must follow YYYY-MM-DD and should reflect the real-world event date.
  • Pillar must be one of the eight supported pillars.
  • Reading time must be a positive integer.
  • At least two topics are required.
  • Each source line must include a title, a valid URL, and a short note; invalid URLs or missing pieces halt the workflow.
  • Slugs must be lowercase with hyphens only.

Notes on data quality

  • Do not use synthetic, mock, or placeholder content. All submissions must be fully sourced and publication-ready.
  • The workflow does not rewrite content; it trusts the submitted text. Treat the form as production input and verify citations before submitting.