Static-first public website
Astro generates fast public pages with responsive media, structured metadata, and minimal client-side JavaScript.
Professional project
Monarch Media
A performance-focused Astro website supported by a custom .NET and PostgreSQL backend for managing projects, team members, images, and administrative users.
AstroTypeScriptTailwind CSSASP.NET CorePostgreSQLAzureNetlify
Project overview
The context behindthe final result.
A closer look at the goals, decisions, and technical thinking that shaped the project.
The public site presents web-development, care-plan, portfolio, and contact content through a fast static-first Astro frontend.
A separate authenticated backend supports ongoing content administration without exposing database access directly to the public frontend.
Key features
What the projectneeded to accomplish.
Core capabilities delivered for Monarch Media.
Custom administrative area
Protected tools support project, team-member, image, and administrator management.
API-driven content
ASP.NET Core endpoints provide controlled access to PostgreSQL-backed content.
Secure authentication
Administrative access uses hashed credentials, JWT-based login, and protected routes.
Cloud deployment
The frontend deploys through Netlify while the API runs through Azure App Service.
Search and social metadata
Canonical URLs, Open Graph data, structured data, sitemap support, and robots controls improve discoverability.
Publishing workflow
From administrative update to public website
Authorized users manage content through protected forms, the API validates and stores the update, and a deployment hook refreshes the public site.
- 0101
Authenticate
An administrator signs in through the protected area.
- 0202
Manage
Projects, people, and media are created or updated.
- 0303
Validate
The API validates authorization and submitted data.
- 0404
Persist
PostgreSQL stores the approved content.
- 0505
Publish
A Netlify build refreshes the public website.
Project gallery
A closer look atMonarch Media.
Selected screens and interfaces from the project.
Technical highlights
The systems behindthe interface.
Selected architectural and implementation decisions that shaped the project.
Astro frontend
The public experience favors pre-rendered pages, optimized assets, and high Lighthouse performance.
ASP.NET Core API
Custom controllers expose public content and protected administrative operations.
PostgreSQL and EF Core
Entity Framework Core manages projects, team members, media, and administrator records.
Authentication security
Argon2id password hashing and JWT authorization protect administrative access.
Storage integration
Media records connect to externally hosted project and team imagery.
Deployment integration
Azure-hosted backend services and Netlify build hooks support the split architecture.
Challenges
The difficult partsshaped the better decisions.
The constraints and implementation problems that required the most thought.
Keeping public pages static
Dynamic administrative requirements had to be isolated so public routes could remain fast and pre-rendered.
Securing administrative workflows
Authentication, cookies, API authorization, and route protection needed to work across the Astro and .NET boundary.
Coordinating two deployments
Frontend and backend services required separate configuration, CORS rules, secrets, and deployment verification.
Outcomes
What the projectmade possible.
The practical result of the work beyond the interface itself.
- 01
Created a maintainable public site with a custom content-management workflow.
- 02
Separated public presentation from protected administrative operations.
- 03
Achieved a fast, SEO-ready frontend while retaining database-backed content management.
Explore what comes next
Need something with similar depth?
Website packages provide a practical starting point, while custom scope is available when the project needs more.