# Primary goals

The development of our framework started in April 2020 (read more about [its history](https://docs.deep-web-solutions.com/knowledge-base/short-history-of-our-framework/)) and had primarily 3 goals:

1. [Central yet modular design](https://framework.deep-web-solutions.com/primary-goals/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](https://framework.deep-web-solutions.com/key-concepts-and-dev-tools) -- 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](https://framework.deep-web-solutions.com/primary-goals/no-3rd-party-dependencies) -- 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](https://www.php-fig.org/psr/) 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](https://packagist.org/packages/deep-web-solutions/) (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.