Skip to content

Astro page structure

We have a dynamic page structure to account for the different pre slugs we use in the backend.

So a slug can look like this: /solutions

Or like this: /resources/blog/blog-slug

In this case /resources/blog would be the pre slug that indicates in which folder the template is.

Everything is inside our [lang] folder, because we use a URL structure where we determine the language of the page using that folder:

www.netwrix.com/en/solutions

This contains the home page, that’s why here we send our main page flag to our query:

const content = await the_query({ type:'pages', language: lang, slug: `home`, isMainPage: true, isDraft });

This contains our modular pages, like netwrix.com/en/solutions or netwrix.com/en/about.

This is the only page aside from our index page that is fixed to a certain slug, because we need it to be specific to be able to send information to our Marketo forms to prefill them correctly.

We have four folders inside our [lang] one:

  • author
  • customer-stories
  • demo

All of these contain only a [slug].astro file that creates the single page associated to that post type.

And [preSlug], that goes one level deeper.

This file will create modular pages for a few post types that are not on the root. This will also create modular pages for some documents that belong to the post type pages but are given a pre slug for SEO reasons.

  • Landing pages
  • Partners
  • Support
  • Resources
  • Cybersecurity Glossary
  • Demo
  • Customers
  • Thank you
  • Environments (not available on launch)
  • Integrations (not available on launch)

All resources and cybersecurity glossary items will be available in this folder.

  • /architectural-concepts
  • /blog
  • /compliance
  • /cuber-security-attacks
  • /event
  • /guides
  • /news
  • /podcast
  • /publications
  • /research
  • /security-concepts
  • /security-frameworks
  • /webinar
  • /webinars - webinar series

This level includes files that need an extra piece of slug before their dynamic part or final pages for things like downloads or demos.

This page contains the following post types or pages:

  • Subproducts
  • Professional services
  • Use cases for solutions

For demos of specific features of a product, like netwrix.com/en/products/password-policy-enforcer/product-tour-online-demo.

For pages that unify all available demos for a product, like for Netwrix Auditor.

For single download pages in products or freeware. This is where Netwrix’s API is called to get the latest versions of a product.

For a single demo of a whole product or solution.

This last folder contains copies of:

  • /[feature]-online-demo.astro
  • /all-demos.astro
  • /download.astro
  • /online-demo.astro

These are used for demos and downloads of subproducts, for instance, that go one level deeper.