docs: Revise FAQ content for clarity and updates

[sasakrsmanovic]

Updated FAQ to clarify the differences between Uno Platform and .NET MAUI, as well as added information on AI integration and design tools.

GitHub Issue: closes #

• 📚 Documentation content changes

PR Type:

What is the current behavior? 🤔

What is the new behavior? 🚀

PR Checklist ✅

Please check if your PR fulfills the following requirements:

• 📝 Commits must be following the Conventional Commits specification.
• 🧪 Added Runtime tests, UI tests, or a manual test sample for the changes have been added (for bug fixes / features) (if applicable)
• 📚 Docs have been added/updated which fit documentation template (for bug fixes / features)
• 🖼️ Validated PR Screenshots Compare Test Run results.
• ❗ Contains NO breaking changes

Other information ℹ️

[Copilot]

Pull request overview

This documentation PR updates the FAQ to clarify differences between Uno Platform and other frameworks (.NET MAUI and Blazor), highlighting new features like AI integration through MCPs and design tools. The changes also streamline the history description of Uno Platform and emphasize rendering flexibility.

Changes:

• Removed historical details about nventive's internal development period
• Added emphasis on rendering choice flexibility
• Reorganized and expanded differentiators from .NET MAUI, focusing on AI integration (MCPs), Hot Design Agent, and Figma integration
• Added similar AI and design tool information to the Blazor comparison section

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@sasakrsmanovic I've opened a new pull request, #22654, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[unodevops]

⚠️⚠️ The build 196308 has failed on Uno.UI - docs.

[unodevops]

⚠️⚠️ The build 196389 has failed on Uno.UI - docs.

[sasakrsmanovic]

@ajpinedam @Jen-Uno Hey guys - could you please see what's up with this one; it is important to me to have this one reviewed and pushed. Thx!!

[Copilot]

@sasakrsmanovic I've opened a new pull request, #22670, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

@sasakrsmanovic I've opened a new pull request, #22671, to work on those changes. Once the pull request is ready, I'll request review from you.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ sasakrsmanovic
✅ ajpinedam
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-22653/docs/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-22653/docs/index.html

[kazo0]

@Mergifyio backport release/stable/6.5

[mergify]

backport release/stable/6.5

❌ No backport have been created

Details

• Backport to branch release/stable/6.5 failed

Git reported the following error:

error: commit 3f27d576040d7e757ecf59edf20b0ed4b8e2cb0a is a merge but no -m option was given.
fatal: cherry-pick failed