chore: issue progression initiative blog

[exploreriii]

Fixes #205

Provides some information on the good first issue initiative i.e. the IPI (Issue Progression Initiative) <-- working title

Summary by CodeRabbit

• Documentation
  • Published a blog post about the Issue Progression Initiative at Hiero, outlining the four-tier difficulty framework (Good First Issue, Beginner, Intermediate, Advanced) for structured contributor development and career progression toward maintainer roles.

[netlify]

✅ Deploy Preview for hiero-open-source ready!

Name	Link
🔨 Latest commit	28f1d9e
🔍 Latest deploy log	https://app.netlify.com/projects/hiero-open-source/deploys/69af67d0b06b7800084f9d62
😎 Deploy Preview	https://deploy-preview-272--hiero-open-source.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR introduces a new blog post detailing the Issue Progression Initiative at Hiero. The article outlines a four-tier difficulty classification system (Good First Issue, Beginner, Intermediate, Advanced) for categorizing contribution opportunities, explains the initiative's structure, benefits, and role in developer retention and community growth.

Changes

Cohort / File(s)	Summary
Blog Post Addition content/posts/hiero_issue_progression_initiative.md	New blog post documenting the Issue Progression Initiative at Hiero, including front matter metadata, initiative overview, difficulty level descriptions, contributor pipeline progression, and practical benefits for attracting and retaining developers.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~15 minutes

Suggested labels

blog, status: awaiting-review

Poem

🐰 A post about progression, so thoughtful and clear,
From Good First Issues to maintainers dear,
Four levels of challenge for every keen soul,
Building pipelines of contributors—a beautiful goal! 🌟
Welcome, dear developers, come join the quest,
The Hiero way helps you become your very best!

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is minimal and lacks most required template sections such as detailed Changes Made, Screenshots, Checklist items (Tests, Documentation, Linting, Branch status), and Deployment Notes.	Expand the description to include all template sections: detailed Changes Made list, filled-out Checklist with testing/documentation/linting status, and any relevant Deployment Notes for the blog post.
Linked Issues check	❓ Inconclusive	While the blog post addresses the core requirement of documenting the Good First Issue initiative, it's unclear if a banner image and contact information for the Good First Issue team have been included as required.	Verify that the blog post includes a banner image and explicit contact information for the Good First Issue team as specified in issue #205's Expected Solution section.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: issue progression initiative blog' accurately describes the main change: adding a blog post about the Issue Progression Initiative.
Out of Scope Changes check	✅ Passed	The PR contains only a single new blog post file directly addressing the linked issue #205 requirements, with no extraneous or out-of-scope changes detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📋 Issue Planner

Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).

View plan for ticket: #205

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[lfdt-bot]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (2)

content/posts/hiero_issue_progression_initiative.md (2)

100-100: Clarify the command formatting.

The text \assign should be formatted with backticks for clarity, as it appears to reference a command or keyword.

💅 Proposed fix

-Create a new workflow that automatically assigns a user to an issue on commenting \assign.
+Create a new workflow that automatically assigns a user to an issue on commenting `\assign`.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/posts/hiero_issue_progression_initiative.md` at line 100, Update the
documentation line that describes the new workflow so the command is rendered as
inline code: wrap \assign in backticks (i.e., change \assign to `\assign`)
wherever it appears in the sentence "Create a new workflow that automatically
assigns a user to an issue on commenting \assign." to clearly indicate it's a
command/keyword.

---

61-66: Add language specifiers to code blocks.

The code blocks at lines 61, 85, 99, and 114 should have language specifiers for proper rendering and accessibility. Since these are example issue descriptions (plain text), consider using text or markdown as the language identifier.

📝 Proposed fix for code block language specifiers

For line 61:

-```
+```text
 Correct the spelling mistake in line 107:

Apply similar changes to code blocks at lines 85, 99, and 114.

Also applies to: 85-88, 99-102, 114-116

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/posts/hiero_issue_progression_initiative.md` around lines 61 - 66,
Add language specifiers to the four fenced code blocks that currently show plain
example issue text (the blocks containing the snippet starting "Correct the
spelling mistake in line 107:" and the similar blocks later) by changing their
opening fences from ``` to ```text (or ```markdown) so they render/accessibly;
also fix the spelling inside the referenced snippet where it reads "Good First
Isue" to "Good First Issue". Ensure you update the fences for the blocks around
the example lines (the blocks at the same locations as the snippets shown) and
correct the misspelling in the example content.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/posts/hiero_issue_progression_initiative.md`:
- Line 279: Add a single trailing newline to the end of the file content for
content/posts/hiero_issue_progression_initiative.md so the file ends with a '\n'
character (ensure the file's last byte is a newline and save the file so tools
detect the EOF newline).
- Line 77: Replace the awkward phrase "familiarity with the workflow repository"
in the sentence starting with "These assume" with a clearer alternative such as
"familiarity with the repository workflow" or "familiarity with the repository's
workflow" by updating that exact string in the content (the phrase "familiarity
with the workflow repository") to one of the suggested rephrasings.

---

Nitpick comments:
In `@content/posts/hiero_issue_progression_initiative.md`:
- Line 100: Update the documentation line that describes the new workflow so the
command is rendered as inline code: wrap \assign in backticks (i.e., change
\assign to `\assign`) wherever it appears in the sentence "Create a new workflow
that automatically assigns a user to an issue on commenting \assign." to clearly
indicate it's a command/keyword.
- Around line 61-66: Add language specifiers to the four fenced code blocks that
currently show plain example issue text (the blocks containing the snippet
starting "Correct the spelling mistake in line 107:" and the similar blocks
later) by changing their opening fences from ``` to ```text (or ```markdown) so
they render/accessibly; also fix the spelling inside the referenced snippet
where it reads "Good First Isue" to "Good First Issue". Ensure you update the
fences for the blocks around the example lines (the blocks at the same locations
as the snippets shown) and correct the misspelling in the example content.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ef982c13-c78a-4607-8361-2d5bfc40c396

📥 Commits

Reviewing files that changed from the base of the PR and between e0487db and 28f1d9e.

⛔ Files ignored due to path filters (1)

• static/images/IPI.png is excluded by !**/*.png

📒 Files selected for processing (1)

• content/posts/hiero_issue_progression_initiative.md

[aceppaluni]

LGTM!

I like the name!