Removed dependencies:

• Illuminate
  • Container
  • Validation
  • Collections
  • Database
  • Config
  • Log
  • Events
• Symfony
• Carbon
• Guzzlehttp
• Twig
• Scssphp

All dependencies are simplified and replaced with our codebase. 

Twig was causing more problems than benefits. Developers in most of the plugins do not check if twig is already registered and that was giving fatal errors that was burdon on our support to explain users that even if error log state that bug was not in our plugin they were still asking us to fix the bug. 

We were not using Symphony and Illumitate that much so we decided to redo php part and remove almost 6mb or dependencies. 

PHP Support

With removing dependencies and scoper we now support even php 8.0. Before minimum was 8.1 

Support for Dartsass

SCSSPHP is code heavy and outdated library that is easy to add to your project but they stated that moving to dartsass is too much work for them. So we moved to native Sass api. 

Gutenberg components library

We started migrating from radix components to gutenberg native components. They are more WordPress friendly and already comes with good accessibility. 

UI updates

We have removed all unnecessary elements to help you focus even more. Two rows header is now merged into one. Winden logo and pages are removed and now main priority are tabs. 

We do not have multiple pages as everything now is one react one page app. 

Added option to collapse right side menu to give more space

Added Topbar quick access. If you do not use WP Admin Cleaner menus can be crowded and this is much easier way to find it.

Helpers

Are now part of wizard with instant preview. If you enable for example bricks colors it’s natural to see interaction and preview right away.

Colors are formatted and now support groups as bricks and oxygen supports palette categories. 

Utility colors now also have preview even in wizard

Colors now start lightest as lowest number same as in tailwind css palette

Improved Wizzard config tab. 

Now all included helpers settings will be displayed inside config as well as JSON output. 

Improved Wizzard screens tab. 

Now support gutenberg break points. 

Generated files. 

We revered logic to have only 1 CSS file for style, not not to make it per task. 

Editor is now fetching content from files. If you edit style.css or config.js file and reload editor with fetch latest changes from tile and not database. If you delete files from upload foldes editor will fallback to the database. 

Improved Style gallery

Does not need to reload page to fetch latest data from config and wizzard. It was force reload before. 

Changed tailwind merge configurations 

Before we were using deepMerge. We moved to combining everything in one file now. And that is why we are allowing saving tailwind.config.js as well.

This helps us to have nicely combined config tab + wizard without breaking anything. 

Updated compile script. 

With cleaner configuration we do not need to hijack compile process anymore. 

Error scripts handling

Now error messages are properly formated to explain in witch line of code and where in code error occurs

Scan path now have toggle. 

Before it was unclear that you need to type path to start searching. Now it will scan it after you toggle it. Once you toggle it you will be presented with input filed to type path. 

Beside UI we also updated way of scaning files

Font Hero Integration

Now you can add custom fonts with just 1 click.

Fixes:

Bricks Builder integration

Improved class names crawling. We did not include classes added under options > CSS. Its fixed will latest build

Files Scaning now have option to save tailwind.config.js as well in case you want to edit them with VS. You will automatically get autocomplete based on your configuration. 

Tailwind CSS was effecting admin area. 

Now checkers if Gutenberg is enabled. 

After completing the deep integration with Gutenberg, Bricks Builder, and Oxygen by dynamically retrieving values from them, it’s time to focus even more on
in-browser actions.

Winden is no longer dependent on a server to compile CSS!

With that said, we reassure you that you will have full ownership of Winden and the compile process. Even if something happens to DPlugins, you will still be able to compile in the future.

other benefits? SPEED!

The compile process is now even faster, taking around 50ms. We’ve also merged the save and cache buttons, so you’ll receive the updated CSS instantly after making any changes.

More Benefits?
Autocomplete is not compiled anymore!

We’ve transitioned from compiling class names into a JSON array to directly communicating with the Tailwind Config, allowing us to retrieve all the data in real-time. This gives us access to more than just class names—it enables us to see the specific values associated with classes like p-2 or rounded-sm.

This also means that during compilation, there is only one task instead of two, reducing the load on both the browser and the server. This leads to even less stress on system resources, improving performance and efficiency.

