• Block Showcase: Powerful development tool (admin-only) to discover, preview, and inspect all registered blocks with their attributes in an organized, interactive format.
• Dominant Color Images: Automatic calculation and storage of dominant colors for uploaded images, used as placeholders while images load.
• Image Prioritizer: Automatically prioritizes above-the-fold images with fetchpriority="high" for improved page load performance.
• WebP Uploads: Automatically generates WebP versions of uploaded JPEG and PNG images for better compression and faster loading.
• ESLint 9 Migration: Upgraded to ESLint 9 with flat config format for modern JavaScript linting.
• PHP Path Auto-Detection: Automatic PHP binary detection for cross-platform compatibility (Mac, Linux, CI/CD).
• CI/CD Extension Support: Automatic PHP extension handling for local development and CI environments.
• Package Updates: Updated npm and dependencies to latest compatible versions.
• Dependency Cleanup: Removed unused npm packages for cleaner dependency tree.
• RSS Block Fix: Improved handling of RSS blocks with missing or invalid feed URLs.

WDS BT is a foundational WordPress block theme designed for maximum flexibility and customization. It integrates seamlessly with the native WordPress block editor, providing an intuitive and adaptable user experience. WDS BT is specifically developed as a foundational rather than parent theme, giving developers a clean and versatile base for advanced customizations.

• WordPress 6.4+
• PHP 8.2+ (fully tested with PHP 8.3)
• NPM (v10+)
• Node (v20+)
• Composer 2+
• License: GPLv3

1. Clone this repository to your WordPress theme directory (wp-content/themes/).
2. Activate WDS BT from your WordPress admin panel under Appearance > Themes.
3. Run npm run setup to install dependencies and perform an initial build.

🔝 Back to Top

  
└── 📁wds-bt
 └── 📁assets
  └── 📁fonts
  └── 📁images
   └── 📁icons
  └── index.js
  └── 📁js
   └── 📁block-filters
    └── buttons.js
    └── index.js
   └── 📁block-variations
    └── index.js
   └── editor.js
   └── 📁global
    └── header.js
    └── index.js
    └── table.js
   └── index.js
   └── 📁templates
    └── index.js
  └── 📁scss
   └── _index.scss
   └── 📁abstracts
    └── _index.scss
    └── mobile-only-mixins.scss
    └── responsive-mixins.scss
    └── utility.scss
   └── 📁base
    └── _index.scss
    └── forms.scss
    └── global.scss
    └── pagination.scss
   └── 📁blocks
    └── 📁core
    └── 📁third-party
   └── editor.scss
   └── 📁patterns
    └── _index.scss
   └── 📁template-parts
    └── _index.scss
    └── footer.scss
    └── header.scss
   └── 📁templates
    └── _index.scss
    └── 404.scss
    └── archive.scss
    └── search.scss
 └── 📁inc
  └── 📁block-template
   └── 📁block
    └── edit.js.mustache
    └── editor.scss.mustache
    └── index.js.mustache
    └── render.php.mustache
    └── style.scss.mustache
    └── view.js.mustache
   └── index.js
   └── 📁plugin
    └── .editorconfig.mustache
    └── .eslintrc.mustache
    └── .gitignore.mustache
    └── $slug.php.mustache
    └── readme.txt.mustache
   └── README.md
  └── 📁functions
   └── back-to-top.php
   └── custom-logo-svg.php
   └── security.php
  └── 📁hooks
   └── enqueue-block-stylesheet.php
   └── enqueue-third-party-block-stylesheet.php
   └── register-block-categories.php
   └── register-block-filters.php
   └── register-block-pattern-categories.php
   └── register-block-patterns.php
   └── register-block-styles.php
   └── register-block-variations.php
   └── restrict-block-patterns.php
  └── 📁setup
   └── scripts.php
   └── setup.php
   └── style-script-version.php
 └── 📁pa11y-ci-report
 └── 📁parts
  └── comments.html
  └── footer.html
  └── header.html
  └── post-meta.html
 └── 📁patterns
  └── comments.php
  └── footer-default.php
  └── header-default.php
  └── post-hero.php
  └── primary-category.php
 └── 📁styles
  └── dark.json
 └── 📁templates
  └── 404.html
  └── archive.html
  └── index.html
  └── page-blank.html
  └── page-no-title.html
  └── page.html
  └── search.html
  └── single.html
 └── .editorconfig
 └── .env
 └── eslint.config.cjs
 └── .gitignore
 └── .markdownlintignore
 └── .nvmrc
 └── .prettierignore
 └── .prettierrc.js
 └── .stylelintignore
 └── .stylelintrc.json
 └── a11y.cjs
 └── babel.config.json
 └── composer.json
 └── composer.lock
 └── CONTRIBUTING.md
 └── functions.php
 └── lefthook.yml
 └── LICENSE.md
 └── package-lock.json
 └── package.json
 └── phpcs.xml.dist
 └── postcss.config.js
 └── README.md
 └── readme.txt
 └── screenshot.png
 └── style.css
 └── theme.json
 └── updateVersion.js
 └── webpack.config.js
  
 

