VCH Project Templates & Assets

This folder contains templates and assets for managing VCH/Windesheim projects.

Templates Available

1. AI_PROJECT_CONCEPT_TEMPLATE.md

Use this for: Planning new AI/ML project ideas before committing resources

Key features:

3 Minute Rule pitch framework (Brant Pinvidic’s 6 questions)
Agile sprint planning with detailed milestone table
Visual asset management checklist
Complete worked example (coffee quality prediction)

When to use:

You have an AI project idea but need to think it through
You want to pitch a project to partners or get approval
You need to plan timeline and resources before starting

2. PROJECT_TEMPLATE.md

Use this for: Adding completed or ongoing projects to the website

Key features:

Simple format for basic project information
Fields for links, status, descriptions
Quick to fill out for existing projects

When to use:

You have a finished project to showcase
You’re documenting an ongoing student project
You need a quick project card on the website

Folder Structure

Each project should have its own folder with assets:

assets/projects/
├── PROJECT_TEMPLATE.md                    ← Template for simple projects
├── AI_PROJECT_CONCEPT_TEMPLATE.md         ← Template for AI projects
├── README.md                              ← This file
├── re-used/                               ← Example: completed project
│   └── project-info.md
├── beyond-the-bar/                        ← Example: completed project
│   └── project-info.md
└── ai-coffee-quality/                     ← Example: concept project
    ├── README.md                          ← Asset documentation
    ├── hero-image.png                     ← Main visual (1200x600px)
    ├── thumbnail.png                      ← Card preview (400x300px)
    ├── diagrams/
    │   ├── model-architecture.png
    │   └── user-flow.png
    └── screenshots/
        ├── dashboard-v1.png
        └── mobile-mockup.png

Workflow: From Concept to Website

For AI Project Concepts

Copy the template

cp AI_PROJECT_CONCEPT_TEMPLATE.md my-project-concept.md

Fill out the 3 Minute Rule pitch (6 questions)
- What is it?
- How does it work?
- Are you sure it can work?
- Can you do it?
- What’s the value?
- What are the risks?
Plan the timeline
- Decide sprint length (usually 2 weeks)
- Fill out the milestone table with specific dates
- Plan Agile ceremonies (standups, reviews, retros)

Create asset folder

mkdir -p assets/projects/my-project-name
mkdir -p assets/projects/my-project-name/diagrams
mkdir -p assets/projects/my-project-name/screenshots

Add visual assets
- Create or find a hero image (1200x600px)
- Make a thumbnail (400x300px)
- Add diagrams if you have them
- Document in the folder’s README.md
Get approval
- Review with Christiaan
- Confirm with partners if applicable
- Decide: go, no-go, or revise
Add to website with “Concept” badge
- Shows you’re exploring this idea
- Gauges interest from students/partners
- Can update status as project progresses

For Completed/Ongoing Projects

Use the simple template

cp PROJECT_TEMPLATE.md projects/my-project.md

Fill in basic info
- Title, category, status
- Short description (1-2 sentences)
- Links to GitHub, website, paper, etc.
Add assets (if you have them)
- Create folder: assets/projects/my-project/
- Add thumbnail and hero image
- Update paths in the markdown file
Provide to Claude to add to the website

Image Guidelines

Required Sizes

Hero image: 1200x600px (2:1 ratio) - Used on project detail pages
Thumbnail: 400x300px (4:3 ratio) - Used on homepage project cards
Logo/Icon: 200x200px or SVG - Optional project branding

File Formats

Photos: JPG (for smaller file size)
Graphics/Diagrams: PNG (for quality)
Logos: SVG preferred (scalable)

Naming Convention

hero-image.jpg or hero-image.png
thumbnail.jpg or thumbnail.png
logo.svg or logo.png
diagram-[name].png (e.g., diagram-architecture.png)
screenshot-[name].png (e.g., screenshot-dashboard.png)

Best Practices

Keep files under 1MB for web performance
Use descriptive alt text for accessibility
Compress images before adding to repo
Update assets as project evolves (mockup → prototype → final)

Agile Project Management

All AI projects follow Agile principles:

Core Principles

Iterative development: Build in small increments
Regular feedback: Demo every sprint
Adapt and improve: Use retrospectives
Deliver value: Focus on working software

Standard Sprint Cycle (2 weeks)

Sprint Planning (Monday Week 1)
- What will we accomplish this sprint?
- Break work into tasks
Daily Standups (Throughout sprint)
- What did I do?
- What will I do?
- What’s blocking me?
Development (Week 1-2)
- Build, test, document
Sprint Review (Friday Week 2)
- Demo working software
- Get stakeholder feedback
Sprint Retrospective (Friday Week 2)
- What went well?
- What could improve?
- What will we change?