Skip to content

Hotfix/windows compatibility #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jul 15, 2025
Merged

Conversation

khleomix
Copy link
Contributor

@khleomix khleomix commented Jul 8, 2025

Closes

N/A

Link to test

Test locally

Description

  • Update compatibility with Windows.
  • Refactor webpack config for consistent font output
    • Fonts are now always copied from assets/fonts/ to build/fonts/ with their subfolder structure preserved.
    • Fonts outside the preset subfolders (body, headline, mono) will retain their directory structure in the build output.
    • Removed redundant font copy logic and simplified MiniCssExtractPlugin filename logic for clarity and maintainability.
  • Ensure all CSS files (including style, editor, and RTL variants) and block styles are output to the correct locations.

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

AI Assistance

  • 🤖 This project was developed with the help of a LLM/AI such as Cursor, Gemini, etc.

Added to documentation?

  • 📜 README.md
  • 📓 ClickUp
  • 🙅 No documentation needed

Added tests?

  • 👍 Yes
  • 🙅 No, because they aren't needed
  • 🙋 No, because I need help

Testing Instructions


Reviewer's Testing Checklist

As a reviewer, please verify that the relevant testing criteria are fulfilled and confirmed before approving this Pull Request.

  • Visual Regression Testing: Ensure that existing functionality is not negatively impacted by the changes.
  • Cross-Browser Compatibility: Test on major browsers (Chrome, Firefox, Safari) to ensure compatibility.
  • Mobile Responsiveness: Confirm that the changes are responsive and functional on various mobile devices.
  • Theme Compatibility: Ensure that the changes do not adversely affect the site's theme and styling.
  • Linting: Check that the code passes all linting checks (PHPCS, ESLint, SassLint). Check if PR passes code quality check.
  • Accessibility Testing: Validate that the changes comply with accessibility standards. Run npm run a11y.
  • Security Best Practices: Ensure that the code follows WordPress security best practices. Check if PR passes security check.
  • Documentation: Ensure that any new features or changes are appropriately documented in the README.md or Confluence.
  • Post-Deployment Tasks: Check if there are any tasks that need to be performed after deployment.

[optional] Additional Reviewer Notes or Considerations?

@khleomix khleomix self-assigned this Jul 8, 2025
@khleomix khleomix requested a review from thatmitchcanter July 15, 2025 16:26
@khleomix khleomix marked this pull request as ready for review July 15, 2025 16:26
Copy link
Contributor

@thatmitchcanter thatmitchcanter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - thanks @khleomix !

@thatmitchcanter thatmitchcanter merged commit 29c8d1f into base Jul 15, 2025
6 checks passed
@thatmitchcanter thatmitchcanter deleted the hotfix/Windows-compatibility branch July 15, 2025 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants