Project Overview

Summary of the MANTEC website redesign project

Phase: Design & Planning

Total Pages

Training Courses

Custom Post Types

Open Items

Project Summary

MANTEC is a Manufacturing Extension Partnership serving South Central Pennsylvania. This redesign transforms their WordPress site from a static informational presence into a dynamic platform with Salesforce/Account Engagement integration.

The client supplied a comprehensive 92-page content document covering full site copy organized around 8 manufacturer challenges. The document is strong on IA and problem-first structure, with complete content for 54 pages and 16 training courses. Functional specifications (registration, payment, calendar, Salesforce) are separate from the content layer — this is expected architecture.

KEY INSIGHT

The 8 challenge areas (Boost Productivity, Find & Retain Employees, etc.) serve as the connective tissue. Each challenge page cross-references related solutions, training, and resources — the same training course or solution appears under multiple challenge pages. The navigation hierarchy diverges from the underlying data model.

Contract & Timeline

Engagement	Website Redesign + Salesforce Integration
Phase	Discovery complete · Design kickoff upcoming

Project Milestones

Milestone	Target
Homepage Design (R1)	Week of April 13
Homepage Approval	Week of April 20
Interior Page Designs (R1)	Week of May 21
Interior Page Approval	Week of May 11
Development Link Presentation	Between weeks of July 27 & August 3
Client Review & Launch	Upon approval (no Friday/holiday weekend launches)

Content Document Coverage

Cindi Moses provided a 92-page content document covering the full site. Here's what's covered:

Content Complete 92%

All pages, challenges, solutions, courses, programs

Minor Gaps 4%

Learning Center TBD, 2 course placeholders

Functional Spec N/A

Registration, payment, CRM are dev-phase items — see Gap Analysis

Dashboard Evolution

Version	What Changed	Artifact	Confidence
v1.0	Initial sitemap tree, data architecture, content builder blocks, gap analysis from content doc.	v1.0 dashboard ↗	Low — content doc only, no site discovery
v2.0	Deep site discovery (72 GF forms, dead SF, $258K payment data, 4 abandoned systems). Corrected course count 14→16. Added Current State, Content Inventory tabs.	Superseded	Medium — content + current state mapped, but gaps unaddressed
v2.1	Whole-project gap analysis (12 resolved, 6 planned, 7 open). SF integration timeline (past → present → direction). Nav proposal tab with two options. Project confidence metrics.	Superseded	High — all inputs reconciled, open items require client input
v2.2	Salesforce org audit (19-page, Derek Beitz) integrated — SF API access and Pardot confirmed, integration clarity 40%→65%. Brand assets received. PM timeline added (6 milestones).	← You are here	High — SF audit in hand, field mapping session is primary remaining gap

REFERENCE: LEGACY SYSTEM DOCUMENTATION

The following documents the current site's technical state for reference purposes only. These patterns represent technical debt we are actively replacing. The new build is a clean-room implementation — none of these systems carry forward.

Gravity Forms (CMS Anti-Pattern)

$258K+

Revenue Processed

139

Database Tables

Gravity Forms: The CMS Anti-Pattern

72 total forms functioning as a content management system:

28 paid course registration forms — 53–62 fields across 4 pages each
29 free event forms — 30+ fields, cloned templates
15 other forms — contact, surveys, podcasts, internal

THE PROBLEM

To create a training event, staff must duplicate an entire form, then manually edit course details (dates, times, location, description, pricing) embedded as HTML blocks INSIDE form fields. Every single event requires raw code editing.

Salesforce / CRM Status

CRM Perks Salesforce plugin: Installed but OAuth connection FAILED in February 2024.

Result: Zero integration, zero data flow between WordPress and Salesforce for 2+ years. Any registration data going to Salesforce must be entered by hand.

Pardot tracking (inconsistent):

piCId 10797 via WPCode footer snippet
piCId 565372 via Insert Headers & Footers
Both under Account ID 928773

Payment Processing

Authorize.Net merchant account (active):

$258,000+ processed through GF Authorize.Net feeds
31 Authorize.Net feeds (30 active)
Pricing ranges $15–$4,495 per transaction
0 active entries in GF database (entries have been purged)

Opportunity: The existing Authorize.Net merchant account handles the payment processing. We keep the integration and build proper CPTs + forms instead of using GF forms.

Abandoned Registration Systems

4 systems installed but not used:

Event Espresso
Tables defined in DB, zero data
WooCommerce
34 tables in DB, 0 orders ever placed
The Events Calendar
2 records, never used
Eventbrite
Organization account exists, OAuth empty