cd /wp-content/themes/your-theme

npm run setup

🔝 Back to Top

From the command line, type any of the following to perform an action:

🔝 Back to Top

WDS BT includes an automated font management system that organizes fonts by purpose and automatically generates the necessary files for optimal font loading and WordPress integration.

assets/fonts/
├── headline/
│   ├── Inter.woff2
│   └── Poppins-Bold.woff2
├── body/
│   ├── Oxygen-Regular.woff2
│   └── OpenSans-Regular.woff2
└── mono/
    └── RobotoMono-Regular.woff2

npm run fonts
# or
php tools/font-processor.php

npm run fonts:detect
# or
php tools/font-detection.php

npm run fonts:generate
# or
php tools/font-generator.php

.heading {
  font-family: var(--wp--preset--font-family--headline);
}

.body-text {
  font-family: var(--wp--preset--font-family--body);
}

.code {
  font-family: var(--wp--preset--font-family--mono);
}

🔝 Back to Top

The theme includes an automated version update system that ensures consistency across all files that reference the theme version.

VERSION=1.4.0 npm run version-update

npx dotenv -e .env -- npm run version-update

# 1. Set the new version in .env file
echo "VERSION=1.4.0" > .env

# 2. Run the version update script
npm run version-update

# 3. Verify the changes
git diff

# 4. Commit the version bump
git add .
git commit -m "WDSBT-XXX - bump version to 1.4.0"

# 5. Tag the release (optional)
git tag -a v1.4.0 -m "Release version 1.4.0"
git push origin v1.4.0

# 1. Create a patch branch
git checkout -b patch/1.4.1

# 2. Make your bug fixes
# ... make changes ...

# 3. Update version to patch
echo "VERSION=1.4.1" > .env
npm run version-update

# 4. Commit changes
git add .
git commit -m "WDSBT-XXX - fix [specific issue]"

# 5. Commit version bump
git add .
git commit -m "WDSBT-XXX - bump version to 1.4.1"

# 6. Create pull request
git push origin patch/1.4.1
# ... create PR and merge ...

# 7. Tag the release
git checkout main
git pull origin main
git tag -a v1.4.1 -m "Patch release 1.4.1 - [brief description]"
git push origin v1.4.1

# 1. Create a feature branch
git checkout -b feature/1.5.0

# 2. Add new features
# ... implement features ...

# 3. Update version to minor
echo "VERSION=1.5.0" > .env
npm run version-update

# 4. Update CHANGELOG.md (if maintained)
# ... document new features ...

# 5. Commit changes
git add .
git commit -m "WDSBT-XXX - add [new feature]"

# 6. Commit version bump
git add .
git commit -m "WDSBT-XXX - bump version to 1.5.0"

