Revise intro.md to emphasize user pain points

[shubhamyadav2809]

Issue Reference

Closes #75

What Was Changed

• Rewrote the "Problem We Solve" section in intro.md.
• Replaced the technical bullet points with more relatable and engaging questions/scenarios, as suggested in the issue.
• The goal was to make the problem statements resonate better with users experiencing those challenges.

Why Was It Changed

To improve the initial documentation experience by making the core problems OpsiMate addresses clearer and more engaging for potential users, aligning with the goal of issue #75.

Screenshots

N/A (Text changes only)

Additional Context

This PR directly addresses issue #75 for Hacktoberfest 2025.

Summary by CodeRabbit

Release Notes

• Documentation
  • Refreshed introductory documentation with conversational questions for improved engagement and clarity around featured topics.

[vercel]

@shubhamyadav2809 is attempting to deploy a commit to the idan lodzki's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The PR replaces declarative problem statement bullet points in the intro documentation with conversational questions to increase relatability and engagement with readers.

Changes

Cohort / File(s)	Summary
Documentation content update opsimate-docs/docs/intro.md	Replaced four problem statement bullet points under "The Problem We Solve" section with conversational questions to make the content more relatable and engaging

Assessment against linked issues

Objective	Addressed	Explanation
Make problem statements more relatable through creative writing and conversational framing [#75]	✅

---

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

[github-actions]

Thanks for your contribution! Join our Slack: https://join.slack.com/t/opsimate/shared_invite/zt-39bq3x6et-NrVCZzH7xuBGIXmOjJM7gA Please make sure to include an image with your PR — it really helps us review and understand the changes better. Only in rare cases will we accept a PR without one. Also, take a moment to review your code to ensure it’s clear, readable, and easy to follow. PRs from contributors who haven’t joined our Slack community or starred the repository won’t be reviewed — we’d love to see you join and be part of the project!

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

opsimate-docs/docs/intro.md (1)

31-31: Optional refinement: Clarify the tone on the manual tasks item.

Line 31 shifts abruptly from aspiration ("Do you wish you could automate...") to frustration ("only to find yourself bogged down by error-prone routines?"). Consider smoothing the flow to be either purely aspirational or purely frustrated, or make the contrast more intentional. For example:

-⏳ **Wasting precious hours on repetitive manual tasks?** Do you wish you could automate the tedious stuff and focus on what truly matters, only to find yourself bogged down by error-prone routines?
+⏳ **Wasting precious hours on repetitive manual tasks?** You want to automate the tedious stuff and focus on what truly matters—but manual processes keep pulling you back in.

This is a stylistic suggestion; the current phrasing is readable and still conveys the pain point.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d711ef7 and 8512f0a.

📒 Files selected for processing (1)

• opsimate-docs/docs/intro.md (1 hunks)

🔇 Additional comments (1)

opsimate-docs/docs/intro.md (1)

27-33: Excellent rewrite that successfully achieves the PR objective.

You've effectively transformed the technical problem statements into conversational, relatable scenarios that should resonate much better with readers. The consistent use of emojis, bold opening questions, and follow-up rhetorical questions creates an engaging pattern that draws users in—well aligned with the goal of making problem statements feel personally relevant.