Infrastructure & Scale

Hosting

Bluehost shared hosting

PHP 8.x, WordPress

Page Builder

WPBakery

10,589 vc_empty_space shortcodes

Navigation

58 main items

28 training menu items

Redirects

685 total

Many legacy + spam

Page

CPT

Navigation Structure Proposal

Two approaches to visitor-facing navigation — same underlying page architecture, different grouping strategies

See both options side-by-side with live hover navigation

IMPORTANT DISTINCTION

The Sitemap Tree and Sitemap Table tabs show page architecture — the underlying URLs, CPTs, and data relationships. This tab addresses visitor-facing navigation — what appears in the header, dropdowns, and footer. Same pages, different organization for different audiences (robots vs humans).

Option A: Client IA Structure Cindi's proposal

Follows the content document's organization directly

Challenges ▾ Solutions ▾ Training ▾ Programs & Events ▾ About ▾ Learning Center Contact ▾

6 top-level items + Contact. Challenges and Solutions as separate dropdowns. All 8 challenge areas visible in dropdown. Training shows all 16 courses. Homepage shows 8 individual challenge cards.

Strength: Maps 1:1 to the content doc. Cindi's mental model. SEO-clear structure.
Concern: 7 nav items is heavy. 8 challenge cards on homepage creates a long scroll (Bruce dislikes). Visitor must understand MANTEC's taxonomy to navigate.

Option B: Consolidated Navigation Proposed

Groups related content for faster visitor scanning

How We Help ▾ Training ▾ Programs & Events ▾ Resources ▾ About ▾ Talk to Us

5 items + CTA button. "How We Help" mega-menu: challenges on left, solutions on right — one hover, full picture. Training organized by track (Continuous Improvement, Leadership & Management, Safety & Quality, Technical Skills). Contact elevated to always-visible CTA button. "Resources" replaces "Learning Center." Homepage shows 4 grouped cards instead of 8.

Strength: Fewer items = faster scanning. Mega-menu reveals both problems AND solutions in one hover. 4 homepage cards = shorter page (Bruce). CTA button creates conversion path.
Concern: Groups Cindi's carefully separated categories. Mega-menu is more complex to build.

Shared Between Both Options

Same 54 pages. Same URLs. Same CPTs and taxonomies. Same SEO structure. Same footer layout. Same content — only the top-level navigation grouping differs. Training, Programs & Events, and About are identical in both approaches. In Option B, Contact becomes the CTA button. The difference is how Challenges + Solutions surface in the header, and how the homepage cards are grouped.

RECOMMENDATION

Option B consolidates the navigation for faster visitor comprehension while preserving all page architecture and SEO structure from Option A. We recommend this approach for the redesign.

Navigation Structure

54 pages from client doc

Path	Page Title	Type	Nav Level	Notes

Navigation ↔ Data Model Divergences

The client's navigation organizes content by user-facing topics (Challenges → specific challenge → related training/solutions), but the WordPress data model uses shared taxonomies to create these relationships.

For example, the training course "Leadership Core Skills" appears under multiple challenge pages (Workforce Retention, Culture & Engagement) via the challenge_area taxonomy — even though the CPT entry lives at /training/leadership-core-skills/.

Custom Post Types

Taxonomies

Relationship Diagram

DEV-SIDED INTAKE ONLY

The content blocks and template architecture below represent the development team's intake of what page types and content patterns will be needed. These are structural proposals — not client-approved designs. Visual design begins at design kickoff.

Pages are composed from reusable content blocks — not individual templates per content type. Editors build pages by stacking blocks in any combination.

Config

Centralized Settings

—

Content Blocks (proposed)

—

Hero Variants

—

WP Template Files

WordPress Template Architecture

Content Builder Blocks

ACF Flexible Content repeater with the following block types:

Whole-Project Gap Analysis

Across all inputs: content document, site discovery, client meetings, RFP requirements

This is a comprehensive accounting of every project workstream — not just the content document. Each item is categorized by current status: resolved (we have what we need), planned (approach defined, pending execution), or open (requires client input or discovery before we can proceed).

Resolved

Planned

Open

EVOLUTION: V1 → V2 Gap Analysis

V1 (March 2) reported "24 functional gaps / 89% not addressed" — which read like an alarm bell. That framing was misleading: it measured a content document against a technical spec checklist. Cindi's document was never supposed to contain registration architecture or Salesforce field mappings.