25 pre-made code snippets.
Tester & Verified by our team.

To make your life easier we have crafted for you code snippets that you can import with one click.

You can test them by click import

Once imported they will be shown in the code block list same as any other that you have crated manually.

Code Snippets list:

Here is the content you provided converted into a table format:

Snippet Name	Description	Tags
Admin Bar Tricks	No description available	Admin
Disable the Emoji	If you are not using Emojis on your website front-end, you should disable it site-wide so that you can have less HTML requests.	WordPress
Change WordPress default excerpt […]	When using Excerpts in WordPress, you see the three dots ( … ) at the end by default, sometimes we need to describe more of this, then you can use this function to modify it.	Content
Change WordPress default excerpt length	By default, WP uses the first 55 words of the content for Excerpt. Sometimes we need to change the length according to client needs or design. Use this and change ’15’ to your need in the return function.	Content
Add a Suffix or Prefix to Woo Product Prices	Sometimes you may need to add a suffix or prefix to your WooCommerce product prices, and if you’d like to know how to accomplish that, see these two code snippets.	WooCommerce
Simple Maintenance Mode	A quick method of WordPress Maintenance Mode. If you are into SEO or already ranking in search engines, then we suggest using a Maintenance mode plugin instead because they handle the SEO aspects better…	Development
Change the text of related products section title	No description available	WooCommerce
Disable Automatic Updates for WordPress	Sometimes WordPress updates break working websites, and we usually don’t notice the issue until reported by someone. This snippet disables the automatic-updates for those cases.	WordPress
Disable Gutenberg editor for Widgets	Don’t like the Gutenberg when using Widgets area? This snippet is here to rescue…	Gutenberg
Disable Comments	If you don’t have a blog where you want to have comments from readers, then you should disable the comments to speed up the website a little bit…	WordPress
Remove Prefix From Archive Titles	Don’t like the prefix on archives (i.e., Category:, Product Category:, etc.)? This snippet will remove the prefix and just display the Archive Title.	Content
Custom Password Protected Message	No description available	Security
Disable Plugin & Theme Editing from WordPress	When you want to secure the theme & plugin modification from the client or misuse by anyone, this snippet disables the Theme Editor & Plugin Editor to secure it.	Security
Remove the Gutenberg Block Library CSS	If you don’t want to use Gutenberg anywhere, you don’t need the default loaded CSS for it on the frontend. This snippet will remove it and lower the HTTP requests.	Gutenberg
Add ID column in admin area for all posts types	Although we can easily see the IDs by hovering the title in WP admin area, sometimes we need to see it in bulk. This snippet will add an admin column for the ID attribute.	Development
Change Add to Cart button text	Sometimes users want to change the default ‘Add to Cart’ text to something else. This snippet is here to do that easily.	WooCommerce
Add product category class to body	This snippet will add a class to the body element for the current product category. It will add like (product_cat_…..) where ‘…..’ will be the slug of the category.	WooCommerce
Disable Gutenberg for specific post types only	No description available	Gutenberg
Allow SVG Uploads for Admins	No description available	Media
Current Year Shortcode	This will add a shortcode named [current_year] for you to add the current year dynamically anywhere possible.	Content
Disable XML RPC	To ensure your site remains secure, it’s a good idea to disable xmlrpc.php entirely.	Security
Disable Emails for Automatic Updates	If you want to keep the automatic updates enabled, but don’t want to receive an email on each update, then this snippet is for you.	WordPress
Lowercase filenames for upload files	Sometimes clients upload files with title case or capital case names. This snippet will make sure that on upload they are all converted to lowercase.	Media
Disable WordPress Lazy Load	No description available	Media
Cleanup WordPress header	This will clean up tags from WordPress stuff like its version, shortlinks, etc.	WordPress

Scripts Organizer and Gutenberg Studio are moved to latest version of Dart Sass.

Most developers, by default, use Composer, and the easiest way to implement Sass (SCSS) is to hook into the SCSSPHP library, and you’re good to go.

