fix: change github repo link for admin dashboard in extend section

[tony-stark-eth]

📑 Description

Link in extend section for admin dashboard pointed to flowbite-svelte repository.

Status

• Not Completed
• Completed

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• I have checked the page with https://validator.unl.edu/
• All the tests have passed
• My pull request is based on the latest commit (not the npm version).

Summary by CodeRabbit

• Documentation
  • Updated hyperlink in the Flowbite Svelte Admin Dashboard section to direct users to the correct GitHub repository.

[vercel]

@Bavragor is attempting to deploy a commit to the Themesberg Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request involves an update to a hyperlink in the documentation for the Flowbite Svelte Admin Dashboard. The link previously directed users to the general Flowbite Svelte GitHub repository and has now been changed to point specifically to the Flowbite Svelte Admin Dashboard repository. The demo link in the document remains unchanged.

Changes

File Path	Change Summary
src/routes/docs/extend/flowbite-svelte-starter.md	Updated the GitHub Repo link from https://github.com/themesberg/flowbite-svelte to https://github.com/themesberg/flowbite-svelte-admin-dashboard.

Possibly related PRs

• fix: typo in demo url #1393: This PR involves a minor modification in the same markdown file (src/routes/docs/extend/flowbite-svelte-starter.md), specifically correcting a URL, indicating a direct connection in terms of documentation updates.

🐇 In the meadow, a link did change,
To guide the users, it’s now more strange.
From Svelte's home to Admin's domain,
Hopping along, we’ll never complain!
With every click, a new path to explore,
The rabbit's joy grows evermore! 🌼

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 099cfa6 and 42b2d3b.

Files selected for processing (1)

• src/routes/docs/extend/flowbite-svelte-starter.md (1 hunks)

Additional comments not posted (2)

src/routes/docs/extend/flowbite-svelte-starter.md (2)

Line range hint 1-41: Overall change looks good.

The update to the Flowbite Svelte Admin Dashboard GitHub repository link is the only change in this file, and it has been implemented correctly. The rest of the file, including other starter kit information and overall structure, remains unchanged and consistent.

---

18-18: Link updated correctly.

The GitHub repository link for the Flowbite Svelte Admin Dashboard has been updated as per the PR objectives. This change correctly points to the specific admin dashboard repository instead of the general Flowbite Svelte repository.

To ensure the link is functional and points to the correct repository, please run the following script:

Verification successful

---

Link Functionality Verified

The updated GitHub repository link for the Flowbite Svelte Admin Dashboard is accessible and contains the expected content.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the updated GitHub repository link

# Test: Check if the link is accessible and contains expected content
curl -s -o /dev/null -w "%{http_code}" https://github.com/themesberg/flowbite-svelte-admin-dashboard | grep 200 && echo "Link is accessible" || echo "Link is not accessible"
curl -s https://github.com/themesberg/flowbite-svelte-admin-dashboard | grep -q "Flowbite Svelte Admin Dashboard" && echo "Repository content verified" || echo "Repository content not verified"

Length of output: 345

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.