V2 (April 1) reframes with the full picture. After deep technical discovery of the live site, client meeting transcripts, and the 92-page content document, we now have clear resolution or a defined plan for 18 of 25 workstreams. The 7 truly open items all require client-side input — they cannot be resolved by our team alone.

Complete Workstream Status

Workstream	Status	What We Know	Next Action
Resolved — We have what we need
Site content & copy	Resolved	92-page content doc covers 49 of 53 sections. Homepage, 8 challenges, 6 solutions, 16 courses, programs, about, contact — all complete with copy.	Build phase
Information architecture	Resolved	Problem-first IA (challenges → solutions → training) defined with rationale. 8 challenge areas as connective tissue. Sitemap structure confirmed.	Build phase
Training course content	Resolved	16 courses with description, outcomes, topics, format, funding, prerequisites. 2 minor placeholders (Lean Fundamentals topics, Lean Practitioner outcomes).	Cindi to fill 2 placeholders
Contact form definitions	Resolved	3 forms fully defined with field names, types, and dropdown categories in the content doc.	Build phase
Payment processing	Resolved	Authorize.Net merchant account active, $258K+ processed. 31 GF feeds (30 active). Pricing $15–$4,495. We keep the account, replace the form layer.	Swap GF feeds → new form handler
Current site technical state	Resolved	Full discovery: 72 GF forms (CMS anti-pattern), 139 DB tables, WPBakery, 10,589 vc_empty_space shortcodes, 685 redirects, 4 abandoned registration systems.	No action — baseline documented
WordPress architecture	Resolved	ScheffeyTheme YAML-driven pattern. 6 CPTs (training_course, solution, learning_resource, program, testimonial, team_member). challenge_area taxonomy as connective tissue.	Build phase
Content builder system	Resolved	ACF Pro Flexible Content with 15 proposed block types. Editors stack blocks per page — no fixed templates per content type.	Build phase
Registration system architecture	Resolved	Replace 72 GF forms (clone-and-edit anti-pattern) with: training_course CPT → single reusable registration form → Authorize.Net payment → SF sync. Staff creates course as post, not as form clone.	Build phase
Email automation requirements	Resolved	4 flows defined: registration confirmation (immediate), 2-day reminder, staff notification (ops + web team), invoice request trigger.	Build phase — implementation TBD (WP transactional vs Pardot)
Sitemap / URL structure	Resolved	54 pages mapped with paths, types, hierarchy levels. CPT archives at /training/, /solutions/. 685 legacy redirects catalogued for migration.	Build phase — 301 redirect map at launch
Calendar / event date handling	Resolved	ACF date/time fields on training_course CPT. Multi-date support. Add-to-calendar links (Google, Outlook, Apple). Capacity management via seats field.	Build phase
Planned — Approach defined, pending execution
Visual design	Planned	Design kickoff with design team. Client preferences documented: minimalist, short pages (Bruce dislikes scrolling), accordions, chevron motifs. DVIRC.org + CatalystConnection.org as inspiration.	Design phase begins at kickoff
Navigation structure	Planned	Cindi's proposed 6-item nav analyzed. Consolidated 5-item proposal drafted with mega-menu approach. Side-by-side comparison built. See Nav Proposal tab.	Review and present at design kickoff
Salesforce integration	Planned	CRM Perks OAuth dead since Feb 2024. Dual Pardot tracking (piCId 10797 + 565372). Full Salesforce org audit complete (19-page report by Derek Beitz, April 2). Org structure, objects, automation, packages, and business process now documented. Integration approach to be defined using audit findings.	Scheffey CRM team — informed by completed SF org audit
Pardot consolidation	Planned	Two piCId values injected by two different plugins. Account ID 928773 confirmed. Need to determine which is authoritative and remove the duplicate.	Confirm during SF discovery session
301 redirect migration	Planned	685 existing redirects. Many are legacy/spam. URL structure is changing (new /challenges/, /solutions/, /training/ paths). Full redirect map needed at launch.	Generate redirect map before go-live
Open — Requires client input or discovery
Learning Center content	Open	Marked "to be completed" in Cindi's doc. Intended to house case studies, guides, podcasts, webinars. Architecture supports it (learning_resource CPT), but no content exists yet.	MANTEC team to provide — before May 1
Salesforce field mappings	Open	WordPress form fields defined in content doc. SF org audit has documented the object model (137 objects, 15 custom including Seminar + Seminar_Registrant). Field-level mapping session still needed to connect WP form fields to specific SF fields.	Mapping session: Scheffey CRM team + MANTEC CRM lead
Salesforce API access	Confirmed	SF org audit confirms API is active — multiple integration users (B2BMA, Exec Pulse, Integration User) logged in as of April 2. Connected Apps in use. Sandbox availability still TBD.	Confirmed via org audit — sandbox question remains
Pardot account access	Confirmed	Pardot (Account Engagement) confirmed active — v5.9, 2 apps, 19 objects. B2BMA integration bridge in place. Used for campaign and lead nurturing automation. Dual piCId consolidation still needed.	Confirmed via org audit — piCId consolidation remains
Brand assets	Received	Brand guidelines, logos, and assets received from MANTEC. Materials are limited but sufficient for design kickoff.	Received — in hand for design phase
Invoice workflow	Open	RFP references "invoice me" option on registration. Unclear: who generates the invoice? Is this a PDF? Sent from what system? Does it touch Salesforce?	Clarify with MANTEC ops team
Staff training / CMS handoff	Open	Current staff creates events by cloning GF forms and editing HTML. New system (CPTs) is radically simpler but requires training. Training plan to be defined with MANTEC team.	Training plan to be defined during build phase

