> For the complete documentation index, see [llms.txt](https://tutorial.frontity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tutorial.frontity.org/part6-custom-post-types.md).

# 6️⃣ Custom Post Types

Although WordPress started out as a blogging platform, it has since developed into a full featured Content Management System (CMS). Part of what makes it so useful as a CMS is it's support for Custom Post Types (CPT). This enables WordPress to host arbitrary data, beyond the default posts and pages.

Frontity is able to work with Custom Post Types, and in this section we'll see how we can use them in our project.

As you will already be aware, our example source data is a travel blog. We have implemented a Custom Post Type in WordPress for our favourite destinations. This CPT is called... *"destinations"* - what else?! 😄

We've also ensured that the CPT is available in the REST API for consumption by our Frontity project.

This section only contains one lesson. That is because it is remarkably easy to get our project to use CPTs, as we're about to see...


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tutorial.frontity.org/part6-custom-post-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.