First Configuration
Work through these files before replacing content at scale. Exact field names can vary by release, so check the source file before editing references in components or pages.
Configuration Checklist
Section titled “Configuration Checklist”- Change the firm name in
src/data/firm.ts. - Update phone, email, address, hours, and social links in
src/data/firm.ts. - Update navigation labels and URLs in
src/data/navigation.ts. - Replace the logo component or its text in
src/components/common/Logo.astro. - Replace
public/favicon.svgandpublic/favicon.ico. - Check
astro.config.mjsfor the productionsiteURL and update it before deployment. - Search the project for the demo domain and replace it with the final production domain.
- Run the site locally and test primary navigation, forms, attorney pages, practice-area pages, blog pages, RSS, and policy pages.
Firm Data
Section titled “Firm Data”Open src/data/firm.ts and inspect the exported object or constants. Update only fields that are clearly meant to be buyer-edited.
Example only:
export const firm = { name: 'Example Legal Group', phone: '+1 (555) 010-1000', email: 'hello@examplelegal.com', address: '100 Main Street, Chicago, IL',};Navigation
Section titled “Navigation”Open src/data/navigation.ts and update labels, route paths, and any CTA links. If a page is removed from navigation, confirm that no component still assumes it exists.
Logo and Favicons
Section titled “Logo and Favicons”Replace src/components/common/Logo.astro when the on-page logo changes. Replace public/favicon.svg and public/favicon.ico for browser icons.
Production URL
Section titled “Production URL”Check astro.config.mjs for the site option. Set it to the final production URL so canonical links, sitemap integrations, RSS, and absolute metadata use the correct domain where applicable.