Services
Custom software developmentUmbraco developmentWeb developmentCRM developmentERP developmentAI & LLM integration.NET development & modernizationE-commerce developmentIntegrations & automationCloud & DevOpsMaintenance, support & project rescueDedicated teams & white-label
Our Work
Case studiesProducts
About Blog Contact
Umbraco package · Editing

NestedPagesView

Edit, publish and add child pages from the parent page in Umbraco

Free Umbraco property editor that shows a container's child pages inline on the parent, so editors can update, publish or unpublish many pages from one screen.

dotnet add package NestedPagesView
NestedPagesView
Downloads2,651
Latest versionv1.0.6
Works withUmbraco 10–13
LicenseFree · MIT
Why it exists

The problem it solves

Many Umbraco sites keep lists of small pages under one container: team members, FAQ entries, locations or product variants. Updating them means opening each child node, editing, saving and going back to the tree. On a multilingual site that work repeats for every language. NestedPagesView puts those child pages on the parent so editors can work through them in one place.

Typical uses

  • Update a team page where each person is a child node
  • Maintain FAQ or glossary entries stored as separate pages
  • Publish a batch of location or branch pages at once
  • Edit translated versions of many small pages on a multilingual site

At a glance

NuGet package
NestedPagesView
Latest version
v1.0.6 · 7 releases
Umbraco
Umbraco 10–13
.NET
net8.0
First released
Oct 2022
Last updated
Sep 2025
Downloads
2,651
License
MIT
Requirements
Umbraco 13.9.2 or later for the current version (Umbraco 10 versions are 1.0.0–1.0.2).NET 8
Features

What NestedPagesView does

Child pages on the parent

A property editor lists the child pages of a container and opens each one inline for editing, in a layout similar to Nested Content.

Publish and unpublish per page

Each child row has its own Publish or Unpublish button, so you can change status without leaving the parent.

Add, copy and delete

Create new child pages from a type picker, copy an existing one, or delete one from the same list.

Multilingual support

Works on sites with several languages, so editors can update each culture's version of the child pages.

Split view

Supports Umbraco's split-view editing for side-by-side work on two languages.

Container rules

The data type setting Allow container of type limits which document types act as containers.

How it works

From install to first use

dotnet add package NestedPagesView
  1. Install the package

    Add NestedPagesView from NuGet to your Umbraco 13 project and restart.

  2. Create a data type

    In Settings, create a data type with the Nested Pages View editor, choose the container document type and set the tree source.

  3. Add it to a document type

    Add a property that uses the new data type to the container's document type and save.

  4. Edit children from the parent

    Open a container page in Content. Its child pages appear in the property, ready to edit, publish or add to.

FAQ

NestedPagesView questions

Need a custom feature or help installing? OSKI built this package and can help.

Contact us
Which Umbraco versions are supported?+

Version 1.0.3 and later need Umbraco 13.9.2 or newer on .NET 8. Versions 1.0.0 to 1.0.2 target Umbraco 10 on .NET 6. The editor is built for the AngularJS back office, so Umbraco 14 and later are not supported.

Is it free?+

Yes. NestedPagesView is free and MIT licensed.

Does it work on multilingual sites?+

Yes. It supports sites with several cultures and Umbraco's split-view editing.

Does it change how pages are stored?+

No. The child pages stay normal Umbraco content nodes. The editor only gives you a way to work on them from the parent.

Where can I report a bug?+

Open an issue on GitHub at github.com/Kirill19837/NestedPagesView, or contact OSKI.

Start a project

Need NestedPagesView customized or a package built for your Umbraco site?

A spec, a Figma file or three paragraphs is enough to start.

  1. First reply · from an engineer, not a sales rep
  2. 30-min call · with Roman, our CTO, to clarify scope
  3. After the call · a written proposal with plan, team and price
Roman Oleksuk
Roman Oleksuk, CTOPrefer to talk? Pick a slot in Roman's calendar
We reply from a human mailbox. No newsletters. Your brief stays under NDA on request. We use your details only to reply; see our privacy policy.