In the Astro edition, everything lives in the repo: projects and insights are Markdown files, page copy is TypeScript, and images sit beside them. There’s nothing to sign up for. For the pages, settings, and components both editions share, see the Davis overview.
Writing a project
Projects go in src/content/projects/, one file each. The file name is the URL: northstar-residences.md becomes /work/northstar-residences/.
---
title: Northstar Residences
description: Brand identity and launch site for a brutalist residential studio.
date: 2026-03-12
category: Brand Identity
client: Northstar
cover: northstar
coverAlt: Concrete residence set alone in an open field under overcast sky
impact:
- value: "7×"
label: Faster phase-one close
note: vs. prior rebrand cycle
quote: Davis felt less like an external agency and more like our own team.
quoteBy: Founder, Northstar
result: 7× faster close
services: ["Brand strategy", "Visual identity", "Guidelines", "Marketing site"]
tags: ["Identity", "Guidelines", "Web"]
featured: true
draft: false
story:
- type: copy
heading: The brief
paragraphs:
- Northstar builds residences that sit quietly in the landscape.
- type: figure
image: interior
alt: Minimal concrete interior with soft daylight
caption: Fig. 02 — Material language
- type: strip
items:
- image: alexander
alt: Architectural detail
caption: Fig. 03 — Detail study
---
| Field | Required | Notes |
|---|---|---|
cover |
Yes | Key into src/assets/images (see photos in src/assets/images/index.ts) |
coverAlt |
Yes | Describes the cover |
category |
No | Shown on cards and case headers |
client |
No | Shown beside the category on the case |
impact |
No | Metric tiles: value, label, optional note |
story |
No | Ordered blocks: copy, figure, or strip |
quote, quoteBy, result |
No | Pull-quote panel on /work/ and case pages |
services, tags |
No | Service chips and free tags |
featured |
No | Featured projects sort first on /work/ and feed the home featured case |
draft |
No | true hides the project from listings and routes |
title, description, date, and seo work as described in Content & blog. Images referenced in cover and story are keys, not file paths — add the asset under src/assets/images/ (or generated/) and register it in the photos map.
Writing an insight
Insights are the shared blog collection in src/content/blog/. Davis uses the standard fields plus an optional category string for the desk meta:
---
title: The brief is the product
description: Most launches fail upstream. Treat the brief like a shipped artifact.
date: 2026-10-14
category: Strategy
tags: [briefs, process]
draft: false
---
| Field | Required | Notes |
|---|---|---|
category |
No | Shown on the Insights index and post header |
draft |
No | true hides the post |
Cover images are optional; Davis’s Insights landing leads with typography and a featured card rather than a photo grid. See Content & blog for seo, tags, and Markdown body rules.
Images and chrome
- Page and project photos:
src/assets/images/via thephotosmap - Nav, footer, fonts, and publisher details:
src/config/identity.ts - Page and band copy:
src/config/pages.ts - SEO, AEO, analytics, contact form:
src/config/integrations.ts
The sticky nav overlays the home hero (pageType="home"). Other pages use the solid bar. Don’t put hex colors in .astro files — use tokens from theme.css.
SEO and AI
| Setting | Edit in |
|---|---|
| Default title, description, social image and alt, X handle, profile links, keywords | seo in src/config/integrations.ts |
| Page titles and descriptions | title and description under each page in src/config/pages.ts |
| Summary, topics, questions and answers, notes for AI assistants, AI crawlers | aeo in integrations.ts |
| Google tag or Plausible, Google and Bing verification | analytics and seo.verification in integrations.ts |
| A post or project’s search title, description, social image, hiding it | That entry’s seo frontmatter |
How these work in Davis (see SEO & AEO for the basics every theme shares):
- Questions and answers in
aeo.faqappear on the contact page, with FAQ structured data on that page only. /llms.txtand/llms-full.txtlist pages, insights, and projects.- Case studies emit project structured data; insights emit
BlogPosting.
Before launch
- Follow the shared launch steps.
- Replace demo projects under
src/content/projects/and insights undersrc/content/blog/. - Swap hero, about, leadership, and city images in
src/assets/images/(and thephotosmap). - Rewrite
src/config/pages.ts,identity.ts, andintegrations.tsfor your studio. - Confirm
public/_headersstill allows framing from baselayerthemes.com if you keep a public demo; remove that line for a client site that should not be embedded. - Run
npm run typecheckandnpm run build.
Want to move to Sanity later? The Astro + Sanity edition can import your projects and insights.