{"id":217,"date":"2023-11-11T20:26:00","date_gmt":"2023-11-11T20:26:00","guid":{"rendered":"https:\/\/www.mitango.app\/?p=217"},"modified":"2024-11-15T20:28:57","modified_gmt":"2024-11-15T20:28:57","slug":"wordpress-plugin-bored-repeating-yourself-try-to-use-a-framework","status":"publish","type":"post","link":"https:\/\/www.mitango.app\/fr\/2023\/11\/11\/wordpress-plugin-bored-repeating-yourself-try-to-use-a-framework\/","title":{"rendered":"WordPress plugin: Bored repeating yourself? Try to use a framework"},"content":{"rendered":"

<\/a><\/p>\n\n\n\n

As a developer the most boring thing that can happen in your job is repeating ourselves again and again. Any programmer is learning eagerer and this is often moment when nothing new is learned.<\/p>\n\n\n\n

The issue with developing WordPress plugin is that at the start of any new plugin implementation there is always a base to rebuild which is exactly the same code from a project to another minus the name of the project forcing us to repeat ourselves before we even started.<\/p>\n\n\n\n

The issue with boilerplates<\/h2>\n\n\n\n

The most common solution used while facing that issue by developers is to tackle it using generated code which create that base for them and that could be an excellent solution but you might guess that if we are here talking about another solution they also bring drawbacks.<\/p>\n\n\n\n

The biggest issue with boilerplates is that is not a recent solution and since then PHP evolved but boilerplates didn\u2019t or really few. Therefore that created a conflict for any developer that would like to use modern standards as their architecture is not compatible with modern pattern or technologies.<\/p>\n\n\n\n

The era of frameworks<\/h2>\n\n\n\n

To face modern problem we need modern solutions.<\/p>\n\n\n\n

In the modern days boilerplates faded away in favor of frameworks which are easier to evolve and maintain. Due to that particular requirement frameworks are build around package managers and more particularly Composer in PHP.<\/p>\n\n\n\n

This compatibility to Composer also open the door an easy management of third-party vendors which also enhance the don\u2019t repeat yourself philosophy.<\/p>\n\n\n\n

The vision behind Launchpad<\/h2>\n\n\n\n

As you might notice Launchpad ships by default with the minimum features to run and nothing more.<\/p>\n\n\n\n

This is something wanted and desired. Today WordPress is a slow solution so reducing as much as possible the footprint of the framework was an objective in order to prevent WordPress to become even slower technology.<\/p>\n\n\n\n

The second reason behind that simplicity is the mantra:<\/p>\n\n\n\n

\n

Don\u2019t impose your solution but always propose a fallback.<\/p>\n<\/blockquote>\n\n\n\n

The idea behind that is that picking a framework is like marriage where you need to accept the constraints that goes with it. In order to make our user lives easier our job as a framework developers is to make the constraints as loose as possible.<\/p>\n\n\n\n

In that purpose, we would only impose the strict minimum for the framework to work to them and give them the opportunity to develop their own solutions for anything that is outside this scope by adopting a modular architecture.<\/p>\n\n\n\n

However just shipping the bare minimum is not enough as most of users are often seeking a quick fix. That\u2019s why it is important to provide a set of default modules for handling most common usages.<\/p>\n\n\n\n

For Launchpad the default modules focus on 6 mains topics:<\/p>\n\n\n\n