chore/docs: add initiatives docs in markdown with pictures

[planksconstant]

Summary

Blog post for the webiste refrence #177 #197

Type of change

• Bug fix (non-breaking change that fixes an issue)
• [] New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that changes existing behaviour)
• New / updated problem (challenge JSON)
• Documentation only
• Chore / refactor / tooling

Related issues

#177

Closes #

How was this tested?

Checklist

• I ran the checks locally on Node 22 and they pass: npx tsc --noEmit, npm run lint, npm run test, npm run build
• I did not commit unrelated package-lock.json changes (see CONTRIBUTING.md - the native-binding gotcha)
• My change is focused and single-purpose
• I added / updated tests where it made sense
• I updated documentation where needed
• For UI changes: it looks correct in both light and dark mode
• For problems: npm run challenges:validate passes and hidden tests are strong
• I did not commit any secrets

Notes for reviewers

some of the events like Praxis did not have a writeup i could get content from some of the members who attended the hackathon and update it

• picture size is minimal as mentioned in the previous pr
• i am concerned about how the blog looks as it just reads like plain text might be a limtation from our SSG engine or skill issue from my side let me know if i could have cleaner/aesthetic blog writeup

[vercel]

@planksconstant is attempting to deploy a commit to the barunaniket-9400's projects Team on Vercel.

A member of the Team first needs to authorize it.

[barunaniket]

@shivanshpap please verify it.

[planksconstant]

Looks Peak, i Might review and fix the blog content again thanks @hagemaruwu :)

[planksconstant]

@shivanshpap @barunaniket Any Nitpicks?

[shivanshpap]

Hey @planksconstant , could you please make the following updates ?

1. LeetCode 101 Page

• Please check the current formatting on the LeetCode 101 page.
• As shown in the attached image, all the content is currently appearing as separate lines.
• It should be properly formatted into paragraphs/sections with appropriate spacing so that the content is easier to read.

2. AlgoHunt Page

• Replace the current dummy winner data with the actual winners.
• Please add the real winners' names, details, and photos.
• I can provide the winner information and photos whenever required.
• Just remember to keep winners of each tracks seperate.

3. Praxis Section
   Please update the following details:

• Arrivals: Change from 800+ arrivals
• Venue: Change from Main Auditorium to MRD Student Centre
• Prize Pool: Update it to the correct prize pool amount
• Winners: Replace the current winners with the actual winners

change the photos of winners and use their team names
I can provide the correct prize pool, winner details, and photos whenever required.

Thanks!

[shivanshpap]

@planksconstant also improve the description for all the events, need to change the timeline part in praxis as right now it does'nt explain much about the event. Also, attaching the image here

[shivanshpap]

Hey @planksconstant thanks for working on this and taking the initiative to compress the images to .webp!

I ran the changes locally and reviewed them against our Events & Initiatives Handbook. There are a few blockers and handbook guidelines that need to be addressed before we can merge this:

1. 🚨 Critical: Duplicate winners key in algohunt.md (Fails Tests)
   In content/initiatives/events/algohunt.md, the winners: key is declared twice (at line 23 and line 63).

