Skip to content
NaturaLife HTML Template

Editing Content and Styles

Find the files you need to edit page content, manage shared headers and footers, add pages, and customize styles and interactive components.

Open a page in dist/ in a code editor. Replace its sample text, contact details, links and image paths, then preview it through a local HTTP server. Keep assets/ beside the HTML files.

Headers and footers appear in each generated page. Direct changes affect only that file; repeat them in the other pages you use. For shared changes, use the source workflow below. Rebuilding from source replaces direct edits to the generated HTML and theme CSS, so choose one main workflow and keep backups.

All paths below are relative to Source/ in your download.

What you want to changeWhere to start
Page text and component settingssrc/data/pages/<page-name>.json
Page structure and sectionssrc/pages/<page-name>.njk
Header logos, including light and 2× versionssrc/data/site.json
Navigation linkssrc/data/menu-tree.json
Shared header structuresrc/pages/site-header.njk
Footer text, contact information and linkssrc/data/footer-content.json
Per-page header/footer options and copyrightThe page’s JSON file
Shared page grid and content gutterssrc/foundations/page-grid.mjs
Demo cart product cataloguesrc/data/store-cart.json (keep product IDs consistent with the product data)
Shared components and interactionssrc/components/
Brand colors, typography and breakpointssrc/styles/theme.css and src/styles/fonts.css
Your CSS overridessrc/styles/custom.css

For example, change story.title in src/data/pages/about-us.json to update the story heading on about-us.html. Keep JSON valid: double-quoted strings and no trailing commas. Run npm run dev while editing to rebuild and reload the browser automatically.

Duplicate a similar page’s JSON and matching .njk template. Give both files the same new basename, update the JSON id to match, and update its title and content. Give its reference a unique value if retained. Add the new ID to src/data/site-pages.json, then build. For example, my-page produces dist/my-page.html.

Add a menu link such as ./my-page.html in src/data/menu-tree.json if needed. Existing demo reference links are converted to local links during the build; new pages can use local HTML paths directly.

Sample team profile and portfolio category links point to the included team and portfolio collection pages. Update those links if you add individual profile or category pages.

To remove a page, remove its ID and incoming links. After building, remove its old generated HTML from dist/ before uploading: a build does not automatically delete previously generated pages. Keep home-1 if you want the default index.html entry page.

Tailwind runs during the source build and writes dist/assets/styles/theme.css; no CDN compiler is used. Brand colors, fonts and breakpoints are design tokens in src/styles/theme.css. The included breakpoints are:

TokenWidth
tablet768px
grid992px
frame1024px
desktop1025px
large1280px

Review the affected layouts before changing a breakpoint.

Use src/styles/custom.css for CSS overrides; it loads after the theme stylesheet. Ready HTML users can edit dist/assets/styles/custom.css instead; keep a backup before rebuilding. Fonts are hosted locally. Change font declarations in fonts.css and the matching font family in theme.css when replacing a font, then check headings, buttons and navigation at mobile widths.

New Tailwind utility classes need a source rebuild. Write complete class names in templates rather than assembling class fragments dynamically. Changing text, or pointing an image to another existing asset, does not require CSS compilation. Review your changes at desktop and mobile widths, particularly after changing typography, spacing or breakpoints.

Start with a matching example page and its JSON settings for sliders, galleries, tabs, accordions and countdowns. Keep IDs unique when duplicating components and preserve their data-* attributes and JavaScript imports. Countdown dates should include a time zone.

site-boot.mjs starts the modules used on each page. Dropdowns open on click, overlays close with their close controls or Escape, and galleries share one lightbox. Sliders and carousels show arrows and dots where configured, and tabs switch to a mobile presentation on small screens. The animation controllers respect the visitor’s reduced-motion preference.

Each component controller keeps its listeners and state inside its root element and provides cleanup. If you move the markup into another framework, preserve the data-* attributes and initialize or destroy the controllers as roots are mounted or removed.

Maps use Leaflet/OpenStreetMap and need internet access for tiles. Video embeds need their external provider. Language links are examples, not an automatic translation system. See Deployment and Backend Services for forms and commerce limitations.

For image replacement and responsive sizes, see Images and Logos.