The problem with this approach is that SCSSPHP is still based on the older version of ‘LibSass,’ and we have been waiting for them to rebuild the entire library since 2020. It’s 2024 and they are only 60% complete. Read more about their roadmap: https://github.com/scssphp/scssphp/issues/210

Given the long wait, we decided it was time to look to the future.

We have completely revamped the compile process and are now using the native Dart compiler built with JavaScript. This ensures that we always have the latest compile compatibilities.

As a result, plugins are now lighter by 500kb, as we no longer use PHP to compile—only a lightweight JavaScript solution.

@Use or @Import

Actually, neither.

We understand that our users aren’t necessarily developers, and many use our plugin to avoid the complexities of coding. That’s why, instead of using the deprecated @import or requiring users to learn @use, we’ve taken a completely different approach.

We combine all partials and code blocks into one virtual file, ensuring they are in the correct order, and then compile it into a single CSS file.

Here are the key differences between @import and @use in SCSS:

Feature	@import	@use
Scope	Global scope, imports everything into the global namespace.	Scoped namespace, requires prefixed access to variables, mixins, and functions.
Global Pollution	Can cause global namespace pollution, leading to potential conflicts.	Prevents global namespace pollution by using a namespace.
Multiple Imports	Allows multiple imports, which can lead to duplicated CSS.	Imports only once per file, avoiding duplication.
Syntax Simplicity	Simple, but can become complex with large projects due to global scope.	Slightly more verbose but ensures better structure and maintainability.
Selective Import	Imports all content, no way to selectively import variables, mixins, or functions.	Allows selective importing and configuring through namespace or with keyword.
Best Practice	Considered outdated for modern SCSS projects.	Recommended best practice for modern SCSS development.
Configuration	Cannot configure imported variables.	Allows configuring variables at the point of import using with.
Compatibility	Supported by all versions of Sass.	Introduced in Dart Sass, may not be supported by older versions.

In summary, @use is the more modern, safer, and recommended approach for importing stylesheets in SCSS, while @import is older and more prone to issues in larger projects.

Are you effected?

No. Every SCSS is already converted to CSS and cached. Once you continue working on your project and press update button again it will be converted to CSS again with new feature.

Changes

The only change you will experience is once you import code blocks you will need now to regenerate code blocks.

Get the plugins:

Theme Support

Now, you can choose between Plugin or Theme to host updates. This option is located at the top of the sidebar in the Download settings.

Once you switch from Plugin to Theme, the sidebar will be updated, as banners are no longer necessary. Additionally, if you go to the “Resources” page and choose Theme instead of the main plugin file, you will receive Theme Style.CSS and Functions.PHP instead of the main plugin file.

Force Update

We have added a transient duration of 6 hours. During this period, we will not check for theme or plugin updates, as each check is an HTTP request that slows down the website, and we are focused on performance.

To force an update, you can either delete the transients from the database or simply click on “Check for update.” This will delete the transients and check for updates again.

Plugins check

Themes check

WP Self Hoster introduces GitHub Authentication, enabling access to and serving of private repositories.

Once you connect your account and grant access, you will get a dropdown to choose your repository. After selecting the repository, you will automatically receive the release zip and plugin version.

Main Template code improvements

define($plugin_prefix . '_VER', '3.0.1');

// Extract the version number
$plugin_data = get_file_data(__FILE__, ['Version' => 'Version']);
define($plugin_prefix . '_VER', $plugin_data['Version']);

<?php

/**
 * Plugin Name:       Marko
 * Description:       Marko's plugin description
 * Requires at least: 6.3.0
 * Requires PHP:      7.4
 * Version:           0.0.1
 * Author:            dev
 * License:           GPL-2.0-or-later
 * License URI:       https://www.gnu.org/licenses/gpl-2.0.html
 * Text Domain:       marko
 * Website:           
 */

if ( ! defined( 'ABSPATH' ) ) {
	exit; // Exit if accessed directly.
}

$plugin_prefix = 'MARKO';

// Extract the version number
$plugin_data = get_file_data(__FILE__, ['Version' => 'Version']); // <= Updated here

