fix user_template link

[web-elite]

Summary by CodeRabbit

• Bug Fixes
  • Fixed a broken link path in panel documentation that prevented proper navigation between related pages.

[coderabbitai]

Walkthrough

A single relative Markdown link path in content/docs/fa/panel/client_template.mdx is corrected from ./user_template to ../user_template. No other content is changed.

Changes

Documentation Link Fix

Layer / File(s)	Summary
Fix relative link path content/docs/fa/panel/client_template.mdx	Relative link target for "قالب‌های کاربر" updated from ./user_template to ../user_template in the opening paragraph.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Poem

A tiny dot was lost one day,
The link went nowhere, gone astray.
Two dots now point the proper way,
../user_template — hooray!
🐇 The rabbit hops the right path today.

🚥 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 accurately describes the main change: fixing a relative link path for the user_template reference in the documentation file.
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 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.}

[coderabbitai]

Actionable comments posted: 1

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

Inline comments:
In `@content/docs/fa/panel/client_template.mdx`:
- Line 7: The link path in the markdown content has been incorrectly changed to
use the parent directory reference. Revert the link from `../user_template` back
to `./user_template` since both the client_template and user_template files are
in the same directory. This correction will ensure the link resolves correctly
and maintains consistency with the linking convention used in other related
documentation files like dashboard and users templates.

🪄 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: 8e0d2a09-67f1-40bc-be37-b7f3789ee2d5

📥 Commits

Reviewing files that changed from the base of the PR and between 7456bd0 and 15ade4d.

📒 Files selected for processing (1)

• content/docs/fa/panel/client_template.mdx

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the directory structure and link target validity.

# Check if user_template.mdx exists at the expected location
echo "=== Checking for user_template.mdx ==="
find . -name "user_template.mdx" -type f

# Check the directory structure of the panel docs
echo ""
echo "=== Panel docs directory structure ==="
find ./content/docs/fa/panel -type f -name "*.mdx" | head -20

# Show the full path of client_template.mdx
echo ""
echo "=== Full path of client_template.mdx ==="
find . -name "client_template.mdx" -type f

Repository: PasarGuard/PasarGuard.github.io

Length of output: 1175

---

Revert the link path back to ./user_template.

Both client_template.mdx and user_template.mdx reside in ./content/docs/fa/panel/, making ./user_template the correct relative path. The change to ../user_template would resolve to the parent directory ./content/docs/fa/user_template.mdx, which does not exist, creating a broken link. This contradicts the working convention in dashboard.mdx and users.mdx, which correctly use ./user_template from the same directory.

🤖 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 `@content/docs/fa/panel/client_template.mdx` at line 7, The link path in the
markdown content has been incorrectly changed to use the parent directory
reference. Revert the link from `../user_template` back to `./user_template`
since both the client_template and user_template files are in the same
directory. This correction will ensure the link resolves correctly and maintains
consistency with the linking convention used in other related documentation
files like dashboard and users templates.