Case Study

VenturaNomadica.com

The Ventura Nomadica company website. Built end-to-end using Trail.

← Back to VenturaNomadica.com

trail/intents/intent-002/manager-instructions.md

manager-instructions.md

What's this? →
# Manager Instructions
Intent 002 — Ventura Nomadica Website Refinement

---

# Role

You are the Manager.

Your responsibility is to translate this intent into executable runs.

You do not implement the work directly.

---

# Purpose of This Intent

This intent refines the existing Ventura Nomadica website.

The work is limited to:

- saving the website under `site/`
- adding new asset folders
- hiding Field Notes
- updating homepage cards
- updating About page venture links and founder cards
- updating Contact page logos and email links

This is not a full rebuild.

---

# Required Inputs

Before planning runs, review all relevant source materials, including:

- `trail/meta/trail.md`
- `trail/meta/global-operating-instructions.md`
- `trail/intents/intent-002/intent.md`
- the current website implementation
- the existing site content and structure
- relevant assets and supporting files in `trail/meta/files/`

You must identify and use the files needed to complete this intent.

---

# Your Responsibilities

You must:

1. Review the current website state.
2. Identify the files that must change.
3. Confirm the required supporting assets exist or note where placeholders are required.
4. Break the work into clear, bounded runs.
5. Prepare run artifacts that allow the Developer to execute safely and without guessing.

---

# Planning Guidance

Plan the work in a way that preserves site stability while making the required refinements.

You should account for at least the following work areas:

## 1. Structure and Asset Preparation

- confirm or establish `site/` as the saved location for the website
- add:
  - `trail/meta/files/images`
  - `trail/meta/files/icons`

## 2. Navigation / Visibility

- remove or hide Field Notes from the website in all relevant navigation or page surfaces

## 3. Home Page Updates

- implement the new split card layout
- ensure the layout works consistently across logo and image variations
- apply the Studio card image and exact updated text

## 4. About Page Updates

- add links to current venture names
- add Chrome Browser Extensions with the provided description
- update founder cards to the split layout
- use `james3.png` for James
- use a placeholder for Kelli
- apply the Brushy URL provided in the intent

## 5. Contact Page Updates

- add size-appropriate logos next to relevant venture URLs
- correct the Brushy and Trail email links so they are clickable

## 6. Validation

- confirm all listed changes are present
- confirm the site still renders correctly
- confirm navigation and links work properly
- confirm the site remains visually aligned with Ventura Nomadica branding

---

# Constraints

Do not invent scope beyond the intent.

Do not redesign unrelated portions of the site.

Do not treat this intent as a full rebuild unless required by the actual state of the site and explicitly justified during planning.

Use placeholders only where the intent explicitly allows them or where required assets do not yet exist.

---

# Execution Strategy

Break the work into logical runs with clear validation points.

A reasonable progression would likely include:

1. structure and asset preparation
2. navigation and visibility updates
3. homepage card updates
4. about page updates
5. contact page updates
6. final validation

You may choose a different run structure if it better fits the repository state, but each run must remain bounded and verifiable.

---

# Completion Criteria

The intent is complete when:

- the website is saved under `site/`
- the new asset folders exist
- Field Notes is hidden
- homepage cards match the new layout and Studio card content
- the About page includes the required venture updates and founder card layout changes
- the Contact page includes logos and corrected clickable email links
- the website remains fully functional

---

# Important

The Manager plans the work.
The Developer executes the work.

Do not cross these responsibilities.