• WordPress
• WPGraphQL
• Environment Variables

Add a variable to your .env and then hit npm run dev:

WORDPRESS_API_URL = https://yoursitename.com/graphql

This starter project leans into the WordPress CMS routing capabilities and uses a getNodeByUri query in WPGraphQL to handle any route path that WordPress knows about. This allows you to handle all WordPress content types using the [...uri].astro component. From there, Astro parses the uri and uses that to call getNodeByURI from api.js to fetch data about that resource from the CMS. Once data is returned, we look at the content type and then dynamically resolve a content template from the templates directory.

This project comes with built in support for Post, Page, Tag, and Category types, but could easily be extended for custom post types or other native content types. To add support for a custom post type you would do the following:

1. Add a GraphQL fragment for your post type to getNodeByURI from api.js
2. Add an Astro component as a template
3. Add a case to the switch statement in [...uri].astro to catch the content type and resolve the template

Since routes using rest parameters in Astro come last in the route priority order, you can easily override this catch-all routing pattern by creating a more specific route to handle a given path.

For example, if you want the path /category/food-trucks to be handled by a different Astro component, you can add a corresponding file to the pages directory to override the default ...uri route.

By default, the menu assigned to the Primary menu location will be used for your header menu.