Blog post for my contribution in CCPS Portal during FOSSOVERFLOW25-26

[Kr-Utkarsh-01]

Wrote a blog post detailing my contribution in CCPS Portal during FOSSOVERFLOW25-26

Summary by CodeRabbit

• Documentation
  • Published a new blog post documenting the CCPS Portal project and its features, including job extraction automation, enhanced job insights, application tracking, improved admin tools, and pagination functionality.

[vercel]

@Kr-Utkarsh-01 is attempting to deploy a commit to the OpenLake_Website Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

A new blog post documenting the CCPS Portal project was added, detailing the author's contributions including job extraction pipelines, scheduling systems, frontend features, application tracking, admin improvements, and technical implementations with learning outcomes.

Changes

Cohort / File(s)	Summary
Blog Content content/blog/CCPSPortal_KumarUtkarsh.md	New blog post describing CCPS Portal project contributions, including automated job extraction, background scheduling, frontend enhancements, application tracking, admin UX improvements, and technical challenges encountered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

📝 A new post hops into the blog so bright,
CCPS Portal shines in the spotlight,
Pipelines and schedulers, features galore,
A rabbit's tale from Kumar to explore! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately and clearly summarizes the main change: adding a blog post documenting the author's contributions to the CCPS Portal project during FOSSOVERFLOW25-26, which matches the changeset content.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

content/blog/CCPSPortal_KumarUtkarsh.md (1)

17-17: Fix heading hierarchy to improve document structure.

The document has heading level violations where h3 headings appear without intervening h2 headings. Proper heading hierarchy improves accessibility, SEO, and document outline generation.

📝 Proposed fix for heading structure

 # My Contributions 💻
 I focused on building a robust data pipeline and enhancing the user experience for both students and administrators.
 
-### Core Features Implemented
+## Core Features Implemented
 * **Automated Job Extraction Pipeline:** Built API integrations with Adzuna and Jooble to scrape high-tier (> 12 LPA) IT and Engineering roles.

 * **Applications Pagination:** Added "Show More" pagination in the Applications page to improve user navigation.
 
-### Technical Challenges & Bug Fixes
+## Technical Challenges & Bug Fixes
 * **Data Normalization:** Handling diverse data structures (like raw HTML descriptions vs. plain text) from different APIs required building robust custom parsers.

 ---
 
-### These are few of the features in action:
+## Features in Action
 <img width="1919" height="1079" alt="image" src="https://github.com/user-attachments/assets/79c065ea-5df0-4769-90c1-934fc1389e46" />

Also applies to: 26-26, 48-48

🤖 Prompt for AI Agents

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

In `@content/blog/CCPSPortal_KumarUtkarsh.md` at line 17, Some h3 headings lack a
preceding h2, breaking heading hierarchy; update any top-level section headings
(for example change "### Core Features Implemented" and the other two similar
h3s flagged) to h2 ("## ...") so every h3 has an appropriate h2 parent, or
insert an H2 wrapper section above them if they are subsections; locate the
headings by their text (e.g., "Core Features Implemented") and adjust the
markdown levels accordingly to restore a proper H2 → H3 structure.

🤖 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/blog/CCPSPortal_KumarUtkarsh.md`:
- Line 7: Update the bio sentence to hyphenate the compound adjective by
changing "full stack Web Developer" to "full-stack Web Developer" in the
sentence containing "Hello everyone, I am [**Kumar Utkarsh**] ..." so the
compound adjective is correctly formatted before the noun.

---

Nitpick comments:
In `@content/blog/CCPSPortal_KumarUtkarsh.md`:
- Line 17: Some h3 headings lack a preceding h2, breaking heading hierarchy;
update any top-level section headings (for example change "### Core Features
Implemented" and the other two similar h3s flagged) to h2 ("## ...") so every h3
has an appropriate h2 parent, or insert an H2 wrapper section above them if they
are subsections; locate the headings by their text (e.g., "Core Features
Implemented") and adjust the markdown levels accordingly to restore a proper H2
→ H3 structure.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ab964db0-924c-442d-9ae5-08d05ec47403

📥 Commits

Reviewing files that changed from the base of the PR and between 3bbfd92 and 7808d20.

📒 Files selected for processing (1)

• content/blog/CCPSPortal_KumarUtkarsh.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Hyphenate the compound adjective "full-stack".

The term "full stack" should be hyphenated when used as a compound adjective before a noun.

✏️ Proposed fix

-Hello everyone, I am [**Kumar Utkarsh**](https://www.linkedin.com/in/profile-kumar-utkarsh/) - A full stack Web Developer and an undergraduate pursuing B.Tech in CSE at IIT Bhilai
+Hello everyone, I am [**Kumar Utkarsh**](https://www.linkedin.com/in/profile-kumar-utkarsh/) - A full-stack Web Developer and an undergraduate pursuing B.Tech in CSE at IIT Bhilai

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Hello everyone, I am [**Kumar Utkarsh**](https://www.linkedin.com/in/profile-kumar-utkarsh/) - A full stack Web Developer and an undergraduate pursuing B.Tech in CSE at IIT Bhilai
	Hello everyone, I am [**Kumar Utkarsh**](https://www.linkedin.com/in/profile-kumar-utkarsh/) - A full-stack Web Developer and an undergraduate pursuing B.Tech in CSE at IIT Bhilai

🧰 Tools

🪛 LanguageTool

[grammar] ~7-~7: Use a hyphen to join words.
Context: ....com/in/profile-kumar-utkarsh/) - A full stack Web Developer and an undergraduate...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

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

In `@content/blog/CCPSPortal_KumarUtkarsh.md` at line 7, Update the bio sentence
to hyphenate the compound adjective by changing "full stack Web Developer" to
"full-stack Web Developer" in the sentence containing "Hello everyone, I am
[**Kumar Utkarsh**] ..." so the compound adjective is correctly formatted before
the noun.