# 7. Create pull request and tag release
# ... same as patch workflow ...

# 1. Create a major release branch
git checkout -b release/2.0.0

# 2. Implement breaking changes
# ... make breaking changes ...

# 3. Update version to major
echo "VERSION=2.0.0" > .env
npm run version-update

# 4. Update documentation for breaking changes
# ... update README, CHANGELOG, etc. ...

# 5. Test thoroughly
npm run build
npm run lint
npm run a11y

# 6. Commit changes
git add .
git commit -m "WDSBT-XXX - breaking: [description of breaking changes]"

# 7. Commit version bump
git add .
git commit -m "WDSBT-XXX - bump version to 2.0.0"

# 8. Create pull request and tag release
# ... same as patch workflow ...

# Quick patch workflow
git checkout -b hotfix/1.4.1
# ... make quick fix ...
echo "VERSION=1.4.1" > .env && npm run version-update
git add . && git commit -m "WDSBT-XXX - hotfix: [issue description]"
git push origin hotfix/1.4.1
# ... create PR, merge, tag ...

# Beta release
echo "VERSION=1.4.0-beta.1" > .env
npm run version-update

# Alpha release
echo "VERSION=1.4.0-alpha.1" > .env
npm run version-update

# Release candidate
echo "VERSION=1.4.0-rc.1" > .env
npm run version-update

🔝 Back to Top

1. Run the Block Creation Script Navigate to your project root in the terminal and run the following command to create a new block:

npm run create-block

Follow the prompts to configure your new block. The script will scaffold a new block structure inside assets/blocks/.

2. Build your block After editing and configuring your block, build your project to compile assets using webpack:

npm run build

This will process JavaScript, SCSS, optimize images, and generate necessary files for each custom block in the ./blocks directory.

🔝 Back to Top

'block_name' => array(
 'name' => __( 'label', 'wdsbt' ),
),

npm run build

npm run build

// In your variations JavaScript file
wp.blocks.registerBlockVariation('core/paragraph', {
 name: 'custom-variation',
 title: __('Custom Variation', 'wdsbt'),
 attributes: { /* Define your custom attributes here */ },
 // Add more variation settings as needed
});

// List of Gutenberg blocks to unregister
const unusedBlocks = [
 'core/file',
 'core/latest-comments',
 'core/rss',
 // Add more unused blocks as needed
];

// List of Gutenberg block variations to unregister
const unregisterBlockVariations = [
 // Example:
 // {
 //     blockName: 'core/group',
 //     blockVariationName: 'group-stack',
 // },
];

// Keep only the necessary embed variations
const keepEmbeds = [
 'twitter',
 'wordpress',
 'spotify',
 // Add more necessary embed variations as needed.
];

🔝 Back to Top

// Usage examples
.my-element {
  width: 100%;

  // Apply styles when the screen width is 600px or more
  @include responsive-mixins.responsive-min(600px) {
 /* Your responsive styles for min-width: 600px */
  }

  // Apply styles when the screen width is up to 600px
  @include responsive-mixins.responsive-max(600px) {
 /* Your responsive styles for max-width: 600px */
  }

  // Apply styles when the screen width is between 600px and 1200px
  @include responsive-mixins.responsive-range(600px, 1200px) {
 /* Your responsive styles for a range of widths */
  }
}

// Example usage:
.my-element {
  @include mobile-only-mixins.mobile-only;
}

🔝 Back to Top

This theme uses a modern stylelint.config.js configuration that extends the WordPress Stylelint Config with additional custom rules to maintain code consistency and enforce best practices.

The configuration extends the base WordPress stylelint ruleset, ensuring that all SCSS follows the WordPress coding standards while incorporating additional theme-specific preferences and PHP 8.3 compatibility.

To check your SCSS files for linting errors, run:

npm run lint:css

🔝 Back to Top