Project Confidence

Content readiness 95%

Only Learning Center TBD + 2 placeholder fields

Architecture confidence 90%

CPTs, taxonomy, blocks, templates all defined

Integration clarity 65%

SF org audit complete; field-level mapping session still needed

Design direction 75%

Brand assets received; preferences documented; nav proposal drafted

Content Inventory from Client Document

Section	Page / Content	Status	Notes
Homepage	Homepage	✓ Complete	8 challenge card descriptions included
Challenges	Boost Productivity	✓ Complete	Intro, solutions, training references
	Find & Retain Employees	✓ Complete	Intro, solutions, training references
	Improve Safety & Quality	✓ Complete	Intro, solutions, training references
	Automate Tasks	✓ Complete	Intro, solutions, training references
	Train Your Team	✓ Complete	Intro, solutions, training references
	Strengthen Leadership	✓ Complete	Intro, solutions, training references
	Grow Sales	✓ Complete	Intro, solutions, training references
	Build Tomorrow's Workforce	✓ Complete	Intro, solutions, training references
Solutions	Assessments	✓ Complete	Description, outcomes, how it works
	Advisory & Coaching	✓ Complete	Description, outcomes, how it works
	Implementation Support	⚠ Complete*	Some placeholder text present
	Challenge Day	✓ Complete	Description, outcomes, how it works
	Training & Workshops	✓ Complete	Description, outcomes, how it works
	Supplier Scouting	✓ Complete	Description, outcomes, how it works
Training Courses	1. Intro to Lean Fundamentals	⚠ Topics Placeholder	Description and outcomes complete; Topics shows "Topic 1, 2, 3"
	2. Lean Practitioner Certificate	⚠ Outcomes Placeholder	Description complete; Outcomes shows "Outcome 1, 2, 3"
	3. Six Sigma Yellow Belt	✓ Complete	All fields detailed
	4. Six Sigma Green Belt	✓ Complete	All fields detailed
	5. Six Sigma Black Belt	✓ Complete	All fields detailed
	6. Introduction to Standard Work	✓ Complete	All fields detailed
	7. Introduction to GD&T	✓ Complete	All fields detailed
	8. Total Productive Maintenance (TPM)	✓ Complete	All fields detailed
	9. Floor Management Development System	✓ Complete	All fields detailed
	10. Leadership Core Skills Training	✓ Complete	All fields detailed
	11. Be a R.E.A.L. Success	✓ Complete	All fields detailed
	12. Dynamic Profiling for Manufacturers	✓ Complete	All fields detailed
	13. Project Management Fundamentals	✓ Complete	All fields detailed
	14. Advanced Project Management	✓ Complete	All fields detailed
	15. OSHA 30 Safety Training	✓ Complete	All fields detailed
	16. Integrating AI in Manufacturing	✓ Complete	All fields detailed
Programs & Events	CI Peer Group	✓ Complete	Agenda, meeting structure detailed
	HR Peer Group	✓ Complete	Overview and structure detailed
	Young Manufacturers Network	✓ Complete	Benefits, testimonial included
	Manufacturing Matters	✓ Complete	Quarterly tour series description
	Career Exploration (5 programs)	✓ Complete	All program descriptions included
	Lean Six Sigma Landing + Belts	✓ Complete	Overview and level descriptions
About	Who We Are	✓ Complete
	Our Impact	✓ Complete
	Our Mission	✓ Complete
	Our Team	✓ Complete
	Our Board	✓ Complete
