- 1<\/span> The journey of Mr.Dev.’s Widget and Module<\/a>
- 1.1<\/span> But then things changed..<\/a><\/li><\/ul><\/li>
- 2<\/span> The plugin development journey of Mr.Dev.’s Framework<\/a><\/li>
- 3<\/span> The new version of Mr.Utils joined with the Framework<\/a>
- 3.1<\/span> As of today, Mr.Utils and the framework reached the block editor!<\/a><\/li><\/ul><\/li>
- 4<\/span> Mr.Utils plugin is available on WordPress repository!<\/a><\/li>
- 5<\/span> Comments<\/a><\/li><\/ul><\/div>\n
The journey of Mr.Dev.’s Widget and Module<\/strong><\/span><\/h2>\n\n\n\n
Back when I first started developing Mr.Dev.’s Widget<\/a> and Module<\/a>, it didn’t have that name and the main intention was to show categories in accordions and posts inside tabs that are inside those accordions for Ruben R Dias<\/a> website.<\/p>\n\n\n\n
Back then, WordPress<\/a> and Joomla<\/a> were CMS where the frontend was totally dependent of extra elements (themes, plugins and other optional features) that the developer\/designer could choose to use or could create custom tools.<\/p>\n\n\n\n
<\/div>\n\n\n\n\n ![\"Ruben](\"https:\/\/marcosrego.com\/account\/wp-content\/uploads\/2021\/08\/rubenrdias-site-desktop-categories-1024x610.jpg\" "\\"-\\"")
Ruben R. Dias desktop website showing the main categories<\/figcaption><\/figure>\n<\/figure>\n\n\n\n We (developers) had the full control over the frontend. <\/p>\n\n\n\n
In my case, I choosed to create a widget and module because of the functions and the graphic user interface (GUI) that both WordPress and Joomla had already built-in. In theory they allowed to not bloat the systems with something otherwise done from scratch or using external dependencies.<\/p>\n\n\n\n
The version of Mr.Dev.’s widget\/module I gave to my direct clients became very powerful, allowing to show any type of content (from posts to products) with many options, themes and layouts<\/strong>. All that with checkbox and fields, so it was safe to give to clients<\/strong>, knowing they would not affect negatively the design.<\/p>\n\n\n\n
To indirect clients (people downloading the widget\/module to their own developments)<\/em> I put the most powerful features part of the paid plugin Mr.Dev.’s Framework<\/a><\/strong>.<\/p>\n\n\n\n
![\"Mr.Dev.'s](\"https:\/\/marcosrego.com\/account\/wp-content\/uploads\/2021\/08\/mrdev-widget-category-description_opengraph-1024x538.jpg\" "\\"-\\"")
<\/figure>\n\n\n\nBut then things changed..<\/strong><\/span><\/h3>\n\n\n\n
As for the module, Joomla 4<\/strong> was later released with different methods to create modules. It was not worth it to recreate the module, so it was discontinued and unsupported for other two reasons: The user-base of Joomla is much smaller comparing to WordPress and I was using Joomla mostly for a company where I am not working anymore<\/a>.<\/p>\n\n\n\n
As for the widget, WordPress also changed,<\/strong> with a new highly visual editor enabled by default: The Gutenberg block editor<\/strong> meant that WordPress was pushing to developers a specific tool to change the frontend, a tool that basically transforms the CMS into a site builder<\/strong>.<\/p>\n\n\n\n
And with that, the optional features such as widgets and the customizer started to become obsolete vs the block editor with full site editor growing much stronger.<\/p>\n\n\n\n
Despite this, Mr.Dev.’s Widget is still compatible and support is available<\/strong>! But no further development will be put into it (for the reason mentioned above).<\/p>\n\n\n\n
Instead I’ll focus my energies on Mr.Dev’s Framework and Mr.Utils..<\/strong><\/p>\n\n\n\n
- 4<\/span> Mr.Utils plugin is available on WordPress repository!<\/a><\/li>
- 2<\/span> The plugin development journey of Mr.Dev.’s Framework<\/a><\/li>
- 1.1<\/span> But then things changed..<\/a><\/li><\/ul><\/li>