// Plugin Constants
define($plugin_prefix . '_DIR', plugin_basename(__DIR__));
define($plugin_prefix . '_BASE', plugin_basename(__FILE__));
define($plugin_prefix . '_PATH', plugin_dir_path(__FILE__));
define($plugin_prefix . '_VER', $plugin_data['Version']);  // <= Updated here

Release Template improvements

Added .gitignore and .distignore

Today, I’m excited to share the latest feature in our DevKit: the Granular Reset Tool.

What is the Granular Reset Tool?

The Granular Reset Tool allows you to safeguard specific WP options, so they remain unchanged even after a reset. This feature is incredibly useful for developers who have numerous plugins installed with activated licenses and specific settings they don’t want to lose.

How Does it Work?

Step-by-Step Guide:

1. Activate the Adminer: If you don’t know the table or option names, you can use the Adminer for assistance.
2. Select Options to Safe List:
   • Navigate to the Dev Kit reset.
   • Choose the wp-options you want to keep.
     For example, if you want to keep the license activated in the script organizer or maintain the Adminer’s active status post-reset, you can add these to the safe list.
3. Execute the Reset:
   • After selecting your options, proceed with the reset.
   • You’ll notice that the specified settings, like licenses, remain intact, while other content and settings are reset.

Why This Tool is a Game Changer

The Granular Reset Tool offers a level of precision not seen in other tools on the market. It provides developers with the flexibility to reset environments without losing crucial settings, enhancing efficiency and productivity.

We’d love to hear your thoughts! Leave a comment and let us know what you think about this new feature and what more you’d like to see in the DevKit.

Navigation Changes

• Adminer has now moved to the right and has new icon. Previously, we had a user icon, but it makes more sense to represent it with a database icon.
• Server Information is now renamed to Server Info
• Settings is now on the end of the list

Files Manager Updates

Selected row is now visible with background change.

Notice that: Uploading a file or folder will override the current one if it exists.

UI/UX Pages Updates

• Added stripes to scan easier
• Error log path is now separated section

• Added stripes to scan easier

• Added stripes to scan easier

Gutenberg Studio block category

that you can also rename as you need.

Better Code formatting With Prettier for CSS, SCSS, JS and HTML

Use CTRL (⌘) + P Shortcut to format code.

Hide Scripts Organizer
from WordPress Menu & Plugins list

By activating this feature Scripts Organizer will be removed from WordPress menu and also from the plugin list so no one can see it or access it.

1. You can activate this under Scripts Oganizer > Features.
2. Get access link to deactivate feature.

Since this will effect everyone even current user you can access Script Organizer by accessing secret link: YOURWEBSITEURL/wp-admin/?scorg_hide=no

You need to be logged in and be admin to access Scripts Organizer again.

GeneratePress Integration

Font Manager

You can add Font Hero registered font into GeneratePress System.

Typography Manager

You can use Font Hero registered font with global selector

GenerateBlcoks Integration

You can find registered fonts under GeneratePress Blocks Typography settings.

The best to learn is to see it. Style guide will be visible with default tailwind config and will be updated as you change config file.

That will give you clear visual representation of what is included and how it will behave.

You can now create new custom menu links inside the dashboard and optimise experience for you or your users.

Menu item option

1. Item Name
2. Item Icons
   • You can use Dashicon by clicking on the icons picker or typing the Dashicon name.
   • Or you can paste SVG code. Remember to replace the fill color with the current color.
3. Add Link. The link can also have the option to be opened in a new tab.
4. Menu priority. Read more about it on the WordPress docs →.
5. If you have multiple custom items, you can choose a parent.
   Only custom items can be parents, as we do not want to include them under other plugins.
6. Capability. We are using WordPress defaults capability options →. This option is not mandatory, and you can leave it as it is.
7. To not disturb others, you can create links only for yourself. By default, it’s for everyone.

Icon Picker

Instead of searching correct dashicon names you can do it with icons picker. or you can paste your own SVG Code

Sub Items

Custom menu icons can also include sub-icons to improve grouping and maintain focus for you or your users.

Hide from other

You can also decide if you want to display custom menu item for you or for others as well. By the default it’s for everyone.