DWS WP Framework
  • Welcome
  • Primary goals
    • Modular design
    • No 3rd-party dependencies
  • Key concepts and dev tools
    • PHP and WP requirements
    • Object-Oriented Programming
    • Semantic Versioning
    • Version Control (git / GitHub)
    • Dependency Management (Composer)
    • Automated Testing (Codeception + Github Actions)
    • Dependency Injection (PHP-DI)
    • Coding Standards (PHPCS and PHPMD)
    • Dependencies Scoping (PHP-Scoper)
    • TypeScript and Sass
    • Task Runners (Grunt)
  • Setting up your dev environment
    • Windows
  • Your first plugin
    • Multiple plugins using the framework on the same site
  • Frequently Asked Questions
  • Bootstrapper Module
    • Motivation
    • How it works
    • How to use
    • White Labeling
  • Helpers Module
    • Motivation
    • How to use
  • Foundations Module
    • Motivation and How to use
    • Actions
      • Local action traits
      • Extension action traits
      • Integration action traits
    • States
    • Utilities
      • Stores
      • Handlers and Services
        • Logging Service
  • Plugin
    • Main Plugin Instance
    • Plugin Components
  • Hierarchies
  • Helpers
  • Utilities Module
    • Motivation and How to use
    • Hooks Service
      • Scoped Handler
    • Shortcodes Service
    • Templating Service
    • Assets Service
      • Scripts Handler
      • Styles Handler
    • CRON Events Service
      • Action Scheduler Handler
    • Admin Notices Service
    • Dependencies Service
    • Validation Service
  • Core Module
    • Motivation and How to use
    • Plugin Tree
      • Plugin Root
      • Plugin Functionality
    • Plugin Components
      • Internationalization
      • Installation / Upgrade / Uninstallation
  • Settings Module
    • Motivation and How to use
    • Settings Service
      • WordPress Handler
      • MetaBox Handler
      • ACF Handler
    • Validated Settings
  • WooCommerce Module
    • Motivation and How to use
    • Extended WC Logger
    • WC Settings Handler
Powered by GitBook
On this page

Was this helpful?

Primary goals

The development of our framework started in April 2020 (read more about its history) and had primarily 3 goals:

  1. Central yet modular design -- the whole point of the framework is to have one central codebase for abstractions and functionalities that are reusable across multiple plugins; however, different plugins have different overlapping needs and we didn't want to force you to load code that will be unused.

  2. Modern development standards -- this framework was meant to fully embrace all the best practices of modern web development; the key concepts and dev tools section provides an introduction into each of them.

  3. Dependencies-free -- the framework should enable anyone to build WordPress plugins using modern tools, but it shouldn't force you to use any 3rd-party libraries you don't want to in production; wherever possible, the framework doesn't assume anything more than whatever the PSR standards foresee.

Obviously, programming is a very opinionated field. We might believe that we've achieved these goals, but you might disagree completely. And that's fine!

If you like our framework and want to use it yourself, you may do so (keeping in mind the GPLv3+ license). If you don't like it, that's awesome too -- but we would really appreciate any feedback you may have just in case there's something that didn't cross our minds yet.

PreviousWelcomeNextModular design

Last updated 3 years ago

Was this helpful?