Zakros Website Content Taxonomy
This proposed taxonomy for Zakros InterArts defines where and how a page surfaces on a the website.
1• SOURCE
The source categorizes based on the canonical location of the item.
Answers "Where does this come from?"
2• DOMAIN
The domain categorizes based on where the item fits within the Zakros Cycle
Answers "What is this for?"
3• AREA (PROJECT)
The Area (Project) categorizes items by their parent area, project, or initiative
Answers "What is this contributing to?"
4• CONTENT TYPE
The content type defines what defines the extended data fields for the item.
Answers "What is this?"
Every Item includes by default
Source • Domain • Area • Title • Publish Date • Content Type
Its Content Type then defines the remaining data fields on the schema
And a "Featured" Checkbox that sends it to the homepage feed.
Internal Content Types
These data fields get added in addition to the standard SOURCE, DOMAIN & AREA.
Event
- Title Image
- Description
- Event Date
- Event Time
- Featured Guest(s)
- Host(s)
- Registration Link
- Event Series Parent
Event Series
- Title Image
- Description
- Series Duration
- Host(s)
Archive Page
- Title Image
- Description
- Original Link
- Original Publish Date
Landing Page
- Title Image
- Description
- Project Title
Info Page
- Title Image
- Description
Documentation Page
- Title Image
- Description
Person / Individual
- Title Image
- Description
- Content Type
Examples
TT Documentation Page
URL: docs.zakros.com/visual-stage/modules-settings (?)
SOURCE: Internal
DOMAIN: Research
AREA: Telematic Theater
TITLE: Modules Settings
PUBLISH DATE: ------
FEATURED: Y/N
CONTENT TYPE: Documentation Page
TITLE IMAGE: -------
DESCRIPTION: -------
MUSEUM EDITION: Creating Tomorrow's Museums Today
URL: https://www.zakros.com/events/museum-edition-01
SOURCE: Internal
DOMAIN: Broadcast
AREA: Events
TITLE: Creating Tomorrow's Museums Today
PUBLISH DATE: ------
FEATURED: Y/N
CONTENT TYPE: Event
TITLE IMAGE: BK-MuseumEdition-EventFlyer-light-01
DESCRIPTION: -------
EVENT DATE: Friday, October 16. 2026 (10/16/2026)
EVENT TIME: 4:00–5:00pm ET
FEATURED GUEST(S): Isabella Bruno
HOST(S): Phyllis Hecht
REGISTRATION LINK: https://www.crowdcast.io/c/museum-edition-01
EVENT SERIES PARENT: Museum Edition
Black | White Archived Page
URL: archive.zakros.com/black-white (?)
SOURCE: Internal
DOMAIN: Broadcast
AREA: Other Projects (?)
TITLE: Black | White
PUBLISH DATE: ------
FEATURED: Y/N
CONTENT TYPE: Archive Page
TITLE IMAGE: -------
DESCRIPTION: -------
External Content Types (In Progress)
OSS Post
Forum Topic
Forum Category
External Links
Notes after drafting this post:
In Areas, where I have define "Other Projects", it does not mean that Other Projects is an explicit category. It is just referring that more projects can fit in this level of taxonomy.
It seems like rather than having rigid guest and host fields for events, it is better to design it this way:Person:
Person: Isabella Bruno
Role: Featured guest
Person: Phyllis Hecht
Role: Host
ChatGPT Review:
Proposed Restructure
Keep the four-part taxonomy:
1. Source — Where does it come from?
Use the specific canonical platform, rather than only “internal” or “external.”
Examples: Zakros, OSS, FORUM, 3SNTV, Third Space Network, Zakros Documentation.
Reasoning: This establishes ownership, canonical links, migration provenance, and synchronization behavior.
2. Domain — What part of Zakros does it serve?
Controlled terms:
- Inside Zakros
- Research
- Create
- Broadcast
- Dialogue
Allow one primary domain and optional additional domains.
Reasoning: Content often moves through multiple stages of the Zakros cycle. A performance might relate to both Create and Broadcast without being duplicated.
3. Area / Project — What does it contribute to?
Connect the item to durable projects or platforms such as:
- Telematic Theater
- OSS
- FORUM
- 3SNTV
- Third Space Network
Allow multiple relationships with one optional primary project. Keep event-series membership separate.
Reasoning: Projects are reusable entities, while labels such as “Events” describe content types. Separating them prevents ambiguous categories such as “Other Projects.”
4. Content Type — What is it?
Recommended core types:
- Page
- Project
- Event
- Event Series
- Archive Record
- Person
- Organization
- External Item
Use Page templates for informational, landing, and feed pages. Use External Item variants for OSS posts, FORUM topics, documentation pages, and future 3SNTV content.
Reasoning: Content type should only determine the record’s fields and validation. Page layout and external source variations do not always require separate CMS types.
Shared Fields
Every feed-eligible item should include:
- Source
- Primary and additional domains
- Primary and additional projects
- Content type
- Title
- Summary
- Canonical URL
- Publication date, when applicable
- Featured media
- Editorial status
- Optional homepage promotion
Replace the generic “Featured” checkbox with “Promote to homepage,” ideally with optional start and end dates.
Key Principle
Source = canonical ownership
Domain = place in the Zakros cycle
Area/Project = organizational relationship
Content Type = schema and required fields
This retains the simplicity of the proposed taxonomy while supporting cross-project content, external aggregation, automated feeds, and historical migration without duplication.
Comments