docs: Add cross-references to new Submit a Ticket and Client Portal Login pages#1
docs: Add cross-references to new Submit a Ticket and Client Portal Login pages#1ridgelawrence wants to merge 1 commit intomainfrom
Conversation
…ages - Update support/overview.mdx with Quick Actions section linking to submit-ticket and client-login pages - Update support/contact.mdx to reference the embedded ticket form and client portal login Triggered by commit 12f9d1c which added these pages. Co-Authored-By: Warp <agent@warp.dev>
📝 WalkthroughWalkthroughDocumentation pages updated to enhance user support visibility. The contact page now references an embedded ticket form and introduces a Client Portal section. The overview page adds a new Quick Actions section with interactive cards for ticket submission and portal login access. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@support/contact.mdx`:
- Around line 14-15: The Client Portal blurb under the "### Client Portal"
heading is missing the phrase "and access co-managed IT resources" that appears
in overview.mdx; update the sentence "Already have a ticket? [Sign in to the
client portal](/support/client-login) to manage tickets and view SLA
dashboards." to match the overview copy by appending "and access co-managed IT
resources" so both pages use the same description.
- Line 15: Update the Client Portal description in support/contact.mdx so it
matches the overview page: modify the sentence "Already have a ticket? [Sign in
to the client portal](/support/client-login) to manage tickets and view SLA
dashboards." by appending "and access co-managed IT resources" so the Client
Portal card description is identical to the overview copy for consistency.
In `@support/overview.mdx`:
- Around line 27-34: The Card icon names are Font Awesome but the docs use
Lucide; update the icon props in the Columns block so Cards use Lucide names:
change the first Card's icon value from "pen-to-square" to "square-pen" and
change the second Card's icon value from "right-to-bracket" to "log-in" (leave
the Columns and Card components and their hrefs/content unchanged).
ℹ️ Review info
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (2)
support/contact.mdxsupport/overview.mdx
| ### Client Portal | ||
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards. |
There was a problem hiding this comment.
bro the client portal description is diff in overview.mdx and it's gonna confuse ppl lmao
ok so like, in overview.mdx line 32 the Client Portal card says "manage tickets, view SLA dashboards, and access co-managed IT resources" but over here on line 15 u only got "manage tickets and view SLA dashboards" — no mention of the co-managed IT thing. idk if that's on purpose or u just forgot to copy paste it but like... users are gonna read both pages and be like "wait where did the co-managed IT thing go"
✏️ Suggested fix to align descriptions
-Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards.
+Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets, view SLA dashboards, and access co-managed IT resources.📝 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.
| ### Client Portal | |
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards. | |
| ### Client Portal | |
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets, view SLA dashboards, and access co-managed IT resources. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@support/contact.mdx` around lines 14 - 15, The Client Portal blurb under the
"### Client Portal" heading is missing the phrase "and access co-managed IT
resources" that appears in overview.mdx; update the sentence "Already have a
ticket? [Sign in to the client portal](/support/client-login) to manage tickets
and view SLA dashboards." to match the overview copy by appending "and access
co-managed IT resources" so both pages use the same description.
| Submit a ticket at [wrld.support](https://wrld.support) or use our [embedded ticket form](/support/submit-ticket). | ||
|
|
||
| ### Client Portal | ||
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards. |
There was a problem hiding this comment.
yo the client portal description here is missing stuff compared to overview.mdx
ok so like... over in overview.mdx line 32, the Client Portal card says "manage tickets, view SLA dashboards, and access co-managed IT resources" but right here on line 15 u only got "manage tickets and view SLA dashboards" — the co-managed IT resources part just vanished bro. users are gonna read both pages and get confused why one page knows about the co-managed IT thing and the other one doesn't even mention it 😵
✏️ Proposed fix to keep descriptions in sync
-Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards.
+Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets, view SLA dashboards, and access co-managed IT resources.📝 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.
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets and view SLA dashboards. | |
| Already have a ticket? [Sign in to the client portal](/support/client-login) to manage tickets, view SLA dashboards, and access co-managed IT resources. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@support/contact.mdx` at line 15, Update the Client Portal description in
support/contact.mdx so it matches the overview page: modify the sentence
"Already have a ticket? [Sign in to the client portal](/support/client-login) to
manage tickets and view SLA dashboards." by appending "and access co-managed IT
resources" so the Client Portal card description is identical to the overview
copy for consistency.
| <Columns cols={2}> | ||
| <Card title="Submit a Ticket" icon="pen-to-square" href="/support/submit-ticket"> | ||
| Start a new support request or look up an existing ticket | ||
| </Card> | ||
| <Card title="Client Portal Login" icon="right-to-bracket" href="/support/client-login"> | ||
| Sign in to manage tickets, view SLA dashboards, and access co-managed IT resources | ||
| </Card> | ||
| </Columns> |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Font Awesome 6 icon "pen-to-square" "right-to-bracket" official names
💡 Result:
- Pen to Square — official icon name:
pen-to-square(shown in the v4→v6 rename table aspencil-square-o→pen-to-square). [1] - Right to Bracket — official icon name:
right-to-bracket(shown in the v4→v6 rename table assign-in→right-to-bracket). [1]
Source(s): [1] Font Awesome v6 docs “Upgrade from Version 4” rename table.
🌐 Web query:
Mintlify Card component icon support Font Awesome
💡 Result:
Mintlify’s <Card> supports icons from Font Awesome (and other sources). To use Font Awesome icons:
- Ensure your
docs.jsonhasicons.library: "fontawesome"(this is the default). [3] - Set the card’s
iconprop to the Font Awesome icon name (string), and optionally seticonTypeto pick the style (solid,regular,brands, etc.). [1]
Example:
<Card title="Security" icon="shield-halved" iconType="solid" href="/security">
Learn about our security model.
</Card>Notes:
iconcan also be a Lucide/Tabler name (depending onicons.library), a URL, a local file path, or an inline JSX SVG. [1][2]
🏁 Script executed:
# Search for Mintlify config files in the repo
fd -t f -e json -e yaml -e yml | grep -E "(mintlify|config)" | head -20Repository: WRLDInc/docs
Length of output: 38
🏁 Script executed:
# Look for any documentation about icon setup or theming
find . -type f \( -name "*.json" -o -name "*.mdx" -o -name "*.md" \) -path "*config*" -o -path "*setup*" | head -20Repository: WRLDInc/docs
Length of output: 100
🏁 Script executed:
# Look for Mintlify config files at root level
ls -la | grep -E "mint|docs|config"Repository: WRLDInc/docs
Length of output: 115
🏁 Script executed:
# Check for mintlify.json or similar config
fd -t f "mintlify\\.json|docs\\.json|mint.*\\.json" . --max-depth 2Repository: WRLDInc/docs
Length of output: 67
🏁 Script executed:
# Check package.json for Mintlify config or dependencies
cat package.json 2>/dev/null | head -50Repository: WRLDInc/docs
Length of output: 38
🏁 Script executed:
cat docs.jsonRepository: WRLDInc/docs
Length of output: 7012
🌐 Web query:
Lucide icon names for "pen" "edit" pencil square
💡 Result:
Common Lucide icon names (kebab-case) and their lucide-react component exports (PascalCase):
- pen →
pen/Pen(app.unpkg.com) - pencil →
pencil/Pencil(app.unpkg.com) - edit / pencil-square (the “pen in a square” edit icon) →
square-pen/SquarePen(icon-sets.iconify.design) - older/alternate “pen-square” name (still present in some packages/versions) →
pen-square/PenSquare(app.unpkg.com)
Citations:
- 1: https://app.unpkg.com/lucide-react%400.522.0/files/dist/esm/icons?utm_source=openai
- 2: https://app.unpkg.com/lucide-react%400.522.0/files/dist/esm/icons?utm_source=openai
- 3: https://icon-sets.iconify.design/lucide/square-pen/?utm_source=openai
- 4: https://app.unpkg.com/lucide-react%400.522.0/files/dist/esm/icons?utm_source=openai
🌐 Web query:
Lucide icon names for "right to bracket" "sign in" login arrow
💡 Result:
In Lucide, the equivalent of Font Awesome’s right-to-bracket (sign-in / login arrow) is:
log-in(component name:LogIn) (shadcn.io)
Related (sign-out):
log-out(component name:LogOut) (docs.rs)
Citations:
- 1: https://www.shadcn.io/icon/lucide-log-in?utm_source=openai
- 2: https://docs.rs/lucide-icons/latest/lucide_icons/enum.Icon.html?utm_source=openai
Icons won't render—those are Font Awesome names but the docs are configured for Lucide
the pen-to-square and right-to-bracket icon names are legit Font Awesome 6 names but like... the repo's docs.json is set to "library": "lucide" so they're just gonna be broken. need to swap em:
pen-to-square→square-pen(Lucide)right-to-bracket→log-in(Lucide)
rest of the Card structure is clean and consistent with the Support Channels section above, so once the icon names are fixed this slaps
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@support/overview.mdx` around lines 27 - 34, The Card icon names are Font
Awesome but the docs use Lucide; update the icon props in the Columns block so
Cards use Lucide names: change the first Card's icon value from "pen-to-square"
to "square-pen" and change the second Card's icon value from "right-to-bracket"
to "log-in" (leave the Columns and Card components and their hrefs/content
unchanged).
Documentation sync: Reference new Support pages
What changed
The recent commit
12f9d1cadded two new user-facing pages:support/submit-ticket.mdx— embedded ticket submission and lookup formsupport/client-login.mdx— client portal login with magic linkHowever, the existing support pages did not reference these new pages, making them harder to discover.
Changes in this PR
support/overview.mdx: Added a "Quick Actions" section with cards linking to the Submit a Ticket and Client Portal Login pagessupport/contact.mdx: Added a reference to the embedded ticket form and a new "Client Portal" section linking to the login pageWhy
Users landing on the Support Overview or Contact page should be able to easily find the new ticket submission and portal login capabilities.
This PR was generated with Warp.
Summary by CodeRabbit