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

# Portfolio Projects

Project types, galleries, technologies and links.

**Dashboard → Portfolio**

## Project types

**Portfolio → Types**

You define these. They are the categories your work falls into — Web Design, Game Development, 3D Art, Branding, whatever fits.

Each has a name, description, icon and position. Types become the filter row on the public listing.

A type with no published projects is hidden from the filter, so visitors never click through to nothing.

## Creating a project

| Field          | Notes                                             |
| -------------- | ------------------------------------------------- |
| Title          |                                                   |
| Type           |                                                   |
| Summary        | One or two lines, shown on cards                  |
| Body           | The full write-up. Rich text                      |
| Cover image    | Shown on the listing                              |
| Cover fit      | How the image sits in its frame                   |
| Gallery        | Additional images                                 |
| Gallery layout | How they are arranged                             |
| Client name    | Optional                                          |
| Completed on   | Optional date                                     |
| Technologies   | Tools used, with brand icons chosen automatically |
| Tags           | Free-form                                         |
| Links          | Website, repository, video, download              |
| Featured       | Pulls it to the front                             |
| SEO            | Title and description                             |

## Publishing

**Draft** projects are invisible to visitors. Staff with `portfolio.view` can preview them at the real address, so work can be reviewed in place before it goes live.

## The public listing

`/portfolio` by default. Change it with `PORTFOLIO_PREFIX` in `.env`.

The listing is an ordinary **page**, editable in the page builder — add a heading, a standfirst, or anything else around the grid.

An unknown type in the URL returns 404 rather than silently showing everything, so a mistyped filter does not quietly lie.

## The Portfolio grid block

Put projects on any page. Pin it to one type, or leave it open and offer the filter row. Choose columns, a maximum, and the wording when there is nothing to show.

Useful for a “selected work” section on a home page.

## Ordering

Drag projects to reorder them. **Featured** projects can be pulled out separately by the grid block.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hollow-peak.gitbook.io/docs/portfolio/portfolio-projects.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
