Skip to content

Marketing Site Template — organizational overview

ConnectSoft.MarketingSiteTemplate is the Factory starter for public marketing websites: a Blazor Server solution with ConnectSoft UIKit, page packs, SEO, lead capture, analytics, and compliance-oriented defaults. It aligns with the live ConnectSoft.MarketingSite baseline and the UIKit + Flowbite alignment plan.

Why use this template

  • Faster time-to-launch for product marketing, landing campaigns, and corporate sites without rebuilding shell, SEO, or observability from scratch.
  • Consistent brand experience via ConnectSoft UIKit and Flowbite — same design language as other ConnectSoft front-end products.
  • Governed defaults for logging, telemetry, security headers, health checks, and testing — suitable for regulated and multi-team environments.
  • Flexible scope through page packs: generate a minimal brochure site or a full B2B SaaS marketing footprint in one dotnet new command.

Typical use cases

  • B2B SaaS product marketing — pricing, platform/solutions pages, case studies, blog, trust center.
  • Corporate or program landing sites — hero, services, FAQ, contact, newsletter signup.
  • Growth and campaign sites — landing variants, A/B experiments, GA4 with cookie consent.
  • Bilingual markets — English and Hebrew with RTL support out of the box.
  • Agency or vertical packs — start from minimal or growth packs and extend JSON content without Razor edits.

Capabilities (what the kernel brings)

  • 50+ ready routes across Core, Product, Content, Trust, and Auth page packs.
  • JSON-driven content — edit copy in wwwroot/data/pages/ without redeploying page structure.
  • SEO and discoverability — meta tags, JSON-LD, sitemap.xml, robots.txt, optional blog RSS.
  • Lead capture — contact and newsletter APIs with stub services ready for CRM integration.
  • Analytics and compliance — GA4 (consent-gated), cookie consent banner, GDPR-oriented legal pages.
  • Observability and security — Serilog, OpenTelemetry, Application Insights, rate limiting, security headers.
  • Three-tier testing — unit (bUnit), integration (WebApplicationFactory), E2E (Playwright).

Page packs at a glance

Pack CLI --PagePack What you get
Minimal minimal Core conversion pages (home, services, pricing, FAQ, contact, legal)
Standard standard Core + trust pages (testimonials, why-us, partners, etc.)
Growth growth Core + product + trust (platform, solutions, integrations, security)
Full full (default) All packs including blog, case studies, careers, and auth UI scaffolds

What leaders should expect

  • Marketing vs portal: This template is for public marketing sites. Authenticated SaaS portals should use Blazor Shell or MFE templates.
  • Content ownership: Default placeholder brand is "Acme SaaS" in JSON and resources — teams replace with their product branding before launch.
  • Identity: Auth pages are UI scaffolds, not an identity provider. Production sign-in flows integrate with Identity / Authorization Server templates or external IdPs.
  • Lifecycle: Template is in Beta — suitable for pilot and early production with engineering support (see Templates lifecycle).

Technical documentation (single hub)

Scaffolding, parameters, architecture, configuration, authentication scaffolds, resilience, testing, development guidance, use cases, and runbooks are maintained only in ConnectSoft.Documentation under this template.

→ Marketing Site Template — technical hub (ConnectSoft.Documentation)