doc(SvgEditor): add reference documentation

[ArgoZhang]

Link issues

fixes #6635

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Documentation:

• Add PackageTips component to the SvgEditor sample page to provide reference documentation

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds reference documentation for the SvgEditor component by introducing a PackageTips element in the sample page to guide users on installation and usage.

File-Level Changes

Change	Details	Files
Add package reference documentation for SvgEditor	Inserted a PackageTips component above the Basic demo block to display installation instructions for BootstrapBlazor.SvgEditor.	src/BootstrapBlazor.Server/Components/Samples/SvgEditors.razor

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6635	Add reference documentation for the SvgEditor component.	✅

Possibly linked issues

• doc(SvgEditor): add reference documentation #6635: The PR adds SvgEditor reference documentation, directly addressing the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• The PR description still contains placeholder sections and checkboxes—please remove or update them to reflect the actual changes.
• Besides adding the PackageTips component, consider including more detailed API usage examples or parameter explanations for the SvgEditor.
• Ensure the new SvgEditor reference documentation is registered in your docs navigation (e.g., sidebar or index) so it’s discoverable.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- The PR description still contains placeholder sections and checkboxes—please remove or update them to reflect the actual changes.
- Besides adding the PackageTips component, consider including more detailed API usage examples or parameter explanations for the SvgEditor.
- Ensure the new SvgEditor reference documentation is registered in your docs navigation (e.g., sidebar or index) so it’s discoverable.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f394087) to head (0b10c25).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6636   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          739       739           
  Lines        31676     31676           
  Branches      4459      4459           
=========================================
  Hits         31676     31676           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.