trail.venturanomadica.com

# Run: run-2026-03-15-16-54-25
# Purpose: Build the initial Trail site and its repository setup

## Task T01

**Description**  
Create the `trail-site` repository in the `Ventura-Nomadica` GitHub organization as a private repository, initialize it with a README, and link the local working copy at the project root to that remote.

**Inputs**  
- GitHub org: `Ventura-Nomadica`
- Repository name: `trail-site`
- Local path: project root

**Outputs**  
- Local git repository initialized at the project root
- `origin` remote pointing at the GitHub repository
- Initial README present locally

**Acceptance Criteria**  
- The local project root is a git repository
- The remote repository name is `trail-site`
- The configured `origin` remote points to the Ventura Nomadica org repository
- If the repository cannot be created because of access or environment limits, the exact blocker is recorded in `results.md`

## Task T02

**Description**  
Read every declared content/style/logo input for this run and create an initial `results.md` entry recording assumptions, contradictions, and any implementation-impacting observations before site implementation begins.

**Inputs**  
- All declared inputs in `operating-instructions.md`

**Outputs**  
- `results.md` initialized with a pre-implementation notes section

**Acceptance Criteria**  
- `results.md` exists before page implementation starts
- Any conflict that could affect implementation is explicitly listed

## Task T03

**Description**  
Create the site's shared foundation at the project root, including the common PHP layout approach, shared stylesheet, any minimal shared JS needed, and reusable header/footer structure required by all pages.

**Inputs**  
- `trail/meta/files/trail-style-guide.html`
- Logo files listed in `operating-instructions.md`

**Outputs**  
- Shared styling and layout files present at the project root
- Reusable header and footer included across all pages

**Acceptance Criteria**  
- All site pages can share one consistent visual system and navigation structure
- The header uses the full logo variant and links to `/`
- The footer includes links to `privacy.php`, `terms.php`, `legal.php`, and `license.php`
- The footer includes `Copyright Ventura Nomadica` with `Ventura Nomadica` linked to `https://venturanomadica.com`
- The footer includes `Created with Trail Framework` with `Trail Framework` linked to `https://trail.venturanomadica.com`

## Task T04

**Description**  
Implement `index.php` using the provided home page content, matching the style guide's visual direction and including the required navigation destinations.

**Inputs**  
- `trail/meta/files/pages/home.md`
- `trail/meta/files/trail-style-guide.html`

**Outputs**  
- `index.php`

**Acceptance Criteria**  
- The page clearly communicates what Trail is, why it exists, and how to get started
- The Home, Docs, Scaffold, Case Studies, About, and Contact nav items are present in the required order
- Core page content is available without JavaScript
- The page renders correctly on desktop and mobile viewports

## Task T05

**Description**  
Implement `about.php`, `case-studies.php`, and `contact.php` from the provided content files, preserving the supplied structure and meaning.

**Inputs**  
- `trail/meta/files/pages/about.md`
- `trail/meta/files/pages/case-studies.md`
- `trail/meta/files/pages/contact.md`
- `trail/meta/files/trail-style-guide.html`

**Outputs**  
- `about.php`
- `case-studies.php`
- `contact.php`

**Acceptance Criteria**  
- `about.php` uses the provided About copy
- `case-studies.php` lists every case study from the source file and clearly marks each as `Coming Soon`
- `contact.php` presents the provided contact methods and any links in usable form
- All three pages use the shared layout and remain functional without JavaScript

## Task T06

**Description**  
Implement `privacy.php`, `terms.php`, `legal.php`, and `license.php` using the provided legal and policy files, adding only minimal structural text if required by the page layout.

**Inputs**  
- `trail/meta/files/pages/privacy.md`
- `trail/meta/files/pages/terms.md`
- `trail/meta/files/pages/legal.md`
- `trail/meta/files/pages/license.md`

**Outputs**  
- `privacy.php`
- `terms.php`
- `legal.php`
- `license.php`

**Acceptance Criteria**  
- Each required file exists and is reachable from the footer
- The page content reflects the supplied source files
- Any direct contradiction between supplied legal copy and other run requirements is documented in `results.md`

## Task T07

**Description**  
Implement `docs/index.php` as a PHP Markdown renderer for files in `../trail-framework/docs/`, including safe page resolution, standard site layout integration, and graceful handling of invalid requests.

**Inputs**  
- Read-only docs dependency at `../trail-framework/docs/`
- Shared layout files created in Task T03

**Outputs**  
- `docs/index.php`

**Acceptance Criteria**  
- A valid page request renders the matching Markdown document from `../trail-framework/docs/[page].md`
- Invalid or missing pages render a graceful not-found experience within the normal site layout
- Directory traversal is prevented
- Raw filesystem paths are not exposed to the user

## Task T08

**Description**  
Ensure all navigation, footer links, and page-to-page flows are wired correctly across the completed site.

**Inputs**  
- All implemented site files

**Outputs**  
- Updated site files as needed

**Acceptance Criteria**  
- Home links to `index.php`
- Docs links to `docs/index.php`
- Scaffold links directly to `https://github.com/Ventura-Nomadica/trail-framework/releases/latest/download/trail.zip`
- Case Studies links to `case-studies.php`
- About links to `about.php`
- Contact links to `contact.php`
- Footer links point to the correct local page files
- No broken internal navigation remains

## Task T09

**Description**  
Review the implementation for accessibility and non-JavaScript behavior, then make the minimal changes needed so each page's core content and navigation work without JavaScript where possible.

**Inputs**  
- All implemented site files

**Outputs**  
- Updated site files as needed

**Acceptance Criteria**  
- Core page content displays without JavaScript
- Navigation remains usable without JavaScript
- Any unavoidable JavaScript dependency is documented in `results.md`

## Task T10

**Description**  
Create or update the root `README.md` so the repository explains what the site is, how to run it locally, and the `../trail-framework/docs/` dependency for the docs renderer.

**Inputs**  
- Completed implementation

**Outputs**  
- `README.md`

**Acceptance Criteria**  
- The README exists at the project root
- It identifies the project as the Trail Framework website
- It explains the PHP requirement and the sibling `../trail-framework/` docs dependency

## Task T11

**Description**  
Run verification checks against the completed site and record the outcomes in `results.md`.

**Inputs**  
- Completed implementation

**Outputs**  
- Updated `results.md`

**Acceptance Criteria**  
- `results.md` records whether each task was completed, partially completed, or blocked
- `results.md` includes verification notes for repository setup, navigation, page availability, docs rendering behavior, and responsive/non-JS behavior
- `results.md` includes notable observations, surprising findings, and reasons for any deviation