Communications Post Guidelines

Created 2026-06-17

Tags communicationsguidelineswritingwebsite

Guidelines for writing Baseworks communications posts — the communications post type at baseworks.com/communication/.

Skill: write-communications-post — the Claude Code skill that executes this workflow. Related: write-blog-post, communications-guide, _site-content-inventory

What Is a Communications Post?

Communications posts document Baseworks’ external appearances and collaborations with named outside entities. They sit at the intersection of record-keeping and editorial content — part press archive, part reflective account.

They differ from blog articles (article post type) in several ways:

	Communications post	Blog article
WordPress post type	`communications`	`article`
Vault location	`02-areas/website/communications/`	`02-areas/website/blog-articles/`
ACF fields	location, entity, details HTML	subtitle, last-updated, FAQ
Primary function	Document a specific appearance or collaboration	Original editorial content
Length	Variable — can be brief or substantial	Typically longer
Byline	Not always named (appearance as a brand)	Always attributed

When to Create a Communications Post

Create one when Baseworks (or a named Baseworks person) appeared in, presented at, or collaborated with an external entity:

Conference or academic meeting — poster, talk, panel, keynote
Podcast or radio / broadcast interview
Press feature — article, newsletter, or media mention
Panel discussion — at an external event
Collaborative workshop — with a named outside organization

Do not create a communications post for internal events (study groups, open days, program sessions) — those use the event post type.

WordPress ACF Fields

The communications post type has four ACF fields, all set via WP-CLI at publish time:

Field key	Label	What goes here
`location`	Location	Geographic location — typically city + country, or just country (e.g., “Italy”, “Montreal, Canada”)
`project`	Entity	The collaborating organization, conference, or platform name (e.g., “BRNet”, “Material For The Brain”)
`details`	Details	HTML block rendered in the sidebar — see format below
`communication_image`	Communication Image	WordPress media library ID of the featured image

The `details` HTML format

The theme renders this as a small info block beside the post. Use inline HTML with <strong> labels and <br> line breaks. Adjust labels based on the appearance type:

Conference / poster / panel:

<strong>Format</strong>: Conference | Poster Presentation<br>
<strong>Presenter:</strong> Asia (Ksenia) Shcherbakova<br>
<strong>Date:</strong> June 8–9, 2026<br>
<strong>Conference Website:</strong> <a href="URL" target="_blank" rel="noopener">BRNet</a><br>
<strong>Abstract:</strong> <a href="URL" target="_blank" rel="noopener">Presentation Title</a>

Podcast / audio interview:

<strong>Format</strong>: Press | Podcast<br>
<strong>Host:</strong> <a href="URL" target="_blank" rel="noopener">Host Name</a><br>
<strong>Date:</strong> Month DD, YYYY<br>
<strong>Podcast Website:</strong> <a href="URL" target="_blank" rel="noopener">Podcast Name</a><br>
<strong>Episode Page:</strong> <a href="URL" target="_blank" rel="noopener">Episode Title</a>

Panel discussion:

<strong>Format</strong>: Panel Discussion<br>
<strong>Panelist:</strong> Asia (Ksenia) Shcherbakova<br>
<strong>Moderator:</strong> Name (Affiliation)<br>
<strong>Date:</strong> Month DD, YYYY<br>
<strong>Event:</strong> <a href="URL" target="_blank" rel="noopener">Event Name</a>

Vault File Location and Frontmatter

Vault files live in 02-areas/website/communications/. Filename: YYYY-MM-slug.md.

---
title: "Post Title"
created: YYYY-MM-DD
type: communications-post
status: draft
language: en
wp-post-id: ""
wp-url: ""

# ACF metadata (for WP publish reference)
acf-location: "City, Country"
acf-entity: "External partner / conference name"
acf-format: "Conference | Poster Presentation"
acf-date: "Month DD, YYYY"
acf-website-label: ""
acf-website-url: ""
acf-episode-or-abstract-label: ""
acf-episode-or-abstract-url: ""

related:
  - "[related-note](/related-note/)"
tags:
  - communications
  - relevant-tags
---

Body Content Conventions

Structure

Communications posts can be brief (a short summary of a podcast episode with an embed) or long (a full reflective account of a conference appearance with observations from the program). The source material determines the length — do not pad, do not truncate to fit a template.

Typical structure for a conference / research appearance:

Opening paragraph — who was involved, what the appearance was, where and when
The presentation or contribution — title, core argument or findings, methodology summary
Context — the field’s current framing, where Baseworks sits within it
Observations from the program — other talks or presenters that are relevant, with names and affiliations
Closing — related baseworks.com content

Typical structure for a podcast / interview:

Opening paragraph — who was involved, the host, the platform
What was discussed — key talking points and themes
Body sections — one per major theme
Embedded media (YouTube, Spotify, etc.)
Closing — related content links

Voice standards

The same voice rules that govern blog articles apply here. Key reminders for this format:

Report, do not pitch. Communications posts describe what happened and what was covered. They are not event promotions.
Accurate field descriptions. If the conference’s dominant framing was clinical or pathological, say so clearly — as a factual observation, not as a contrast against which Baseworks is positioned.
Name people precisely. Full name and affiliation on first mention. Do not paraphrase credentials.
Domain-expert audience. Researchers, clinicians, and academics who attended the same event may read this. Write at a level that holds up for them.

Embedded media

For podcast episodes: embed the Spotify <iframe> or YouTube  block. For conference talks (if recorded and public): embed the recording if available.

Use Gutenberg block HTML format matching existing communications posts on the site.

Source Material Required Before Writing

For conference appearances:

Conference program / schedule (for presenter names, affiliations, talk titles)
Abstract (the submitted abstract, if any)
Any recordings of observed talks (use /transcribe)
Video of Baseworks’ own presentation or panel (use /watch)
Photos (processed via /compress-photos before publishing)

For podcast appearances:

Episode URL (for embedding)
Episode page link
Any show notes or summary provided by the host

write-communications-post — the skill that executes this
_site-content-inventory — full communications archive
communications-guide — for participant and collaborator communications (separate from this)
_blog-post-guidelines — for blog articles