Enterprise Design System and Digital Experience Standard
The authoritative standard for the design, structure, accessibility, automation, governance, and continuous improvement of every NAPPSA digital experience.
1. Purpose and Scope
This standard applies to all public pages, member workspaces, executive applications, committee tools, conference systems, Foundation experiences, AI services, plugins, forms, dashboards, integrations, and automated publishing workflows operated under NAPPSA and NEOS.
Its purpose is to ensure that every experience is clear, consistent, secure, accessible, measurable, maintainable, and aligned with NAPPSA’s mission.
2. Governing Principles
Purpose, audience, current status, and next action must be obvious.
Similar tasks must use the same components, language, and interaction patterns.
Information must be current, attributable, validated, and transparent.
Experiences must be usable across devices and by people with disabilities.
Repetitive work should be automated with validation, logging, and human oversight.
New programs and data sources must fit the architecture without redesigning the platform.
3. Standard Digital Object Model
Important information must be managed as structured objects rather than isolated page text. Core object types include Member, Event, Conference, Committee, Course, Intelligence Article, Executive Brief, Publication, Expert, Sponsor, Donor, Campaign, Scholarship, Grant, Award, Chapter, Volunteer Opportunity, and Research Project.
Every object must include, where applicable: unique identifier, canonical URL, owner, status, audience, created date, modified date, review date, expiration date, taxonomy, search metadata, relationships, accessibility metadata, SEO metadata, source attribution, and version history.
4. Universal Page Standard
- Identity: title, concise purpose statement, breadcrumb, owner, and last-updated date.
- Current Status: deadlines, alerts, availability, and time-sensitive information.
- Primary Content: the essential information required to complete the visitor’s task.
- Related Resources: relevant people, events, education, intelligence, documents, and opportunities.
- Recommended Next Step: one visually dominant and contextually relevant action.
- Feedback: a lightweight mechanism to report a problem or indicate whether the page was helpful.
5. Approved Component Library
New interfaces should use approved reusable components: hero headers, action cards, status panels, metric cards, event cards, speaker cards, profile cards, timelines, accordions, notification banners, search interfaces, forms, tables, progress indicators, breadcrumbs, disclosure panels, and next-step callouts.
One-off styling is permitted only when an approved component cannot meet a documented user need. Any new component must be named, documented, accessibility-tested, responsive, and added to the component inventory.
6. Visual and Interaction Standard
- Primary colors: NAPPSA navy, white, and heritage gold.
- Body copy must remain highly readable, with sufficient spacing and contrast.
- Pages must have one clear primary action and no more than two secondary actions within the opening viewport.
- Motion must be purposeful, limited, and disabled when users prefer reduced motion.
- Mobile layouts are not compressed desktop layouts; they must preserve task order, readable type, touch targets, and content hierarchy.
- Visitors must be able to identify where they are, what is current, and what to do next within approximately seven seconds.
7. Content Quality Gates
No automated or manual content may be published unless it passes the following controls:
- Specific and meaningful title
- Correct destination and audience
- Reliable source and attribution
- Freshness and expiration checks
- Duplicate and near-duplicate detection
- Mobile rendering validation
- Accessible headings, links, images, and controls
- Taxonomy and search metadata
- Broken-link and missing-media checks
- Editorial state and accountable owner
8. AI Governance
Every AI service must have a documented purpose, approved data sources, permitted decisions, prohibited decisions, escalation path, audit log, quality metric, and human-approval boundary.
AI-generated summaries and recommendations must be clearly distinguishable from authoritative source material. Clinical, legal, financial, regulatory, credentialing, and governance decisions may not rely solely on unreviewed AI output.
9. Automation Governance
Every production automation must define its trigger, inputs, validation rules, processing logic, outputs, notifications, audit trail, failure handling, rollback procedure, owner, and review cadence.
Automations must fail safely. When required data is missing or quality validation fails, the workflow must hold, route to review, or suppress publication rather than publish misleading information.
10. Role-Based Access Standard
Access must be assigned through roles and entitlements rather than scattered page-level exceptions. Standard roles include Visitor, Member, Volunteer, Committee Member, Committee Chair, Conference Team, Foundation Team, Executive Board, Administrator, and System Administrator.
Protected information must use least-privilege access, authenticated sessions, explicit authorization checks, and auditable administrative changes.
11. Performance and Accessibility Targets
| Largest Contentful Paint | Target under 2.5 seconds |
| Accessibility | WCAG 2.2 AA as the minimum standard |
| Mobile usability | No critical mobile defects |
| Broken links | Zero known critical broken links |
| Search | Relevant results and measurable task completion |
12. Content Lifecycle
All governed content follows: Draft → Review → Approved → Published → Review Due → Archived → Removed.
Each item must have an owner and review date. Time-sensitive material must have an expiration rule. Archived content must remain available only when it has historical, legal, accreditation, or governance value.
13. Measurement Framework
Success must be measured through outcomes rather than page views alone. Required enterprise indicators include membership conversion, renewal, conference registration, CE enrollment and completion, volunteer participation, donations, search success, task completion time, mobile completion, accessibility defects, content freshness, and user satisfaction.
14. Change-Control Checklist
Before deployment, the responsible owner must confirm:
- The user problem and intended audience are documented.
- The feature uses approved objects and components.
- Security, privacy, accessibility, mobile, and performance checks have passed.
- Analytics and audit logging are configured.
- Rollback and support procedures exist.
- Production ownership and review cadence are assigned.
Authority and Review
This document is the baseline NEOS digital experience standard. Exceptions require written justification, an accountable owner, and approval through the established NEOS governance process. The standard should be reviewed at least annually and whenever a major platform, regulatory, accessibility, or data-governance change occurs.