Bot releases are hidden (Show)
We are delighted to introduce wd_s (wdunderscores) version 4.0.0, marking a significant milestone in WordPress theme development. In this release, wd_s transforms into a powerful hybrid theme, equipped with the Site Editor and pre-styled core blocks via theme.json, enhancing your creative possibilities. Here's what you can expect:
With wd_s version 4.0.0, you not only have a hybrid theme at your disposal, but you also enjoy a smoother and more productive WordPress theme development experience. Explore the new features, embrace the pre-styled core blocks, and make the most of the Site Editor.
Published by khleomix over 1 year ago
wd_s
Transition ReleaseWe are excited to announce the latest release of wd_s
, packed with exciting updates and improvements. This release focuses on ensuring compatibility with the latest technologies and leveraging new features to enhance your theme customization experience. Here's what you can expect:
We have updated our theme to be fully compatible with PHP 8.0, taking advantage of the latest features and improvements offered by this version. This ensures better performance, security, and compatibility with modern hosting environments.
In addition to PHP 8.0 compatibility, we have also made our theme compatible with Node.js 16 and tested up to Node 19. This allows developers to use the latest version of Node.js and leverage its enhanced performance, security, and new features when working with our theme.
We have implemented support for the new theme.json file introduced in WordPress. This powerful feature allows you to centralize and manage theme configuration settings, styles, and block editor settings. By leveraging theme.json, you can customize and fine-tune your theme with ease, reducing the need for custom code and enhancing the flexibility and maintainability of your website.
We have updated all theme dependencies to their latest versions, ensuring compatibility and security.
We have conducted extensive performance optimizations, resulting in faster page loading times and improved overall performance.
Various accessibility enhancements have been implemented, making wd_s
more inclusive and user-friendly for all visitors.
We have refined and updated various design elements, offering a more modern and visually appealing look.
We have addressed several reported issues and fixed bugs to ensure a smoother user experience.
Published by oliverharrison about 2 years ago
We have updated the function names across the board to be more descriptive of that function's purpose. This allows you to more easily scan the list of files inside a folder and know what you're able to do.
We've moved away from function prefixing (s or wd_s_) as a means to avoid function naming collions and have adopted a more modern approach. You can find more information (Highly recommended reading) about PHP namespaces at Sal Ferrarello's blog here and here.
Published by gregrickaby over 3 years ago
This release includes a complete and total overhaul of WDS Coding Standards. In short, we're just using WordPress Coding Standards.
Many years ago, WDS created its own PHP standards on top of WordPress PHP Standards. At that time Gutenberg wasn't even on the radar. We also created our own standards (and ruleset files) for Sass and JavaScript and included them in wd_s. Eventually, we even created Github repos, NPM packages, and even our own "WDS Scripts" package for compiling assets.
Since Gutenberg was released, WordPress now maintains ruleset files in both WordPress Develop and the Gutenberg repos for languages like Sass, JavaScript, and more. There's also @wordpress/scripts for compiling styles, scripts, and assets.
Maintaining our own standards and scripts was time consuming and using coding standards as packages sometimes caused issues. What happens if a Project Lead updated the project dependencies? Code editors are barking at Engineers about the entire codebase! Ugh. Projects themselves couldn't easily adjust standards to meet the project's needs either, and finally, the endless debates about them were exhausting.
There is no point in maintaining our own standards, scripts and NPM packages... let's just adopt what WordPress is doing.
@wordpress/scripts
(as natively as possible) for compiling assetspre-commit
hook in Git@wordpress/scripts
and deferring minifying to production builds only, npm run watch
compilation times were reduced from ~6-8 seconds down to ~2. 💪🏻 😮pre-commit
hook, we'll have less back-and-forth during a Pull Request. Engineers will be forced to check-in properly formatted code. This is good for the bottom line! 💰main
branch of wd_snpm i --legacy-peer-deps
npm run watch
to kick-off the dev server and BrowsersyncNot everyone want's to be stopped and forced to format their code prior to a commit. Especially if it's early in your feature, and you're working in a dirty branch prior to opening a pull request.
You can bypass the pre-commit
hook by using the --no-verify
flag.
git commit -m "fixed the thing" --no-verify
Note: Buddy will still run assertions against your PR, so don't forget to clean things up before opening it!
Thanks to @aubreypwd @jrfoell @richaber @salcode and @coreymcollins for all their testing and support.
Published by jrfoell almost 4 years ago
Adds composer/installers
dependency so theme is installed in the correct place when required via composer.
Published by gregrickaby about 4 years ago
This release marks a huge shift in how WebDevStudios builds websites going forward. Please read https://webdevstudios.com/2020/09/08/gutenberg-first/ for more information behind the "why".
To summarize, we've gutted wd_s and started over from scratch... leveraging a modern tool-chain for building WordPress themes.
Check out the README and Wiki for information on getting started.
@coreymcollins, @aubreypwd, and @asharirfan.
Also, thank you to everyone who was involved in each and every conversation and demo over the last few weeks.
WebDevStudios does not support semantic versioning for wd_s. Because this release is a such a drastic departure from 1.0, I felt it necessary to tag and release. WDS will not be tagging and releasing minor updates, we'll just push updates directly to the main
branch.