Contact	Talk to a Member of Our Team	✓ Complete	Form fields defined
	Request On-Site Training	✓ Complete	Form fields defined
	General Contact Form	✓ Complete	Form fields with dropdown categories
Learning Center	Learning Center Hub	✗ TBD	Marked "to be completed" in document. No content provided yet.

Summary: 49 of 53 main content sections are complete or substantially complete. Learning Center (4 sections) is the only entirely missing section. This is the content Cindi confirmed she will provide, along with completion of the 2 placeholder course fields.

Salesforce Org Audit Complete

19-page audit by Derek Beitz (Soloex) — April 2, 2026 | Covers users, objects, automation, packages, reports, opportunity & account analysis, business process, and prioritized recommendations.

Full Integration tab revision forthcoming based on audit findings. Current content below reflects pre-audit planning.

Salesforce Integration: Past → Present → Direction

Past State

CRM Perks Salesforce plugin installed to sync Gravity Forms entries to Salesforce.

OAuth connection failed Feb 2024. No one noticed or fixed it.

Result: zero data flow between WordPress and Salesforce for 2+ years. Any registration reaching SF has been entered manually.

Pardot tracking deployed inconsistently — two different piCId values (10797 via WPCode, 565372 via Insert Headers & Footers), both under Account ID 928773. Unclear which is authoritative.

Present State

Integration is dead. The plugin is installed but non-functional. No forms are sending data to Salesforce.

Payment processing works — Authorize.Net merchant account handles $258K+ in transactions via GF feeds, independently of Salesforce.

Discovery session needed between Scheffey and MANTEC teams to understand what MANTEC actually needs from their Salesforce instance — contact records? opportunity tracking? event attendance? This needs to be defined before integration can begin.

Initial alignment discussions identified the need for a comprehensive discovery process to define the full integration workflow — not just a form migration.

Direction Forward

Build proper integration after discovery confirms requirements:

1. Discovery session defines which SF objects and fields matter

2. Evaluate REST API (custom) vs plugin (CRM Perks or Salesforce WP connector)

3. Consolidate Pardot tracking to one piCId

4. Registration form → Authorize.Net (payment) + Salesforce (CRM sync) in parallel

5. Pardot automation for email confirmations / reminders (if client uses Pardot for this)

Scope note: Salesforce integration complexity depends entirely on what the discovery session reveals. Simple contact-record sync is straightforward; full bi-directional workflow is a larger effort.

Salesforce Discovery Plan

Status: Discovery Phase

Questions for the discovery session:

• What SF objects do registrations need to touch? (Contact, Lead, Opportunity, Custom Object?)
• Is the Salesforce API enabled? Connected App available?
• Is there a sandbox org for development and testing?
• Which piCId is the correct Pardot tracking code?
• Does MANTEC use Pardot for email automation, or just tracking?
• Who has Pardot admin access?

Key context: Initial alignment discussions identified the need for a comprehensive discovery process to define the full integration workflow. Discovery must start from requirements, not assumptions.

Email Automation

Status: TBD

Required flows:

Registration Confirmation
Immediate upon registration, includes event details + add-to-calendar links
2-Day Reminder
Auto-send 2 days before event
Staff Notifications
New registration alert to operations team, web team, others as defined
Invoice Request
If registrant selects "Invoice me", trigger invoice generation

Payment Processing

Status: Continuation Plan

Current merchant account: Authorize.Net (active, processing $258K+)

Plan:

• Keep existing Authorize.Net merchant account
• Replace Gravity Forms feeds with proper form submission handler
• Support paid + free registrations
• Support invoice request option (per RFP)
• PCI compliance via Authorize.Net tokenization

Calendar & Event Scheduling

Status: TBD

Requirements:

• Course details include date, time, location, format (in-person/hybrid/online)
• Add-to-calendar links (Google Calendar, Outlook, Apple Calendar)
• Multi-date courses (some courses run multiple days)
• Registration capacity management (seats available)
• Staff view of registrations by event

Integration Timeline

Phase	What	Owner	Target Date
Discovery	Salesforce mapping session + define requirements	Scheffey CRM team + MANTEC CRM lead	Upcoming
Design	Visual design of registration form + flows	Scheffey design team	At kickoff
Development	Build CPTs, form handler, payment integration, email automation	Scheffey dev lead	After design
Testing	Registration workflow, payment, Salesforce sync, emails	MANTEC ops team + QA	Before launch
Go-Live	Production deployment upon client approval	Scheffey dev lead	After client review (dev link late July)