Announcing the New Agility CMS .NET 10 Starters: Blazor SSR & MVC

TL:DR

We're excited to announce a major update to how you build websites with Agility CMS and .NET. Today, we're releasing two production-ready starters—a modern Blazor SSR starter and a refreshed MVC starter—along with completely rewritten documentation to help you get up and running faster than ever.

What's New?

One-Click Azure Deployment

Both starters include pre-configured ARM templates for deploying to Azure App Service with a single click. Just enter your Agility API credentials, and you'll have a production-ready site in minutes.

The deployment automatically configures:

• Linux App Service running .NET 10
• WebSockets for Blazor interactivity (when needed)
• AlwaysOn to eliminate cold starts
• HTTPS with TLS 1.2 minimum
• Optimized cache headers for CDN compatibility

GraphQL + REST: Query Content Your Way

Both starters support our Fetch API with full GraphQL capabilities. Query exactly the fields you need, reduce payload sizes, and build efficient data fetching strategies:

var posts = await FetchApi.GetContentByGraphQL<Post>(@"
    {
        posts(take: 10, sort: ""fields.date"", direction: ""desc"") {
            contentID
            fields {
                title
                slug
                excerpt
                image { url }
            }
        }
    }
", "posts", "en-us");

Or use our typed REST endpoints for simpler use cases:

var posts = await FetchApi.GetTypedContentList<Post>(
    referenceName: "posts",
    locale: "en-us",
    take: 10
);

Built for Content Editors

These starters aren't just developer-friendly—they're designed with content editors in mind:

• Editor-Driven Pages: Content editors control the sitemap and page structure directly in Agility CMS, without needing developer involvement for every change
• Drag-and-Drop Modules: Components map directly to Agility modules, so editors can build pages visually
• Instant Preview: Preview draft content before publishing, with secure preview URLs
• Webhook-Powered Updates: Content changes publish automatically through our cache invalidation system

Which Starter Should You Choose?

Both starters share the same content fetching, caching, and deployment patterns—so your choice comes down to component architecture preference.

Migrating from an Older .NET Implementation?

If you're running an older Agility .NET integration, we've got you covered. Our new Migration Guide walks you through updating from legacy .NET MVC 4/5 implementations to the modern starters, including:

• API method mapping from Content Repository to Fetch API
• Converting views to Blazor components or ViewComponents
• Updating configuration from Web.config to appsettings.json
• Step-by-step migration checklist

What's Next?

This release is just the beginning. We're continuing to invest in the .NET ecosystem with plans for:

• Additional component examples and patterns
• Performance optimization guides
• Advanced caching strategies
• More deployment options

We'd love to hear your feedback. Join the conversation in our Community or open an issue on GitHub.

Ready to see what you can build? Get started with Agility CMS and .NET today.