Listdom Developer Best Practices Documentation

Practical guidance backed by source patterns

These recommendations are derived from observed core behavior and extension points in extracted data.

1. Initialize on listdom_loaded

   • Core emits this action after initialization.

2. Use hooks/filters, not core file patches

   • Prefer extension points like lsd_template, lsd_addons, and API lifecycle hooks.

3. Follow API auth contract exactly

   • Send lsd-token for API token checks.
   • Send lsd-user for user-protected routes.

4. Match sanitization/escaping patterns

   • Use sanitization before persistence and escaped output in UI contexts.

5. Prefer theme template overrides

   • Override in /wp-content/themes/{theme}/listdom/... rather than editing plugin templates.

6. Integrate with existing JS event contracts

   • listdom:modal:opened, listdom:modal:closed, lsd-autocomplete-select, lsd-mapsearch.

Compatibility notes

WordPress Block Editor compatibility

Listdom 5.8.0 updates its block editor integration to use Block API version 3. No configuration change is required for normal Listdom sites.

If a custom integration extends or wraps Listdom blocks, test it after updating and review any custom assumptions about block registration, editor wrappers, or saved markup. This compatibility update does not convert Listdom shortcodes or Template Builder layouts into WordPress blocks.