This theme uses PHP_CodeSniffer with WordPress coding standards and PHP 8.3 compatibility checks.

• PHP Version: Fully tested with PHP 8.2+ and PHP 8.3
• WordPress Standards: Follows WordPress-Extra and WordPress-Docs coding standards
• Compatibility: Uses PHPCompatibilityWP for version-specific checks

To check your PHP files for coding standard violations, run:

npm run lint:php

Note: PHP path and extension flags are automatically detected based on your environment. The linting scripts use the scripts/get-php.sh and scripts/get-php-flags.sh helpers to ensure compatibility across different development environments (Local by Flywheel, Homebrew, CI/CD).

🔝 Back to Top

This theme uses ESLint with WordPress coding standards for JavaScript files.

• Configuration: Uses ESLint 9 flat config format (eslint.config.cjs)
• Standards: WordPress ESLint plugin with recommended rules (via compatibility layer)
• Version: ESLint 9.x with @eslint/eslintrc for WordPress config compatibility

To check your JavaScript files for coding standard violations, run:

npm run lint:js

Note: This theme uses ESLint 9 with flat config format (eslint.config.cjs). The WordPress ESLint plugin configuration is loaded via the @eslint/eslintrc compatibility layer. Some WordPress rules incompatible with ESLint 9 are automatically disabled.

🔝 Back to Top

The Block Showcase is a powerful development tool that automatically discovers and displays all registered blocks (core WordPress blocks, custom theme blocks, and third-party plugin blocks) in an organized, interactive format. This feature is perfect for developers who want to see all available blocks, their attributes, and preview how they render.

• Automatic Block Discovery: Uses WordPress's WP_Block_Type_Registry to find all registered blocks
• Organized by Category: Blocks are grouped by their WordPress block categories (Text, Media, Design, Widgets, Theme, Embeds, etc.)
• Block Previews: Each block is rendered with example content so you can see how it looks
• Attribute Information: View all block attributes, their types, default values, and available options
• Interactive Accordions: Collapsible sections for easy navigation through block categories
• Security: Only accessible to administrators (manage_options capability)

1. Create a New Page:

   • Go to Pages > Add New in your WordPress admin
   • Give it a title (e.g., "Block Showcase")

2. Select the Block Showcase Template:

   • In the page editor, look for the Page Attributes panel (or Template in the sidebar)
   • Select "Block Showcase" from the template dropdown
   • Note: This template option is only visible to administrators

3. Publish the Page:

   • Click Publish to make the page live
   • The page will automatically display all registered blocks using the [wdsbt_block_showcase] shortcode

The showcase automatically organizes blocks into sections:

