ASTRO HOSTING

No. Static.app hosts pre-built files without a server runtime. Use Astro's default static mode (output: 'static') which pre-renders all pages during the build step. If you've switched to SSR or hybrid mode in your config, change it back to static before building. The static output includes all your pages as plain HTML files that Static.app serves directly.

Yes, fully. Astro's island architecture compiles interactive components (React, Vue, Svelte, Solid) into JavaScript files during the build. The HTML page loads first, then the interactive islands hydrate independently in the browser. Client directives like client:load, client:visible, and client:idle all work because they're browser-side features built into the compiled output.

Yes. Astro supports components from React, Vue, Svelte, Solid, Preact, Lit, and Alpine. These components compile during the build step into JavaScript that the browser runs. Use client directives (client:load, client:visible) to control when they hydrate. The compiled output is standard HTML and JavaScript that Static.app serves like any other static file.

Yes. Astro's content collections process Markdown and MDX files at build time, generating static HTML pages for each piece of content. Blog posts, documentation pages, product listings, anything in your content collections compiles to HTML during npm run build. Upload the output and every page works. To update content, edit your Markdown files, rebuild, and re-upload.

Astro DB requires a server runtime to handle database queries, so it doesn't work on static hosting. For static websites, use content collections (Markdown/MDX files processed at build time) or fetch data from an external source (headless CMS, API) during the build step. The fetched data gets baked into static HTML pages. You can also use client-side databases like Supabase or Firebase for dynamic data in the browser.

Yes. View Transitions are a browser API that Astro wraps for smooth page transitions. The feature works by including a small JavaScript file in the build output that manages the transition animations between pages. Since it's all client-side browser functionality, it works on any static host including Static.app. Pages still load as ordinary static files, the transitions just make navigation feel smoother.

Build-time integrations (image optimization, sitemap generation, RSS feeds) all work because they run during npm run build. Runtime integrations that need a server won't work.

Hybrid mode lets you mix static and server-rendered pages in one project. The server-rendered pages require a Node.js runtime that Static.app doesn't provide. To host on Static.app, use output: 'static' (the default) which pre-renders every page at build time. If you have specific pages that need server rendering, consider hosting those on a separate Node.js platform and keeping the static pages on Static.app.

Yes. Connect any headless CMS (Contentful, Sanity, Strapi, Decap CMS, Keystatic) to your Astro project. Astro fetches content from the CMS API at build time and generates static HTML pages. Upload the build output to Static.app. When content changes in the CMS, rebuild your Astro project and re-upload. For automated workflows, use GitHub Actions to trigger a build and deploy whenever CMS content updates.

Very fast. Astro ships zero JavaScript by default, so pages are pure HTML and CSS. There is very little for the browser to download, so the page renders as soon as the HTML arrives. Astro websites commonly score well on Lighthouse performance. Even pages with interactive islands load fast because the HTML renders immediately while JavaScript hydrates components in the background.

Extremely fast. Astro's zero-JavaScript-by-default approach means most pages are pure HTML and CSS, typically 10-50KB total. Static.app serves these files directly over HTTPS, and with so little to download most pages appear almost immediately. Lighthouse performance scores are typically high. Adding interactive islands increases the JavaScript payload, but Astro's partial hydration keeps it minimal compared to full-framework approaches.