In YAML, duplicate keys throw a fatal parse error:
[initiatives] ⚠️ Error reading algohunt.md: duplicated mapping key at line 63
This causes buildInitiativesManifest() to fail parsing the file, dropping AlgoHunt completely from the manifest and causing 4 tests in src/lib/initiatives.test.ts to fail.
Fix: Please merge both tracks under a single winners: block following the template in the handbook (Page 4). Also make sure 1st place champions have their heroImage: and experience: fields set so the Spotlight Hero card renders properly.
2. 📁 Image Directory Convention (public/events/)
According to Principle #2 in our handbook, all event photos should live under public/events/ and be referenced as /events/....
Fix: Please move the compressed images from public/eventsCompr/ into public/events/ (you can overwrite the old uncompressed ones or add .webp files there), remove the public/eventsCompr/ folder, and update the paths in your markdown files.
3. 📄 Revert initiatives.manifest.json (Rule #0)
As per Rule #0 in the handbook, never manually commit src/app/initiatives/initiatives.manifest.json.
The manifest is auto-generated on build/dev by buildInitiativesManifest() in next.config.ts. Committing manual edits causes merge conflicts and overwrites.
Fix: Please revert src/app/initiatives/initiatives.manifest.json from this PR (git checkout origin/main -- src/app/initiatives/initiatives.manifest.json).
4. ✍️ Content Formatting
praxis.md: The description is currently a single run-on sentence without punctuation. Could you structure it with headings (## About Praxis, etc.) and bullet points similar to leetcode-101.md?
(Regarding your note about the blog reading like plain text): This is because our Tailwind configuration doesn't have the @tailwindcss/typography plugin installed yet for the prose class. Don't worry about that for this PR—we'll address the blog prose styling in a separate follow-up PR!

Verification
Once you make these adjustments, please run:
npm run test

Ensure all 72 tests pass, then push the changes and request another review. Thanks again!

[planksconstant]

so the tests have passed
some details i need to mention
heroimage for advanced track in content/initiatives/events/algohunt.md was available from a participants linkedin swalpa stalking but was not able to find for the easy track let me know what needs to be done

src/app/initiatives/initiatives.manifest.json is reverted sorry for the issues with this
\events\- the pictures have been moved to the prescribed events folder

praxis.md the fix has been done LGTM but can be changed if required

[shivanshpap]

Hey @planksconstant , thanks for the update. The tests have passed on my end.

A few of the requested changes are still pending:

1. Event descriptions
   Please update the descriptions for each of the events once again. Right now, the descriptions look quite short compared to what we need. Please make them more detailed and informative while keeping the formatting clean and consistent across all the event pages.

• LeetCode 101: Use the detailed description/content I shared earlier and format it properly into paragraphs and sections.
• AlgoHunt: Expand the description and replace the dummy winner details with the actual winners and their photos.
• Praxis: Expand the description and update the relevant event details, including arrivals, venue, prize pool, and winners.

2. Praxis timeline
   The Praxis timeline also still needs to be updated as discussed.

3. Photos / assets
   Here are the photos you asked for:

• LeetCode 101: [Google Drive folder]
• Praxis: [Google Drive folder]
• AlgoHunt: [LinkedIn post]

For AlgoHunt, you can use the images from the LinkedIn post for the hero/winner images as required.

The changes to src/app/initiatives/initiatives.manifest.json and the events/ picture folder are fine. The main things remaining are the event descriptions, Praxis timeline/details, and replacing the dummy winner information.

Thanks!

[planksconstant]

can i get the details of the winners of praxis i was not able to find that either in the google drive or the orgianisation linkedin page :(

LeetCode 101: Use the detailed description/content I shared earlier and format it properly into paragraphs and sections.

i am using the required markdown i am not really sure what needs to be done in this change but anyways i restructured it

LeetCode 101 is our flagship mentorship program designed to help students build a strong foundation in data structures, algorithms, and problem-solving.

## What is LeetCode 101?

  LeetCode 101 is a guided learning program focused on developing the problem-solving habits required for competitive programming and technical interviews.

  Instead of treating problem solving as a collection of tricks to memorize, the program focuses on understanding the patterns behind problems and learning how to recognize those patterns when encountering something new.

## What We Focus On

### Data Structures

  We build a practical understanding of the data structures that appear frequently in programming problems. The emphasis is not simply on learning what a data structure is, but on understanding when and why it should be used.

### Problem-Solving Patterns

  A major part of LeetCode 101 is learning to recognize recurring patterns. Students learn to break unfamiliar problems down, identify useful structures, and develop systematic approaches rather than memorizing individual solutions.

### Complexity and Optimization

  Students compare different approaches and examine their time and space complexity, learning how to identify unnecessary work and improve solutions as input sizes grow.

## Learning Through Problems

  The program is built around solving problems rather than passively watching explanations. Students learn to understand the problem, break it into smaller parts, develop possible approaches, implement a solution, analyze its complexity, and review alternative approaches.

## Mentor-Led Reviews

  Mentorship is a core part of the program. Solutions are reviewed beyond simply checking whether they pass, with attention given to the chosen approach, implementation, complexity, clarity, and possible improvements.
## Editorial Practice

  Students learn how to read and write problem editorials by identifying the key observation, explaining the algorithm, and reasoning about its complexity.

## From Foundations to Competitive Programming

  LeetCode 101 provides the foundation for students who want to continue into deeper competitive programming and technical interview preparation. The goal is to develop consistent problem-solving habits, recognize algorithmic patterns, analyze complexity, learn from failed approaches, and communicate technical reasoning clearly.

## Start With the Problem, Not the Solution

  Problem solving is a skill that improves through deliberate practice. Every difficult problem is an opportunity to identify a new pattern, question an existing approach, and become better at breaking down unfamiliar problems.

  LeetCode 101 provides the structure, mentorship, and practice environment to make that process consistent.

Praxis timeline The Praxis timeline also still needs to be updated as discussed.
this has been changed will be visible in a subsequent push

Mentors visible in the praxis page- do we need this judges and mentor thing in praxis if yes i need the details there is no post written about praxis in either of the clubs social media page :soob

[planksconstant]

and do we need more pictures , yes there are lots of pics u guys hv sent but i felt 3 were sufficient if we need more lmk i can push them as well