> For the complete documentation index, see [llms.txt](https://whoisandywhite.gitbook.io/porterwp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whoisandywhite.gitbook.io/porterwp/documentation/directory-structure.md).

# Directory Structure

*PorterWP keeps all theme‑specific code and assets in a single **`/porter`** directory.*

```
my-theme
├── porter
│   ├── blocks/            # ACF blocks (one folder per block)
│   ├── inc/               # Plain‑PHP helpers loaded automatically
│   ├── config/            # JSON config files (see below)
│   ├── assets/            # Theme‑level JS/SCSS processed by gulp
│   └── blocks/make.sh     # Scaffold script for new blocks
└── functions.php
```

### Key Config Files

| File              | Purpose                                                                                                                       |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `porter.json`     | Global options, asset enqueues & premium feature flags                                                                        |
| `posttypes.json`  | Registers Custom Post Types                                                                                                   |
| `taxonomies.json` | Registers Custom Taxonomies & their relationships                                                                             |
| `blocks.json`     | **Single hub** for block registration: links ACF block folders, adds extra block **styles**, and registers block **patterns** |
| `acf.json`        | ACF Option pages (Key Pages, theme colours, etc.)                                                                             |

> **Details:** See the [Configuration Files Index](/porterwp/documentation/configuration-files.md)

***

### The `inc/` autoloader

Any PHP file placed in **`porter/inc`** (or nested sub‑folders) is required automatically on `after_setup_theme`:

* Folders `first/` and `traits/` are loaded *before* everything else.
* Exclude a folder/file with `add_filter( 'porter_wp_inc_filepath_exclusions', … )`.

Returned paths are cached in the `porter_inc_files*` options when the site is in a `production` environment. Cache invalidates when you bump the `version` key inside **`porter/config/porter.json`**.


---

# 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://whoisandywhite.gitbook.io/porterwp/documentation/directory-structure.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.