Skip to content
Baseworks KB

Event Post Guidelines

Created 2026-04-01
Tags websiteeventsguidelinesworkflow

Guidelines for event vault notes and the workflow for publishing events to baseworks.com. For technical details of the event post system (ACF fields, taxonomies, template routing), see event-post-system.

Event Note Location & Naming

Section titled “Event Note Location & Naming”

Event notes live in 02-areas/website/events/.

Filename convention: YYYY-MM-slug.md

  • Year and month = the start month of the event
  • Slug = short descriptive identifier

Examples:

  • 2026-04-montreal-study-group-spring.md
  • 2026-03-montreal-practice-sessions-spring.md
  • 2026-06-brnet-padua.md

Two Types of Events

Section titled “Two Types of Events”

The event CPT on baseworks.com covers two distinct types. The vault note format is the same, but some fields differ.

TypeDescriptionExamples
Program eventA Baseworks-run event — Study Group cohort, Practice Sessions season, Open Day, Study LabMontreal Study Group Spring 2026, Practice Sessions Spring 2026
Conference eventBaseworks presenting or participating at an external eventBRNet 2026, ICNN 2025, Neuropsychology Day

Vault Note Format

Section titled “Vault Note Format”

Frontmatter

Section titled “Frontmatter”
---
title: "Full Event Title"
type: event
event-type: program  # or: conference, open-day, study-lab, practice-session, study-group
status: draft        # or: ready-to-publish, published
wp-post-id:          # populated after publishing
wp-url:              # e.g. /event/montreal-study-group-spring-2026/
language: en


# Dates
event-date: YYYY-MM-DD        # start date
event-date-end: YYYY-MM-DD    # end date (same as start for single-day)
event-date-text: ""           # human-readable, e.g. "April 4–May 16, 2026"
event-month: ""               # first month, e.g. "April"
is-single-day: false


# Location
venue: ""                     # e.g. "Proto Studio"
venue-address: ""             # full address, e.g. "5333 Av. Casgrain suite 1107, Montréal"
city: ""
country: ""
region: ""                    # e.g. "NORTH AMERICA" or "EUROPE"
latitude: ""
longitude: ""


# Author / Facilitator
author: pandasia               # pandasia (Asia only), basework (Patrick only), baseworks (both)


# Organizer
organizer: Baseworks           # "Baseworks" for events we run; conference name if external


# WordPress taxonomies
wp-event-cat: ""               # e.g. "Study Group", "Baseworks Practice Session"
wp-event-topic: ""             # e.g. "Baseworks Practice"
wp-event-level: "UNIVERSAL"
wp-event-year: ""              # e.g. "2026"
wp-tags: []                    # list of tag names


# Template
elementor-template: global     # global (auto via event_year), or: custom (needs separate Elementor build)
elementor-template-status: ""  # if custom: draft, ready, or leave blank
elementor-template-notes: ""   # any notes about template timing/status


# Redirect
redirect-to-page: false        # true if this event post should redirect to a landing page
redirect-url: ""               # target URL if redirect-to-page is true


# Booking (leave blank if not used)
show-booking-section: "No"     # "Yes" or "No"
show-student-booking-button: "No"
booking-url: ""
student-booking-url: ""
facilitator-title: "FACILITATORS"  # label above facilitator profiles


# Media (populated when images are ready)
featured-image-id: ""          # WP attachment ID after upload
banner-image-id: ""            # WP attachment ID for bg banner (no text overlay)


# SEO
seo-title: ""
seo-description: ""
og-title: ""
og-description: ""
og-image-url: ""
og-image-id: ""
schema-location-name: ""       # venue name for event schema
schema-location-address: ""    # full address for event schema


created: YYYY-MM-DD
tags:
  - event
  - relevant-tags
related:
  - "[...](//)"
---

Body

Section titled “Body”

The body should contain the clean event description — what will populate post_content in WordPress. Write in HTML (not markdown), since it’s published directly via WP-CLI.

Structure for program events:

  1. Short introductory paragraph or tagline
  2. Session/schedule details (if applicable)
  3. Venue and logistics
  4. About the program (optional — can reference the hub page instead)

Structure for conference events:

  1. Event overview
  2. Presentation details (title, abstract summary, time slot)
  3. About the conference
  4. Presenter bio

Translation Section

Section titled “Translation Section”

Translations go at the bottom of the same note, below a horizontal rule and a ## [Language] heading. Example:

---


## French


[French translation of the event description]

Publishing Workflow

Section titled “Publishing Workflow”

Use the /create-event-post skill to publish. The skill handles two starting points:

Path A — Note already exists:

  1. Skill reads the vault note
  2. Prompts to confirm or fill in any missing metadata fields
  3. Confirms publishing decisions (template, redirect, booking)
  4. Publishes via WP-CLI and updates the note with wp-post-id and wp-url

Path B — No note yet:

  1. Skill gathers event information from your description
  2. Creates the vault note with all fields filled in
  3. Proceeds to Path A

Checklist Before Publishing

Section titled “Checklist Before Publishing”
  • Event description written in body (HTML)
  • All frontmatter fields filled in (or confirmed as intentionally blank)
  • Featured image uploaded to media library — ID recorded in featured-image-id
  • Banner image uploaded to media library — ID recorded in banner-image-id
  • SEO title and description written
  • OG title, description, and image confirmed
  • Author set correctly (pandasia / basework / baseworks)
  • Taxonomy terms confirmed (event_cat, event_year, city, country, region)
  • Elementor template decision confirmed: global or custom?
    • If custom: is template already built, or will it be built after post is created?
  • Redirect decision confirmed: direct to post, or redirect to landing page?
  • Translation: required now, or deferred?

Post-Publish Steps

Section titled “Post-Publish Steps”
  • Update wp-post-id and wp-url in vault note frontmatter
  • Update status to published
  • If custom Elementor template needed: note it as a pending step
  • If redirect snippet needed: add to Fluent Snippets and log in changelog
  • Commit and push vault note changes
Section titled “Related”