Orchard Core Content Studio

Content Studio is a Paper-inspired Vue authoring application hosted by Orchard Core. This private repository contains the application, its permission-aware Orchard modules, reusable companion modules, a browser Adapter SDK, a distributable reference site, tests, and two executable hosts.

The active development package line targets .NET 10 and the Orchard Core build embedded in Pomi. Packages are prepared for NuGet distribution, but no workflow publishes them to an external feed yet. Cloud remains pinned to its separately captured Orchard Core 3.0.1-compatible package set.

Repository layout

• src/MarkBartha.OrchardCore.ContentStudio.Core: marker parts, settings, permissions, and extension contracts.
• src/MarkBartha.OrchardCore.ContentStudio.Api: API boundary and compiled SPA assets.
• src/MarkBartha.OrchardCore.ContentStudio.App: Vue/Vite application source.
• src/MarkBartha.OrchardCore.ContentStudio.AdapterSdk: framework-neutral browser adapter package.
• src/MarkBartha.OrchardCore.ContentStudio.AdapterSample: example custom Orchard field and browser adapter.
• src/MarkBartha.OrchardCore.ContentStudio.ReferenceSite.Theme: Lumen & Form model, recipes, assets, and public templates.
• src/MarkBartha.OrchardCore.EditorJs: separately packaged Editor.js field integration used by the reference fixture.
• src/MarkBartha.OrchardCore.EditorialToolkit: separately packaged generic editorial administration helpers.
• tests/MarkBartha.OrchardCore.ContentStudio.Api.Tests: focused backend policy tests.
• samples/MarkBartha.OrchardCore.ContentStudio.DevHost: source-referenced development application.
• samples/MarkBartha.OrchardCore.ContentStudio.PackageConsumer: package-only restore/build smoke test.
• Docs: product, architecture, SDK, performance, and decision records.

Local development

Build and validate every generated frontend artifact, backend test, NuGet package, and package-only consumer:

./Pack.ps1 -Version 0.2.0-pomi.1

The packages are written to artifacts/packages. Use a new prerelease version for every changed package to avoid stale NuGet cache entries.

Run the development host:

dotnet run --project samples/MarkBartha.OrchardCore.ContentStudio.DevHost

Fresh Development setup creates:

• Default at / with Orchard's built-in SaaS recipe.
• ReferenceSite at /reference with MarkBartha.OrchardCore.ContentStudio.ReferenceSite.Setup.

The development-only administrator is admin / Password1!. The HTTPS endpoint is https://localhost:5781; Content Studio is available below /reference/content-studio after setup.

Delete only samples/MarkBartha.OrchardCore.ContentStudio.DevHost/App_Data when a prototype definition or recipe change requires a fresh setup.

Packaging contract

Each Orchard module or theme is packed independently. Internal project references become exact-version NuGet dependencies. Orchard's module/theme targets embed recipes, Razor assets, and static web assets into the package assemblies.

CI rebuilds committed frontend outputs, runs the fast test suites, packs the projects, and restores the separate consumer host exclusively through PackageReference. The manual release workflow uploads private build artifacts only; it intentionally contains no nuget push step.

The browser Adapter SDK remains an npm package source with UNLICENSED metadata until a separate publication decision is made.

Content model boundary

Content Studio supports schema-driven recursive editing for named BagPart collections and dedicated menu/taxonomy trees. FlowPart remains opaque and round-trip safe. New composable sites should attach a named Sections BagPart to the page and constrain it to content types using Orchard's Block stereotype.

See the current implementation, the technical architecture, and the Adapter SDK guide for deeper details.