Website Functionalities — Index

Documentation of how the Baseworks website ecosystem is built and how its parts connect. Use this index to find the right doc before asking Claude to load context.

---

What are you looking for?

How the three sites connect (ecosystem-wide)

• Website Ecosystem Overview — The full picture: baseworks.com, practice.baseworks.com, crm.baseworks.com, WP Fusion tag-based access, FluentCRM automation, Uncanny Automator recipes, and how a purchase flows through the system
• Cross-Site User Sync (WPRUS) — How user accounts and login sessions sync between sites, admin account isolation, BuddyBoss “View As” fix

The practice site specifically

• Practice Site Platform Infrastructure — BuddyBoss, LearnDash, the BW Activity Plugin, Formidable forms, code snippets, dashboard architecture, WPRUS configuration notes

Specific plugins and features

• Custom Code Overview — MU-Plugins, Snippets & Theme Overrides — Full inventory of all custom PHP on both sites: what each mu-plugin and code snippet does, what’s active vs archived, vendor vs custom
• BW Activity Plugin — Design & Implementation Plan — The custom activity tracking plugin (wp_bw_activity table): design decisions, implementation history, shortcode reference
• Practice Sessions Booking Widget — The mu-plugin for returning-participant booking with WP Fusion gating and sliding-scale discounts

Content types and post systems

• Event Post System — Custom Post Type, Fields & Templates — The event CPT: all ACF fields with formats and field keys, taxonomies, Elementor template routing logic, the author/facilitator pattern, redirect pattern for events with separate landing pages, and the connection to vault notes

Automated data pipelines (Obsidian vault sync)

• Vault Sync Systems — How data flows automatically from the sites into the Obsidian knowledge base: questionnaire export (live), segment feedback (planned)
• Segment Feedback Automation Plan — Development plan for automating segment feedback sync from practice.baseworks.com; includes field spec, file naming, and VPS cron requirements

Where changes are recorded

• Baseworks Changelog Repo — The git repo that logs all code changes, plugin snapshots, and server-side modifications across all sites

Historical decisions

• Functionalities Archive — Archived audits and design decisions (e.g. why the activity log moved from Formidable to a custom plugin)

---

Relationship between these docs and the changelog

These Obsidian docs capture architecture and decisions — what the system is, why it’s built this way, and what to watch out for. They change slowly.

The changelog repo captures what changed and when — code diffs, plugin files, and dated entries for every modification. It changes with every session.

When something breaks or needs to be debugged, start here for context, then check the changelog for recent changes.