uno-navigation-regions

Implement region-based navigation in Uno Platform apps using Region.Attached, Region.Name, and Region.Navigator.

9|1|Updated Dec 10, 2024
One-click install
npx skills add https://github.com/unoplatform/studio --skill uno-navigation-regions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uno-navigation-regions
Source: https://github.com/unoplatform/studio/tree/main/plugins/uno-platform-studio/skills/uno-navigation-regions
Command: npx skills add https://github.com/unoplatform/studio --skill uno-navigation-regions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement region-based navigation in Uno Platform applications by leveraging Region.Attached, Region.Name, and Region.Navigator to coordinate content regions with navigation controls.

Core Features & Use Cases

  • Define regions that map to content areas on a page, enabling consistent cross-platform navigation.
  • Link content regions to navigation controls such as TabBar and NavigationView, including visibility-driven region switching and nested regions.
  • Use as a reference workflow for building region-driven routing in Uno Platform apps.

Quick Start

Create a sample Uno Page that defines a region using Region.Attached, Region.Name, and Region.Navigator and binds it to switch content.

Frequently Asked Questions about uno-navigation-regions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement region-based navigation in Uno Platform?

Region-based navigation in Uno Platform is implemented using Region.Attached to host content regions, Region.Name for route identity, and Region.Navigator to switch content visibility. This approach coordinates navigation controls like TabBar and NavigationView with mapped content areas.

What is the difference between Region.Attached and Region.Navigator in Uno Platform?

Region.Attached is used to host content regions within a page, while Region.Navigator controls content switching visibility. Region.Name provides route identity for the region, enabling navigation controls like TabBar and NavigationView to target specific content areas.

Can I use region-based routing with TabBar and NavigationView in Uno Platform?

Yes, region-based routing supports linking content regions to TabBar and NavigationView controls. Region.Attached, Region.Name, and Region.Navigator coordinate these navigation controls with content areas, including visibility-driven region switching and nested regions.

Does Uno Platform region navigation support nested regions?

Uno Platform region navigation supports nested regions by applying Region.Attached and Region.Name within parent content areas. Region.Navigator manages visibility switching for both top-level and nested regions, enabling complex hierarchical navigation structures.

Why is my Uno Platform region navigation not switching content visibility?

Region navigation issues often stem from missing Region.Attached for hosting, incorrect Region.Name for route identity, or improper Region.Navigator configuration. The Skill warns about these pitfalls and specifies requirements for coordinating content regions with navigation controls.

When should I use region-based navigation instead of page-based navigation in Uno Platform?

Region-based navigation suits scenarios where content areas on a single page need coordinated switching via TabBar, NavigationView, or visibility-driven logic. It maps routes to in-page content regions using Region.Name, unlike page-based navigation that transitions between separate pages.