Content Foundry

The root directory for creating publishable documentation sites. Each site contains a content directory where you organise pages into subdirectories that become your site navigation.

January 24, 2026

The Content Foundry directory contains your publishable documentation sites. Unlike the other root directories which represent architecture domains, Content Foundry is where you build documentation websites that can be published for local viewing or hosted on a web server.

Site Structure

Each site inside Content Foundry has a fixed structure:

What Belongs Here

Content Foundry publications are suited for any documentation you want to publish as a website or PDF:

Example Content Directory

Organise your content directory to match how users will browse your site. The folder hierarchy becomes the site navigation.

content/
├── getting-started/
│   ├── sort-order.cf.json
│   ├── overview.cf.page.json
│   ├── installation.cf.page.json
│   └── first-steps.cf.page.json
├── guides/
│   ├── sort-order.cf.json
│   ├── creating-diagrams/
│   │   ├── basic-shapes.cf.page.json
│   │   └── connectors.cf.page.json
│   └── documenting-apis/
│       ├── rest-apis.cf.page.json
│       └── graphql-apis.cf.page.json
└── reference/
    ├── sort-order.cf.json
    ├── content-blocks.cf.page.json
    └── diagram-elements.cf.page.json

Publishing

Content Foundry supports two publishing targets:

Target	Output	Use Case
Local	.neoarc-local-site folder	Viewing with file:// URLs or the desktop app
Hosted	.neoarc-hostable-site folder	Deploying to Azure Static Web Apps or any web server

Learn more

Getting Started with Publishing

Publish your documentation to local folders, hostable static sites, Azure, or PDF. Use the publishing wizard to select content, configure targets, and deploy your publication.