Welcome to the WP SMS development guide! This page provides an overview of the codebase, including key classes, methods, architectural decisions, and resources to help you understand the structure of the WP SMS plugin and contribute effectively.

Before diving into development, set up your development environment by following our comprehensive guide:

• Getting Started with WP SMS Development

This guide covers:

• Cloning the repository
• Installing PHP and JavaScript dependencies
• Building assets with Gulp
• Running unit tests with PHPUnit

• Gateway Dispatch Philosophy: Bulk vs Single & Template vs Simple API
• Add a new SMS Gateway

• All major WP SMS functions

• Hooks Reference

• Migration Manager

• Assets
• Singleton
• View
• Sms
• RemoteRequest

• TransientCacheTrait

• Notification

The WP SMS plugin is designed with a modular architecture to handle various functionalities like visitor tracking, performance reporting, and more. It is structured into several core components:

• Service Layer: Manages application logic and data processing.
• Models: Handles data operations and interactions with the WordPress database.
• Traits: Reusable code blocks.
• Helpers: Utility functions and classes for common tasks.

1. Follow Coding Standards: Adhere to PSR-12 standards for PHP coding to maintain code quality.
2. Error Handling: Ensure proper error handling using try-catch blocks.
3. Testing: Write unit tests for new features and critical components.

For a complete list of guidelines, visit our Contributing Guide.

We welcome contributions to the WP SMS project! To get started:

1. Read the Contributing Guide: Familiarise yourself with our development processes and standards.
2. Fork the Repository: Create your own fork to work on new features or bug fixes.
3. Create a New Branch: Use descriptive branch names like feat-your-feature-name.
4. Submit a Pull Request: Once your changes are ready, submit a pull request for review.

For more information on how to get involved, visit our GitHub Issues page.