Documentation
Light reading for curious minds.
This section explains how the Taylor vNext site is built, organized, and versioned — a user manual for anyone exploring this portfolio who might not be fluent in developer language or metaphors.
Each tab on this page acts as a reference file — short, clear, and built to help non-technical readers understand what they’re seeing and how to navigate it.
Think of me as a product. This site is encoded in developer-inspired representations — and these docs serve as the translator, turning technical structure into plain human language.
Getting Started with Taylor vNext
This website is essentially my product-management portfolio — a repository where I document everything I do in my career.
Taylor vNext reflects how I build and grow — structured with intention, guided by understanding, and always evolving.
This onboarding guide shows how to explore, interpret, and connect with the site as if you were onboarding to new software.
Step 1 → Understand the build
Taylor vNext follows software logic — continuously deployed and iteratively improved.
The first release, vNext.2025.0, launched the brand and rebuilt the site — shifting it from a marketing portfolio to a product-management framework. This version marks an early stage — expect rapid iteration.
(Check the latest release.)
This structure demonstrates my ability to:
- Design and document products with systems thinking, clarity, and precision.
- Translate technical concepts for non-technical audiences.
- Build repeatable frameworks for communication, process, and iteration.
- Treat career growth like a release cycle—intentional, measured, and well-documented.
Step 2 → Explore the docs
Use the tabs on this page to see how everything connects:
- Glossary — shared terminology and key site language.
- Architecture — how the site is organized and how to navigate it.
- LearnDash / WordPress — context for core platforms used across projects.
- Release Notes — version history of this site, beginning with vNext.2025.0.
Step 3 → Get to know Taylor vNext
Navigate each page to see Taylor vNext — the product — in action. Each section works like a release module: compact, documented, and easy to browse.
You’ll see this README icon as a cue — expand it to reveal plain-language explanations of technical terms.
Step 4 → Connect
If you think I’m the right product manager for your team, let’s connect. Questions are welcome.
Email me at contact@taylord.ink or use the form below.
Key Terms
Sometimes I get carried away with a good metaphor. This is a reference sheet for the recurring terms, metaphors, and system names used throughout the site.
Keep this open while exploring — it’s the translation layer between creative narrative and plain human language.
|
Term |
Definition |
|
Taylor |
The product representation of myself — unsurprisingly, I used my own name. |
|
vNext |
The current release of Taylor — the latest iteration following eight years with StellarWP. |
|
t→ |
The visual icon and shorthand symbol for Taylor vNext. |
|
2025.0 |
A simplified take on software versioning. Major updates follow the format |
|
Release Notes |
Version-specific notes summarizing current and upcoming updates to the site. |
|
Repo |
A repository is where source code lives and evolves—this website serves as the repo for “Taylor as a software product.” |
|
Branch |
Repositories have different “branches” where versions of the same software develop — sometimes side by side, sometimes merged. Retired branches become “legacy,” while experimental ones explore new or unstable ideas. I always have an experimental branch, so it’s always active, usually with one topic at a time (right now, AI). |
|
vLearnDash |
Indicates my time as Product Owner at LearnDash. |
|
vExperimental |
Represents my current experimental branch—focused on AI innovation and agentic systems. |
|
vGiveWP |
A past version of “Taylor as a software product.” My titles changed often at GiveWP, but my function remained consistent until I became Director of Product Marketing at StellarWP. |
|
vStellarWP |
Represents my time as Director of Product Marketing at StellarWP—initially for GiveWP, later for multiple brands. |
|
Human API |
An API is an access point that lets software systems communicate. It defines what can be done (capabilities) and where it can be done (endpoints). My “Human API” defines my skills, tools, and workflows. |
|
README.txt |
A standard file in software projects that onboards users with key details. My README outlines my core values, working style, and guiding principles. |
|
Commit Messages |
LinkedIn recommendations — pulled directly from my profile and sometimes shown in abbreviated form. |
|
Artifact |
A deep dive into a deliverable such as a feature launch or special project. |
|
Book a Demo |
A playful nod to software sales. Instead of scheduling a product demo, you’re booking time to talk with me before hiring. |
|
Context Guide |
Simplified overviews of the core environments referenced throughout each branch — WordPress, LearnDash, and Agentic AI. |
How to Navigate Taylor vNext
The Taylor vNext site is structured like modular documentation for a software repository — each section serves a defined purpose.
Core Structure
Look for the icon on each page — it expands to reveal human-readable explanations and notes.
|
Page |
Purpose |
|
Onboarding |
The home page — a pseudo onboarding screen and dashboard for “Taylor vNext.” It orients you to who I am and how to explore the site. |
|
Human API |
A short biography paired with the skills I bring, the tools and platforms I use, and the knowledge I’ve developed. |
|
README.txt |
The page every potential employer should read first — it defines how I work and what kind of company culture I thrive in. Think of it as a compatibility check for shared values. |
|
Legacy Branch |
A deep dive into my time as Product Owner at LearnDash. The case studies here explore projects I led on the product (none of the information is proprietary or confidential). |
|
Experimental Branch |
Highlights AI-focused experiments and projects — work that began as side innovation and evolved into tools adopted across teams at StellarWP and LearnDash. |
|
Artifacts |
WordPress posts with custom labels — each representing a project or a small collection centered on a single concept. |
|
Commit Messages |
A showcase of my LinkedIn recommendations from my time at StellarWP — genuine testimonials from peers and collaborators. |
|
Book a Demo |
All the ways to get in touch. I typically respond within 48 hours — often much sooner. |
What is LearnDash?
LearnDash is a WordPress-based learning management system (LMS) for building and delivering online courses. It provides a structured framework for lessons, quizzes, progress tracking, and certificates — essentially turning a WordPress site into a full-fledged learning platform.
LearnDash as a Platform Plugin
LearnDash isn’t just another plugin — it’s a platform plugin, meaning it serves as the functional foundation of a website. A WordPress site can technically run multiple platforms, but it’s usually best to anchor the build around one major system for performance and stability.
In most implementations, LearnDash defines the site’s overall structure: users register and log in, progress through learning paths, and interact with content managed inside LearnDash’s templated frontend UI.
Core Features
- Course, Lesson, Topic Hierarchy → organize content into logical learning formats.
- Assessment Tools → quizzes, assignments, and grading.
- Group Management → coordinate learners, instructors, and organizations.
- Reporting → track engagement, completions, and performance.
- eCommerce Tools → sell courses with built-in payment gateways or integrations with eCommerce plugins.
- REST API → connect external systems for automation, reporting, or analytics.
Customer Base
LearnDash serves a wide spectrum of users — from enterprise teams to solo educators.
Typical implementations fall into two main categories:
- End-user builds
WordPress’ accessibility also attracts a large non-technical user base. These projects often need simplified setup flows, stronger documentation, and ongoing customer success support before and after purchase. - Developer-led builds
Many LearnDash sites are implemented by developers — either internal teams or agencies — who handle setup, custom integrations, and performance tuning. Once built, the site is handed off or maintained by the developer.
Developer Community
Among StellarWP products, LearnDash had one of the largest developer ecosystems — shaped by its complexity, legacy codebase, and deep integration potential. The community ranges from plugin developers extending the LMS to agencies building fully custom learning platforms for clients.
Relation to Taylor vNext
In this portfolio, LearnDash represents the Legacy Branch — the closing chapter of my work at StellarWP before launching Taylor vNext.
That experience became the prototype for what followed: a system built on clarity, iteration, and empathy — the balance point between strategy and humanity.
What is WordPress?
WordPress is an open-source content management system (CMS) that powers roughly 43% of the modern web. It gives anyone — not just developers — the ability to publish, customize, and grow online platforms through a flexible, extensible framework.
WordPress as an Open-Source Product
The WordPress ecosystem is built and maintained by thousands of contributors worldwide. A common point of confusion: there are two distinct entities behind “WordPress.”
- Foundation-owned (
WordPress.org) — The original, open-source software maintained by the WordPress Foundation. It’s free to download and can be used on any self-hosted website that meets the technical requirements. You control everything — hosting, configuration, and customization. - Automattic-owned (
WordPress.com) — A hosted service that runs the same software but bundles in hosting, support, and maintenance. When you pay .com, you’re not buying WordPress itself — you’re paying for the infrastructure around it.
Core Components
- Themes — define presentation and layout.
- Plugins — add or extend functionality.
- Block Editor — a modular, visual interface for composing rich content.
- Custom Post Types — structured data models for specialized content like case studies, releases, or documentation.
- REST API — enables integrations, automations, and connections with other systems.
Relation to Taylor vNext
This site runs on WordPress, using its modular architecture to organize dynamic content and layered documentation.
It’s the same foundation that supports the StellarWP ecosystem — including GiveWP and LearnDash — experiences that shaped my approach to scalable systems, thoughtful architecture, and product design that bridges technical structure with human experience.
Agentic AI Overview
For me, AI is an operational layer. Every reference to “AI,” “agents,” or “automation” here connects to practical systems that enhance human work, not replace it.
The goal is augmented intelligence: building products and workflows that amplify creativity, empathy, and strategic decision-making.
Key Concepts
- Agentic AI — Software that can interpret goals, make decisions, and act autonomously within defined constraints. In practice, this means building systems that can manage documentation, triage support, or analyze feedback — all while keeping humans in control. It’s more complex than traditional AI chat systems.
- Model Context Protocol (MCP) — A framework for connecting AI tools to product data and documentation through shared context. It lets agents “understand” a product’s ecosystem before acting, ensuring accuracy, security, and alignment with business logic.
- Human-in-the-Loop — A principle that ensures AI decisions are reviewed or influenced by people. Automation handles speed and scale; humans handle nuance and ethics.
- “Ops” / AI Workflow Systems — Internal tools I design (often in Cursor or Notion) that link data from Jira, GitHub, Help Scout, and docs to streamline product ops — transforming repetitive processes into adaptive systems.
Application in Product Work
In my projects — from LearnDash 5.0’s agentic integrations to AI Ops inside Cursor — AI acts as both infrastructure and collaborator:
- It automates product-ops tasks like triage and backlog grooming.
- It powers context-aware documentation and user guidance.
- It supports decision-making through pattern recognition and data synthesis.
These systems aren’t theoretical; they’re tested, refined, and deployed within real product ecosystems. Each one represents a step toward smarter, safer, more human-centered software.
Why It Matters
I use AI extensively — not as a novelty, but as a core part of how I make work more efficient and communicate more effectively. I truly believe that AI can enhance, not replace, the people behind the product.
Website History & Release Notes
The “changelog” tracks major updates to the Taylor vNext site itself— similar to a product release log. Each entry summarizes things I added, updated, or fixed.
Structure
- Version — identifier (e.g.,
2025.0). - Codename — optional theme or milestone name.
- Highlights — key updates or new modules.
- Changes — details of modifications or optimizations.
- Next — planned updates or in-progress features.
Purpose
To maintain clear version tracking, document evolution, and provide visibility into upcoming iterations — a living record of continuous improvement.
Latest Releases
Details from the most recent three website updates.
version: 2025.1.1
codename: peer-commits// highlights
tweak: finished adding all 21 new recommendations from LinkedIn
tweak: updated all with relationship context
tweak: added dependencies (tags) to peer-reviews// purpose
goal: showcase social proof for Taylor vNext.// vNext
next: 2025.2 → in dev
→ legacy + executive branches (artifact expansion)
version: 2025.1
codename: docs// highlights
feat: new reviews format + meta context
feat: added latest LinkedIn recommendations
feat: new header + tagline
feat: footer + menu refresh
feat: documentation section added
feat: onboarding updated
style: extensive visual + accessibility polish// purpose
goal: improve user onboarding + bridge metaphor for nontechnical users// vNext
next: 2025.2 → in dev
→ legacy + executive branches (artifact expansion)
version: 2025.0
codename: MVP// highlights
feat: new branding + archived legacy branch (vLearnDash) // sunset old build// vNext
next: 2025.0.1 → in dev
→ nontechnical user documentation + artifact expansion
“Taylor is the definition of a strategic Product Owner. She has an incredible ability to see across teams and align moving parts so that everyone works toward the same goal, and her passion is infectious. You just can’t help but be excited for the next big thing she has in the works.
Her leadership in AI enablement has transformed not only how our teams collaborate, but also how I personally approach documentation. She’s helped me develop stronger, more efficient workflows that use AI in practical, meaningful ways, saving time while improving quality.
Taylor also creates some of the best resource docs I’ve ever worked from; clear, complete, and built for real users both internal and external. Working with her makes every project stronger, smarter, and smoother. She’s an absolute asset to any product organization, team collaboration or project. She’s exactly the kind of colleague you want on your team.”
Stephanie Liy
Sr. Technical Writer @ LiquidWeb, Cloud One Digital
on LinkedIn