[add] a new blog

[apsinghdev]

Summary by CodeRabbit

• Documentation

  • Published new blog post on OSS projects and software sustainability.
  • Updated hyperlink in existing blog post.

• Chores

  • Updated social media profile links.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
opensox-website	Ready	Preview, Comment	Jun 15, 2026 11:37am

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates Twitter and Instagram profile URLs in the blog socials component and in one existing blog post, and adds a new MDX blog post titled "why 100% software isn't good" covering OSS project labeling concepts, tag-accuracy challenges, and a direction toward opensox pro.

Changes

Blog Content and Social URL Updates

Layer / File(s)	Summary
Social link URL updates apps/web/src/app/(main)/blog/blog-socials.tsx, apps/web/src/content/blog/how-i-started-opensox.mdx	Twitter and Instagram href values updated in the socials array; the "my first sale" hyperlink target in the existing post is changed to a different X/Twitter URL.
New blog post apps/web/src/content/blog/why-100-percent-software-isnt-good.mdx	New MDX post added with frontmatter (title, date, description, author, tag) and 70 lines of body text describing the OSS labeling concept, tag-accuracy problem, and opensox pro direction.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• apsinghdev/opensox#387: Modifies the same how-i-started-opensox.mdx blog file, directly overlapping with the X/Twitter hyperlink target change in this PR.

Poem

🐇 A tweet link here, a gram link there,
New words on the blog floating through the air,
"100% software" — now that's a thought,
The bunny typed fast and the new post was wrought!
Small and steady wins the race, they say —
Opensox hops forward another day! 🧦

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title describes adding a new blog post, which aligns with the primary change (new MDX blog file), though it is quite generic and doesn't specify which blog post or its topic.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add/b156

---

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.}

[coderabbitai]

🧹 Nitpick comments (2)

apps/web/src/app/(main)/blog/blog-socials.tsx (1)

3-40: ⚡ Quick win

Consider renaming the socials array to SOCIALS to follow UPPER_SNAKE_CASE convention for constants.

Per coding guidelines, constants should use UPPER_SNAKE_CASE. Since this is a module-level constant, renaming would align with the convention.

✨ Proposed refactor

-const socials = [
+const SOCIALS = [
   {
     label: "Twitter",
~
   {
     label: "YouTube",
~
   {
     label: "Instagram",
~
   {
     label: "Discord",
~
 ];

 export default function BlogSocials() {
   return (
     <div className="flex items-center gap-3">
-      {socials.map((s) => (
+      {SOCIALS.map((s) => (

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/src/app/`(main)/blog/blog-socials.tsx around lines 3 - 40, Rename
the `socials` constant to `SOCIALS` to adhere to the UPPER_SNAKE_CASE naming
convention for module-level constants. Update the variable declaration and any
references to this constant throughout the file to use the new uppercase name.

Source: Coding guidelines

apps/web/src/content/blog/why-100-percent-software-isnt-good.mdx (1)

9-11: 💤 Low value

Apply standard hyphenation for compound adjectives before nouns.

Per grammar conventions, compound adjectives that precede nouns should be hyphenated. Several instances need fixing:

• Line 9: "open source projects" → "open-source projects"
• Line 11: "open source contributor" → "open-source contributor" and "open source project" → "open-source project"

Consider applying the same fix to line 43 ("high-level architecture") and line 79.

🔧 Proposed fixes

-what if i scrap all the open source projects, filter them and then manually labels them like "this oss project hires contributors", "this project is active", "this project has great maintainers".
+what if i scrap all the open-source projects, filter them and then manually labels them like "this oss project hires contributors", "this project is active", "this project has great maintainers".

-so that a new open source contributor doesn't have to waste weeks of his/her time to find a suitable open source project to contribute.
+so that a new open-source contributor doesn't have to waste weeks of his/her time to find a suitable open-source project to contribute.

Also apply similar fixes to:

• Line 43: "high level architecture" → "high-level architecture"
• Line 79: "open source projects" → "open-source projects"

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/src/content/blog/why-100-percent-software-isnt-good.mdx` around
lines 9 - 11, Apply standard hyphenation rules to compound adjectives that
precede nouns in the markdown file. Specifically, replace all instances of "open
source" with "open-source" and "high level" with "high-level" where these
phrases appear as adjectives before nouns (such as in "open-source projects",
"open-source contributor", and "high-level architecture"). This applies to all
occurrences throughout the file where compound adjectives precede their nouns.

Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/web/src/app/`(main)/blog/blog-socials.tsx:
- Around line 3-40: Rename the `socials` constant to `SOCIALS` to adhere to the
UPPER_SNAKE_CASE naming convention for module-level constants. Update the
variable declaration and any references to this constant throughout the file to
use the new uppercase name.

In `@apps/web/src/content/blog/why-100-percent-software-isnt-good.mdx`:
- Around line 9-11: Apply standard hyphenation rules to compound adjectives that
precede nouns in the markdown file. Specifically, replace all instances of "open
source" with "open-source" and "high level" with "high-level" where these
phrases appear as adjectives before nouns (such as in "open-source projects",
"open-source contributor", and "high-level architecture"). This applies to all
occurrences throughout the file where compound adjectives precede their nouns.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7e5850d7-a6b2-41a0-8aa0-3b2c0a0ad472

📥 Commits

Reviewing files that changed from the base of the PR and between 9496c9c and bb49e7b.

📒 Files selected for processing (3)

• apps/web/src/app/(main)/blog/blog-socials.tsx
• apps/web/src/content/blog/how-i-started-opensox.mdx
• apps/web/src/content/blog/why-100-percent-software-isnt-good.mdx