Skip to content

feat: add 4 usage scenario tutorials#14

Merged
corylanou merged 1 commit intomainfrom
feat/tutorial-series
Mar 15, 2026
Merged

feat: add 4 usage scenario tutorials#14
corylanou merged 1 commit intomainfrom
feat/tutorial-series

Conversation

@corylanou
Copy link
Copy Markdown
Member

Summary

Adds the remaining 4 tutorials from the usage scenario series (#3):

  1. Training Materials — Building reusable course content with Hype's include system, snippets, and code execution. Covers modular structure, shared content, exercises, and multi-format output.

  2. Engineering Handbook — Automating internal docs: coding standards with compiled examples, onboarding scripts that run in CI, runbooks with validated commands, and auto-updating API docs via go doc.

  3. Release Notes Pipeline — Validated release notes with executable migration scripts, breaking change examples that show real compiler errors, dynamic version info, and CI integration for automated GitHub releases.

  4. AI-Assisted Authoring — Combining AI coding assistants with Hype's build-time validation. Generate → build → fix workflow, practical walkthrough, tips for effective AI prompting, and output stabilization.

Combined with the existing posts (Single-Source Docs, Deploying with Docker), this completes the 6 flagship tutorials.

Partial progress on #3

Test plan

  • hype blog build succeeds (18 articles, no warnings)
  • Each post renders at its expected URL
  • All posts appear in /blog/ listing
  • Homepage teaser shows latest 3 articles

- Training Materials: building reusable course content with includes
- Engineering Handbook: automated internal docs that stay in sync
- Release Notes Pipeline: validated release notes with executable examples
- AI-Assisted Authoring: combining AI speed with build-time validation

Partial progress on #3
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2b4bd2aaaf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

<cmd exec="bash scripts/migrate.sh"></cmd>

If you see errors at Step 2, check the
[troubleshooting guide](/docs/troubleshooting/).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point migration docs link to an existing troubleshooting page

This link targets /docs/troubleshooting/, but a repo-wide search shows no matching page or slug (the only troubleshooting reference is this line), so the published link will 404. Readers who hit migration errors are sent to a dead end instead of actionable guidance.

Useful? React with 👍 / 👎.

- name: Create GitHub Release
uses: softprops/action-gh-release@v1
with:
body_path: releases/${{ github.ref_name }}/RELEASE.md
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use unescaped GitHub expression in workflow body_path sample

The workflow example uses ${{ github.ref_name }} instead of ${{ github.ref_name }} for body_path. In a fenced code block, readers will copy these entities literally, so GitHub Actions will not interpolate the ref name and the example path is incorrect for real workflows.

Useful? React with 👍 / 👎.

@corylanou corylanou merged commit e6d79cc into main Mar 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant