Skip to content
NaturaLife Astro Theme

Global Settings

Find the shared settings for your logo, navigation and content layouts, and learn where to update your brand details and public site identity.

FileControls
site.jsonLogos, navigation, contact/social content, interface labels, shared SEO, blog defaults and demo store settings
blog.jsonShared blog-detail header/footer, sidebar, sharing and comment presentation
products.jsonShared product-detail header/footer and product interface text
portfolio.jsonShared project-detail header/footer and project interface text

These files are the entry point for shared settings. There are no duplicate settings to maintain under src/content/site/ or src/data/.

Edit the existing logo and lightLogo objects in site.json, preserving dimensions and responsive choices appropriate for the chosen design. Replace their registered image sources as described in Images and Fonts.

Update the existing navigation links, footer contact content, social links and interface labels. Test menus, footer destinations and readable logo contrast at mobile and desktop widths. A navigation link does not create its destination: add the route or content record separately.

Designed-page header/footer choices remain in src/content/pages/. Blog, product and portfolio detail defaults live in the corresponding settings file. Individual page or record overrides still apply where the public schema supports them.

Repeated layout values are not a new inheritance or deep-merge system. Edit the file used by your page type, and inspect its supported fields before adding an override. Individual article, product, project and taxonomy data stays in the content collections.

The starter uses preview/noindex SEO. Set genuine site identity, language and production settings in site.json before launch; follow Deployment and SEO for the exact production switch.

Comments, store controls and language selectors include presentation settings. Enabling their appearance does not install comment hosting, payment processing or translated content. Connect those services and routes separately when your project needs them.