J3ZZ

Content Management

Front Matter Standards

All collection items must follow these front matter standards to ensure consistency across the site.

Portfolio Items (_portfolio/)

Required Fields:

Category Fields (Required - choose one format):

Optional Fields:

Example - Recommended Structure with Centralized Metadata:

---
layout: work
title: Project Title
work_id: project-title
abstract: "Brief description of what this work is, including medium and key themes."
description: |
  A comprehensive introduction to the work that provides context, goals, and key
  features. This description appears on the work detail page and can include
  **Markdown formatting** for emphasis. Explain the concept, approach, and impact
  of the work in 3-5 sentences.
category: installations
image: /assets/img/project.jpg
order: 15

# Centralized metadata
metadata:
  release_date: "2024-01-01"  # ISO format date (YYYY-MM-DD) for releases, installations, etc.
  year: "2024"
  location: "City, Country"
  role: "Sound artist, composer"
  technology: "Technologies used"
  commissioned_by: "Organization Name"
  # ... additional category-specific fields

sections:
  - type: description  # Displays the description from front matter

  - type: metadata

  - type: text
    title: "About the Work"
    content: |
      Additional detailed project information here.

  - type: image-grid
    columns: 3
    images: [...]
    captions: [...]
---

Example - Multiple Categories:

---
layout: work
title: Project Title
work_id: project-title
abstract: "Multi-format work combining installation and performance elements."
description: |
  This collaborative work explores the intersection of installation art and live
  performance, bringing together multiple artists to create an immersive experience.
  The project was commissioned for a major festival and combines **visual art**,
  **sound design**, and **interactive elements**.
categories: [installations, commissions, live-acts]
primary_category: installations
image: /assets/img/project.jpg
order: 15

metadata:
  release_date: "2024-03-15"  # ISO format date (YYYY-MM-DD)
  year: "2024"
  location: "Paris, France"
  places: "Venue Name"
  role: "Co-creator, performer"
  collaborators: "Artist 1, Artist 2"
  commissioned_by: "Festival Name"
  # Include fields from all relevant categories

sections:
  - type: description  # Displays the description from front matter

  - type: split-hero-metadata
    content_type: "image"
    image: /assets/img/hero.jpg

  - type: text
    title: "About the Collaboration"
    content: |
      Additional details about the collaboration process...
---

Events (_events/)

File Naming Convention: Event files should use date-based naming: YYYY-MM-DD-event-name.md

Required Fields:

Optional Fields:

Example - Basic Event:

---
title: Festival Performance
date: 2025-06-15
time: "20:30"
country: Spain
city: Barcelona
venue_name: Festival Venue
venue_link: https://www.venue.com
ticket_link: https://www.tickets.com/event
description: Live performance at the festival main stage.
---

Example - Event Linked to Work:

---
title: Festival Performance
date: 2025-06-15
time: "20:30"
country: Spain
city: Barcelona
venue_name: Festival Venue
venue_link: https://www.venue.com
ticket_link: https://www.tickets.com/event
description: Live performance at the festival main stage.
work_id: my-project-title
---

Important Notes:

Multi-Category Support

Works can belong to multiple categories. Use either format:

Single category:

category: installations

Multiple categories:

categories: [installations, commissions]
primary_category: installations  # Used for primary overlay color

Adding a New Portfolio Work

IMPORTANT: All new works should follow the standardized structure with centralized metadata and modular sections (see Best Practices).

⭐ RECOMMENDED: Copy _portfolio/1900-01-01-complete-template.md as your starting point - it includes ALL metadata fields and module types with comprehensive examples and guidance.

Recommended Approach - Modular Layout with Centralized Metadata

  1. Create the file: YYYY-MM-DD-work-name.md in _portfolio/ (e.g., 2026-01-01-new-work.md using the actual release/creation date)
  2. Add front matter with required fields: ```yaml — layout: work title: New Work Title work_id: new-work-title # Required: unique ID (A-Z, a-z, 0-9, -, _) abstract: “Brief description of what this work is, medium, and themes.” category: installations # or live-acts, releases, commissions image: /assets/img/work-preview.jpg order: 31 # Higher numbers appear first

Centralized metadata - use category-specific template

metadata: release_date: “2024-01-01” # ISO format date (YYYY-MM-DD) year: “2024” location: “City, Country” role: “Your role” technology: “Technologies used” # … add category-specific fields (see Metadata Reference) custom: - label: “Custom Field” value: “Value”

sections:

# Add more modules as needed

3. **Place images** in `assets/img/`
4. **Test locally**: `bundle exec jekyll serve`
5. **Verify display**: Check both web view and printable WORKS page

**Category-Specific Templates:**
- **Installations**: See [Metadata Reference > Installations](/docs/metadata-reference.html#installations)
- **Live Acts**: See [Metadata Reference > Live Acts](/docs/metadata-reference.html#live-acts)
- **Releases**: See [Metadata Reference > Releases](/docs/metadata-reference.html#releases)
- **Collaborations**: See [Metadata Reference > Collaborations](/docs/metadata-reference.html#collaborations)

### Legacy Simple Layout (Not Recommended)

The simple layout (single image + text content) is still supported for backward compatibility, but all new works should use the modular layout with centralized metadata.

If you must use simple layout:
```yaml
---
layout: work
title: Work Title
work_id: work-title
abstract: "Brief description"
category: installations
image: /assets/img/work.jpg
order: 25

metadata:
  year: "2024"
  location: "City, Country"
  # ... other fields
---
Optional markdown content here.

Note: This approach lacks the flexibility and consistency of the modular sections system.