• Core Blocks: All WordPress core blocks, organized by category:

  • Text (Paragraph, Heading, List, Quote, Code, etc.)
  • Media (Image, Gallery, Audio, Video, etc.)
  • Design (Columns, Group, Cover, Separator, Spacer, etc.)
  • Widgets (Archives, Calendar, Categories, Latest Posts, etc.)
  • Theme (Site Logo, Site Title, Site Tagline, etc.)
  • Embeds (YouTube, Twitter, etc.)
  • Other Core Blocks (any blocks that don't fit the above categories)

• WDS BT Custom Blocks: All blocks registered with the wdsbt namespace

• Third Party Blocks: Blocks from other plugins, organized by their namespace

For each block, the showcase displays:

• Block Name: The human-readable display name
• Block Identifier: The fully qualified block name (e.g., core/paragraph)
• Attributes: Expandable details showing:
  • Attribute name
  • Data type (string, number, boolean, array, object, etc.)
  • Default value (if applicable)
  • Available options (if the attribute uses an enum)
• Live Preview: The block rendered with example content

The showcase uses intelligent content generation:

1. Block Examples: If a block has an example property defined, it uses that
2. Default Content: For core blocks, predefined example content is used
3. Default Attributes: For blocks with default attribute values, those are used to generate the preview
4. Fallback: If no example or defaults exist, a minimal block markup is generated

• Template Restriction: The Block Showcase template is only available to users with manage_options capability (administrators)
• Shortcode Protection: The [wdsbt_block_showcase] shortcode returns empty content for non-administrators
• 404 for Non-Admins: If a non-administrator tries to access a page using the Block Showcase template, they'll see a 404 error

The showcase styling can be customized via the theme's SCSS files:

• Main Stylesheet: assets/scss/templates/block-showcase.scss
• CSS Classes:
  • .wdsbt-block-showcase - Main container
  • .wdsbt-showcase-section-heading - Section headings (Core Blocks, WDS BT Blocks, etc.)
  • .wdsbt-showcase-category - Category containers
  • .wdsbt-showcase-block-card - Individual block cards
  • .wdsbt-showcase-block-title - Block name heading
  • .wdsbt-showcase-block-name - Block identifier code
  • .wdsbt-showcase-block-attributes - Attributes container
  • .wdsbt-showcase-block-preview - Block preview area

• Streaming Block Parser: Uses WordPress 6.9+ streaming block parser for efficient block processing
• WP_Block_Processor: Leverages the efficient WP_Block_Processor class for block rendering
• KSES Filtering: All block output is properly sanitized using WordPress's KSES system
• Data URI Support: Allows data URIs for images in block previews (temporarily enabled during rendering)

Block not showing in showcase:

• Some blocks (like core/legacy-widget and core/freeform) are intentionally skipped
• Blocks that require specific context or configuration may not render properly
• Check that the block is properly registered in WordPress

Template not appearing in dropdown:

• Ensure you're logged in as an administrator
• The template is hidden from non-admin users for security

Shortcode not rendering:

• Verify you have administrator privileges
• Check that the shortcode is placed in an HTML block: [wdsbt_block_showcase]

🔝 Back to Top

WDS BT automatically calculates and stores the dominant color for uploaded images, then uses it as a background placeholder while images load. This improves perceived performance by showing a color-coordinated placeholder instead of a blank space.

1. Automatic Color Calculation: When an image is uploaded to the media library, the theme calculates its dominant color using Imagick (if available) or the GD library.
2. Color Storage: The dominant color is stored as post meta (_dominant_color) for each image attachment.
3. Placeholder Display: When images are displayed, the dominant color is used as a background color, visible until the image fully loads.
4. Smooth Transitions: CSS and JavaScript handle smooth fade-in effects when images finish loading.

• Works with all standard WordPress image formats (JPEG, PNG, GIF, WebP)
• Automatically processes images uploaded through the media library
• Compatible with both attachment images and block editor image blocks (core/image and core/cover)

• File Location: inc/performance/dominant-color-images.php
• Color Calculation: Uses Imagick (preferred) or GD library fallback
• Storage: Post meta key _dominant_color (hex color format, e.g., #ff0000)
• Integration: Works with wp_get_attachment_image() and block editor image rendering
• Performance: Color calculation happens asynchronously during image upload

The dominant color is automatically applied to images. To customize the placeholder behavior, you can:

• Modify CSS: The feature adds a has-dominant-color class to images, which you can style in your theme's SCSS files
• JavaScript Events: Images with dominant colors have a data-dominant-color attribute for custom JavaScript interactions
• Disable for Specific Images: Filter wp_get_attachment_image_attributes to exclude specific images

• PHP GD extension or Imagick extension (for color calculation)
• WordPress 6.4+ (for block editor support)

Note: Inspired by the WordPress Performance plugin.

🔝 Back to Top

WDS BT automatically prioritizes above-the-fold images by adding fetchpriority="high" to the first few images on a page. This signals browsers to load these critical images sooner, improving perceived performance and Largest Contentful Paint (LCP) metrics.

1. Image Detection: On singular pages, the theme identifies the first few images (featured image plus up to 3 images from content).
2. Priority Assignment: Adds fetchpriority="high" attribute to these above-the-fold images.
3. Lazy Loading Removal: Automatically removes loading="lazy" from prioritized images since they should load immediately.
4. Compatibility: Works alongside the existing LCP image optimization without conflicts.

• Featured images (post thumbnails)
• Images in content blocks (core/image and core/cover)
• Works with both attachment images and block editor image blocks

• File Location: inc/performance/image-prioritizer.php
• Priority Limit: Prioritizes up to 3 images per page (featured image + 2 content images)
• Page Types: Only active on singular pages (posts, pages, custom post types)
• Integration: Works with wp_get_attachment_image() and block editor image rendering
• Compatibility: Checks for existing fetchpriority to avoid conflicts with LCP optimization

• LCP Optimization: Focuses on the single Largest Contentful Paint image
• Image Prioritizer: Prioritizes multiple above-the-fold images for broader performance improvement
• Both work together: The LCP image will be prioritized by both systems, ensuring optimal loading

The prioritization happens automatically. To customize:

• Change Priority Limit: Modify the $limit parameter in get_above_fold_image_ids() function
• Exclude Specific Images: Filter wp_get_attachment_image_attributes to exclude images
• Disable for Specific Pages: Use conditional checks in the filter functions

Note: Inspired by the WordPress Performance plugin.

🔝 Back to Top

WDS BT automatically generates WebP versions of uploaded JPEG and PNG images. WebP format provides superior compression compared to JPEG and PNG, resulting in smaller file sizes and faster page loads while maintaining image quality.

1. Automatic Conversion: When JPEG or PNG images are uploaded, the theme automatically generates WebP versions.
2. Multiple Sizes: WebP versions are created for all registered image sizes (thumbnail, medium, large, etc.).
3. Storage: WebP files are stored alongside original images with .webp extension.
4. Metadata: WebP file paths and URLs are stored in attachment metadata for easy access.

• Input: JPEG and PNG images
• Output: WebP format (85% quality by default)
• Image Sizes: All WordPress registered image sizes (thumbnail, medium, large, full, and custom sizes)

• File Location: inc/performance/webp-uploads.php
• Conversion Method: Uses Imagick (preferred) or GD library fallback
• Quality Setting: 85% compression quality (balance between file size and quality)
• Storage: WebP files stored in same directory as originals with .webp extension
• Metadata Keys: _webp_file (file path) and _webp_url (URL)

• PHP Extensions: Imagick with WebP support OR GD library with imagewebp() function
• Server Support: WebP format must be supported by your PHP installation
• WordPress: WordPress 6.4+ recommended

The theme provides helper functions to access WebP versions:

// Get WebP URL for an attachment.
$webp_url = \WebDevStudios\wdsbt\get_webp_url( $attachment_id );

// Get WebP file path for an attachment.
$webp_file = \WebDevStudios\wdsbt\get_webp_file( $attachment_id );

// Check if browser supports WebP.
$supports_webp = \WebDevStudios\wdsbt\browser_supports_webp();

• Modern browsers (Chrome, Firefox, Edge, Safari 14+) support WebP natively
• The theme adds data-webp attribute to images for JavaScript-based fallback handling
• Original images are always preserved for compatibility

• Quality Setting: Modify the quality parameter (85) in generate_webp() function
• File Naming: WebP files use the same name as originals with .webp extension
• Size Generation: WebP versions are automatically generated for all image sizes

The theme automatically generates WebP versions for existing images in the following scenarios:

1. Automatic Regeneration: When image thumbnails are regenerated (e.g., using the "Regenerate Thumbnails" plugin), WebP versions are automatically created

Method 1: WordPress Admin (Easiest)

1. Go to Tools > WDSBT Settings in your WordPress admin
2. Click the "Regenerate WebP for All Images" button
3. Confirm the action
4. Wait for the process to complete (may take several minutes for large media libraries)

Method 2: WP-CLI (Recommended for Large Sites)

# Regenerate WebP for all images
wp webp regenerate --all

# Regenerate WebP for a specific attachment
wp webp regenerate --attachment-id=123

Method 3: PHP Function (For Developers)

// Regenerate WebP for a specific attachment
\WebDevStudios\wdsbt\regenerate_webp_for_attachment( $attachment_id );

// Bulk regeneration for all images
$attachments = get_posts( array(
    'post_type'      => 'attachment',
    'post_mime_type' => array( 'image/jpeg', 'image/png' ),
    'posts_per_page' => -1,
    'fields'         => 'ids',
) );

foreach ( $attachments as $attachment_id ) {
    \WebDevStudios\wdsbt\regenerate_webp_for_attachment( $attachment_id );
}

Note: Inspired by the WordPress Performance plugin.

🔝 Back to Top

This theme automatically registers block pattern categories based on subfolders in the patterns/ directory. To add a new pattern category:

1. Create a new subfolder inside patterns/ (e.g., patterns/cards/).
2. Place your pattern PHP files in that subfolder.
3. In each pattern file, set the Categories header to the folder name (e.g., Categories: cards).

The category will be registered automatically and available in the block editor. No manual code changes are needed to add new pattern categories.

🔝 Back to Top

WDS BT integrates automated workflow actions to maintain high standards of code security, quality, and accessibility. Accessibility checks are built into the development process, ensuring that websites developed with WDS BT comply with WCAG 2.2 standards. This proactive approach reflects WDS BT's commitment to inclusivity and usability for all users.

🔝 Back to Top

WDS-BT enforces strict Lefthook integration with pre-commit, pre-receive, pre-push, and push hooks. These ensure that all automated quality checks (linting, formatting, security, accessibility) are executed before commits and pushes.

• Pre-Commit Hook: Runs quality checks before allowing a commit.
• Pre-Receive Hook: Ensures compliance before WDS-BT accepts the push.
• Pre-Push Hook: Runs additional validations before pushing changes to remote.
• Push Hook: Enforces project-wide integrity checks before finalizing a push.

Bypassing Lefthook (--no-verify) is strictly prohibited, ensuring that all enforced checks are properly executed.

🔝 Back to Top

This project uses rimraf in npm scripts instead of rm -rf to ensure compatibility across Windows, macOS, and Linux. All contributors can use the provided npm scripts without needing Git Bash or WSL on Windows.

If you add new scripts that need to remove files or directories, please use rimraf instead of rm -rf.

The project automatically detects the PHP binary path for cross-platform compatibility (Mac, Linux, CI/CD). The detection scripts (scripts/get-php.sh and scripts/get-php.js) check common paths:

• /opt/homebrew/bin/php (Homebrew on Apple Silicon Mac)
• /usr/local/bin/php (Homebrew on Intel Mac / Linux)
• /usr/bin/php (Standard Linux path)
• php (Fallback to PATH)

For CI/CD environments (like Buddy or GitHub Actions): You can set the PHP_BIN environment variable to override auto-detection:

export PHP_BIN=/usr/bin/php

The project automatically handles PHP extensions based on the environment:

• Local Development: Uses -n flag to suppress extension warnings (useful for Local by Flywheel environments with mismatched extensions)
• CI/CD Environments: Automatically enables required extensions (tokenizer, xmlwriter, simplexml) for PHPCS and other tools

The scripts/get-php-flags.sh script detects the environment and applies the appropriate flags. This ensures builds work correctly across different environments without manual configuration.

Your contributions and support tickets are welcome. Please see our contributing guidelines before submitting a pull request.

WDS BT is free software, and is released under the terms of the GNU General Public License version 2 or any later version. See LICENSE.md for complete license.

The WDS-BT theme was initially inspired by the Powder theme. We acknowledge and thank the creators of Powder for their work.

🔝 Back to Top