Case Study
trail.venturanomadica.com
The Trail Framework website. Built end-to-end using Trail.
# Intent — trail-site v1.0
Owner: James
Last Updated: 2026-03-14
---
## Purpose
trail.venturanomadica.com needs to exist. There is currently no public web presence
for the Trail Framework. This intent covers the full build of the initial site —
every page, every feature, and the Git repository. The site is the primary public artifact of the Trail Framework's April 1,
2026 launch. It must be complete, functional, and self-consistent on first ship.
---
## Constraints
- **Technical:** PHP, HTML, CSS, vanilla JS only. No JavaScript frameworks. No npm.
No build tools. No third-party UI libraries.
- **Stack:** The Docs section renders Markdown from a sibling repository
(`../trail-framework/docs/[page].md`) via PHP. This rendering path is fixed.
- **Assets:** Style guide, logos, and page content files are provided in
`trail/meta/files/`. The Developer must use these and must not invent
design decisions not covered by them.
- **Repository:** The `trail-site` Git repository does not yet exist. It must be
created in the Ventura Nomadica GitHub org as part of this intent.
- **Privacy:** No third-party analytics, no tracking scripts, no cookies beyond
what is technically necessary.
- **Deadline:** Site must be launch-ready by April 1, 2026.
- **Maintainer:** Single developer. No solutions requiring ongoing team maintenance.
- **Deployment:** Git repository creation and local setup only. Infomaniak connection and webhook configuration are out of scope for this intent.
- **Accessibility:** All pages must be functional without JavaScript where possible.
---
## Dependencies & Files
**Input files (in `trail/meta/files/`):**
- `trail/meta/files/trail-style-guide.html` — visual design reference; governs
colors, typography, spacing, and component patterns
- `trail/meta/files/logos/` — two logo variants:
- Full: Trail logo plus wordmark
- Logo: mark only
- `trail/meta/files/pages/` — page content files:
- `case-studies.md` — case study content and structure
- `contact.md` — contact page content and requirements
- Additional page content files as present in this directory
**External dependencies:**
- `../trail-framework/` — sibling repository providing the Markdown files
rendered by the Docs section. Read-only. Must exist at this relative path
in the deployment environment.
- Ventura Nomadica GitHub org — `trail-site` repo must be created here.
---
## Scope (In Scope)
- Create the `trail-site` Git repository in the Ventura Nomadica GitHub org
- Build all pages listed in the Header Menu section of Specifics below
- Build all footer pages listed in the Footer section of Specifics below
- Implement the header navigation as specified
- Implement the footer as specified
- Implement PHP-based Markdown rendering for the Docs section
- Apply the style guide throughout
- Use provided logo variants correctly in header and where appropriate
- Use provided page content files for all page copy
- Initialize the repository with a README
---
## Out of Scope (Non-Goals)
- Webhook configuration and Infomaniak deployment connection (future intent)
- Content authoring for pages not covered by files in `trail/meta/files/pages/`
- Blog, news feed, or any dynamic content system
- User accounts, authentication, or any form of login
- Search functionality
- Third-party analytics or tracking
- Any JavaScript framework or build toolchain
- Email handling infrastructure (contact form backend, if applicable, is limited
to what can be declared from `contact.md`)
- SEO optimization beyond semantic HTML and appropriate meta tags
- Internationalisation or multi-language support
- The trail-framework repo itself — it is read-only input, not a deliverable
---
## Assumptions
- The style guide at `trail/meta/files/trail-style-guide.html` is complete and
authoritative. The Developer must not make design decisions not covered by it.
- Logo files in `trail/meta/files/logos/` are production-ready and correctly named.
- Page content files in `trail/meta/files/pages/` are complete and ready to use as-is.
- The trail-framework repo exists at `../trail-framework/` relative to the site root
in the local dev environment. The Manager will not verify this — the
Developer should document any mismatch in `results.md`.
- The GitHub org `Ventura-Nomadica` exists and the Developer has access to create
repositories in it.
- "Scaffold" in the header nav links to the latest release zip at:
`https://github.com/Ventura-Nomadica/trail-framework/releases/latest/download/trail.zip`
This URL is fixed and must not be modified.
---
## Specifics
### File Structure
All site files live at the project root. There are no subfolders for pages.
Named files are used throughout — not `index.php` in subdirectories.
```
dev/trail/trail-site/
├── index.php ← homepage
├── about.php
├── case-studies.php
├── contact.php
├── privacy.php
├── terms.php
├── legal.php
├── license.php
├── docs/ ← PHP Markdown renderer for Trail documentation
│ └── index.php
└── trail/ ← Trail folder structure (meta, intents, runs)
```
The `docs/` folder is the only subdirectory. Its `index.php` handles the
Markdown rendering from `../trail-framework/docs/[page].md`.
---
### Header Navigation
Menu items, in order:
1. **Home** — links to `index.php` (homepage)
2. **Docs** — 'docs/index.php' links to the PHP-rendered documentation section
3. **Scaffold** — direct link to:
`https://github.com/Ventura-Nomadica/trail-framework/releases/latest/download/trail.zip`
4. **Case Studies** — links to `case-studies.php`
5. **About** — links to `about.php`
6. **Contact** — links to `contact.php`
Header logo: use the full logo variant (logo + wordmark). Logo links to `/`.
### Footer
Footer links:
- `privacy.php`
- `terms.php`
- `legal.php`
- `license.php`
Bottom of footer:
- Copyright line: `Copyright Ventura Nomadica` — "Ventura Nomadica" is a hyperlink
to `https://venturanomadica.com`
- Tagline: `Created with Trail Framework` — "Trail Framework" links to
`https://trail.venturanomadica.com`
### Pages
**Home (`index.php`)**
Primary landing page for the Trail Framework. Content is governed by files in
`trail/meta/files/pages/`. The page must clearly communicate what Trail is, why
it exists, and how to get started.
**Docs (`/docs/index.php`)**
PHP renders Markdown from `../trail-framework/docs/[page].md`. The page must
handle navigation between docs, render Markdown to HTML cleanly, and degrade
gracefully if a requested page does not exist.
**Scaffold**
Not a page — this nav item is a direct download link. No page required.
**Case Studies (`case-studies.php`)**
Content is governed by `trail/meta/files/pages/case-studies.md`. All case studies
are marked "Coming Soon" at launch. They must be listed with their details visible
(name, description, intent count, build time breakdown) but not yet linked to
individual case study pages.
**About (`about.php`)**
Content is governed by files in `trail/meta/files/pages/`. See the About page
content file for copy.
**Contact (`contact.php`)**
Content and requirements are governed by `trail/meta/files/pages/contact.md`.
**Privacy (`privacy.php`)**
Legal/policy page. Content must be created based on the product's actual data
practices: no third-party tracking, no cookies beyond technical necessity,
no user data collection. Standard privacy policy structure.
**Terms (`terms.php`)**
Terms of use for the website. Standard terms appropriate for a documentation and
download site. No e-commerce, no accounts, no user content.
**Legal (`legal.php`)**
General legal notices. Includes copyright and any required disclaimers.
**License (`license.php`)**
Describes the Trail Framework's dual license:
- Documentation and methodology: CC BY 4.0
- Scaffold files: MIT
Copyright: Ventura Nomadica.
### Git Repository Setup
- Repository name: `trail-site`
- Organization: `Ventura-Nomadica`
- Visibility: Private initially (switching to public is a separate decision)
- Initialize with a README
- Local path: `dev/trail/trail-site/`
### PHP Doc Renderer
The Docs section must:
- Accept a page parameter (e.g., `?page=quickstart` or via URL rewriting)
- Read the corresponding `.md` file from `../trail-framework/docs/[page].md`
- Render it as HTML within the site's standard layout
- Return a 404-equivalent page if the requested file does not exist
- Not expose the raw file path or allow directory traversal
---
## Deliverables
- `trail-site` repository created in the Ventura-Nomadica GitHub org, initialized,
and linked to the local dev path `dev/trail/trail-site/`
- All HTML/PHP/CSS/JS source files for the complete site
- All pages listed in Scope are functional and styled per the style guide
- PHP Markdown renderer for the Docs section is working
- No broken links in navigation
---
## Acceptance Criteria
- The `trail-site` repository exists in the Ventura-Nomadica GitHub org
- The repository is linked to `dev/trail/trail-site/` locally
- All six header nav items are present and link to the correct destinations
- All four footer links are present and functional
- The copyright line links "Ventura Nomadica" to `https://venturanomadica.com`
- The footer tagline "Created with Trail Framework" links to
`https://trail.venturanomadica.com`
- The Docs section renders a Markdown file from `../trail-framework/docs/` when
given a valid page parameter
- The Docs section returns a graceful error when given an invalid page parameter
- The Case Studies page lists all case studies with "Coming Soon" labels
- The About, Contact, Privacy, Terms, Legal, and License pages all exist and
contain appropriate content
- No page requires JavaScript to display its core content
- The site renders correctly on desktop and mobile viewports
- The style guide is applied consistently across all pages
---
## Notes
The trail-site is itself a Trail project. The Trail folder structure for this project
lives under `dev/trail/trail-site/trail/`. The site source lives alongside it.
The Ventura Nomadica website (`venturanomadica.com`) is a separate project and a
separate Trail. It is referenced for context only — it is not a dependency of this
intent.
The case studies are placeholders at launch. Individual case study pages are a
future intent.
Contact page behavior (form submission, email routing, etc.) is governed entirely
by `trail/meta/files/pages/contact.md`. Do not invent requirements not stated there.