Add splash screen overview documentation page

[Copilot]

GitHub Issue: closes #18194

PR Type:

📚 Documentation content changes

What is the current behavior? 🤔

The documentation lacks a centralized overview page for splash screen functionality. Developers must navigate multiple disparate documents (manual setup tutorial, Resizetizer docs, WebAssembly AppManifest) without understanding how they relate or which approach applies to their project.

What is the new behavior? 🚀

Added a comprehensive splash screen overview page (doc/articles/features/splash-screen-overview.md) that serves as the entry point for splash screen documentation. The page includes:

• Introduction: Brief explanation of splash screens with links to platform-specific design guidelines (Windows, Apple, Android)
• Uno Platform feature section:
  • Default cross-platform support statement
  • Uno.Resizetizer automatic configuration for templates 4.8+
  • Setup paths for modern vs. legacy templates
• Customization options:
  • Color customization (background, accent)
  • WebAssembly-specific options via AppManifest.js
  • Platform-specific configuration (Windows, Android, iOS/macOS, GTK/Linux)
• Cross-references: Properly links manual tutorial, Resizetizer docs, AppManifest reference, and sample project

Updated doc/articles/toc.yml to include the page in UI > Features section.

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 ℹ️

Documentation builds successfully with all xref links validated. The page follows existing documentation structure and style conventions.

Auto-generated CSS build artifacts (main.css and main.css.map) have been reverted to avoid including unintended build outputs in the PR.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Overview page for splash screen feature</issue_title>
<issue_description>While a tutorial document for manual setup was recently updated to reflect new possibilities with Resizetizer, we currently lack a higher-level overview page for the splash screen feature in Uno apps. This would serve as a centralized starting point for devs to understand the feature, yet emphasize the consistency that’s possible across Uno targets.

We need to present the existing tutorials and/or reference pages alongside the context needed to save developers time. Such overview-style page may include:

intro: splash screens

• A very brief introduction to splash screens (hereafter “the feature”) as an aspect of the UX which links to external content ie Windows app or other platform guidance where needed - for supporting perspectives

section: splash screens as an Uno feature

• Statement that Uno apps default to leveraging this feature where supported, across platforms.
• Reference our tutorial(s) which address remaining platform-specific gaps (cough cough GTK) in setting up the feature itself
• Splash screens display an image asset
• Uno projects created with newer templates handle scaling the provided assets (reference resizetizer config docs)
• Uno projects created with prior template versions can use resizetizer or opt to set up their splash screen manually (reference to both tutorials)
• Uno enables you to customize aspects of the feature such as its background and accent color

section: options to customize the feature

• Reference WASM AppManifest properties
• Highlight any additional customization possibilities per-platform

Concern

Clarification of capabilities

Affected platforms

No response

Any feedback?

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Overview page for splash screen feature #15431

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[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.
1 out of 2 committers have signed the CLA.

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

[Copilot]

Pull request overview

This pull request adds a comprehensive splash screen overview page to the Uno Platform documentation, addressing issue #15431. The new documentation provides a centralized starting point for developers to understand splash screen capabilities across all Uno Platform targets, with clear guidance on setup approaches and customization options.

Key Changes

• Added new splash screen overview documentation at doc/articles/features/splash-screen-overview.md
• Updated table of contents in doc/articles/toc.yml to include the new page under Features
• Updated minified CSS build artifacts (auto-generated files)

Reviewed changes

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

File	Description
doc/articles/features/splash-screen-overview.md	New comprehensive overview covering splash screen concepts, default behavior, setup approaches for modern and legacy templates, and platform-specific customization options
doc/articles/toc.yml	Added "Splash screen" entry in Features section with proper alphabetical ordering
doc/templates/uno/styles/main.css	Auto-generated minified CSS with webkit-backdrop-filter prefix addition
doc/templates/uno/styles/main.css.map	Auto-generated source map for CSS debugging

[Jen-Uno]

@copilot undo the changes to main.css and main.css.map

[Copilot]

@copilot undo the changes to main.css and main.css.map

Reverted the auto-generated CSS build artifacts in commit 5b2aba5.

[unodevops]

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

[github-actions]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or it will be closed in 10 days.

[github-actions]

This PR was closed because it has been stalled for 10 days with no activity.