Build on WordPress-native foundations.
Build on Free REST and WordPress-native extension points, then add Pro completion hooks, Search Push and licensed workflow webhooks.
Canonical shortcodes
Use the nexdirectory_ prefix for archives, maps, calendars, submissions, accounts and operational apps.
ExploreContent model
Core listings use the nexdirectory_event post type beneath profile-specific labels, with WordPress ownership and capability checks.
ExploreStandard classifications
Free uses the registered Type, Mode, Tag and Price Range taxonomies supplied by the active profile.
ExploreFree standard REST
Use the standard REST functionality supplied for core WordPress publishing workflows, with appropriate authentication and permission checks.
ExploreREST namespace
Core endpoints are registered under nexdirectory/v1. Treat route names and response shapes as versioned interfaces rather than scraping front-end HTML.
ExploreRead and write boundaries
Public discovery can expose published listing data; submissions, moderation, account actions and private records require the relevant user capability and request protection.
ExploreExtension safety
Use documented hooks, shortcodes, template overrides and REST interfaces instead of editing plugin files that will be replaced by an update.
ExplorePro integrations
Add Pro for IndexNow Search Push, domain verification, completion hooks and payment or Event Web App webhooks.
ExploreVersion and staging
Pin integrations to a tested NexDirectory version, review the changelog and verify permission, error and empty states on staging before deployment.
Choose the plan that matches the work.
Free handles publishing. Pro handles customisation, automation, monetisation and scale.
Turn the reference into action.
Start with canonical shortcodes
Use the nexdirectory_ prefix for archives, maps, calendars, submissions, accounts and operational apps.
Then review content model
Core listings use the nexdirectory_event post type beneath profile-specific labels, with WordPress ownership and capability checks.
Complete the plan with standard classifications
Free uses the registered Type, Mode, Tag and Price Range taxonomies supplied by the active profile.
Common questions.
What does NexDirectory developer reference cover?
Build on Free REST and WordPress-native extension points, then add Pro completion hooks, Search Push and licensed workflow webhooks.
How do Free and Pro differ?
Free covers unlimited basic publishing, discovery and day-to-day management. Pro adds advanced fields and filters, automation, commercial workflows, reporting and agency-scale controls.
Can one installation use all four profiles simultaneously?
No. Choose one active profile for each WordPress installation, then follow the relevant solution and feature guidance.