Pages

For a policy, a guide, or any page of text. Every file in src/content/pages/ becomes a page.

1. Create a new file, for example src/content/pages/english/our-approach.md. The file name becomes the URL: /our-approach/.

2. Add a title, a description, and the Markdown body:

   ---
   title: "Our approach"
   description: "How we work with clients, from first call to final report."
   ---
   
   ## How we start
   
   Text of the page...

3. Create the French version in src/content/pages/french/ with the same file name.

4. Add a link to it in src/config/menu.en.json and menu.fr.json.

A text page shows the page header, the body, and the features and call to action sections (featuresSection and ctaSection blocks). For a legal page in the style of the privacy policy, copy privacy-policy.md: its legalPage block holds the sections, the “last updated” line, and the contact box.

For a landing page that reuses Consultiz’s sections.

1. Copy a route with a similar structure, for example src/pages/[...lang]/pricing.astro, to src/pages/[...lang]/advisory.astro. The file name becomes the URL: /advisory/.

2. Make it read its own content file. Change getEntryCTM("pricing", "-index", ...) to getEntryCTM("pages", "advisory", Astro.currentLocale), and create src/content/pages/english/advisory.md with a title and the named blocks you need.

3. Stop the text-page route from building the same file: in src/pages/[...lang]/[page].astro, filter out advisory the way webinar-event is filtered out.

4. Replace the sections inside <Base> with the ones you want, and pass each its block, for example <FaqCentered content={entry?.data?.corporateFaq} />. Use block names from sectionsSchema in src/sections.schema.ts.

5. Create the French content file and add the page to the menus.

Section 6 of NEXTJS-TO-ASTRO-GUIDE.md in the theme walks through the same steps with full code.