aerialps.com
AstroJS (SSG x SSR) The main site. Pre-generated at build time. No traditional server (except for blogs and media page), blazingly fast for end users.
Architecture Overview
AerialPS is split into two distinct applications that work together:
cms.aerialps.com
WordPress Content management only. Never hit directly by end users browsing the main site.
Why two apps?
Section titled “Why two apps?”The main site stays static and blazingly fast because it is pre-generated at build time. WordPress handles content creation only, it is never hit directly by end users browsing aerialps.com, only when fetching blogs or specific media.
Main technologies
Section titled “Main technologies”You need familiarity with all of the following to work on this project:
React
react.dev — UI components.
Astro
astro.build — SSG framework.
Tailwind CSS
tailwindcss.com — utility-first styling.
shadcn/ui
ui.shadcn.com — used for 2–3 fixed components only.
Also required: Node.js, Git, and npm (or an alternative package manager).
Rendering approach
Section titled “Rendering approach”The main site uses Static Site Generation (SSG). At build time, Astro compiles all the static pages and bakes them into static HTML pages. No WordPress connection is needed at runtime except for when reaching for /blogs or /drone-photography pages.
Fast page loads
Pages are pre-built files, no server round-trip on each visit. Also means we can host it for free )
Minimal bandwidth
Static files are cached at Cloudflare’s edge globally. In other words, Cloudflare always picks the closest server to the user for the fastest loading time
Great SEO
Crawlers get complete HTML immediately, no JavaScript rendering required.
No runtime dependency
WordPress going down does not affect the live site.
See Blogs - How It Works for the full technical detail on the build pipeline.
Hosting
Section titled “Hosting”aerialps.com
Cloudflare Pages: Free
cms.aerialps.com
SG Cloudhosting: Paid
See Hosting for full configuration details.